Skip to content

flags and target #24

@ghost

Description

llvm 6.0.1

bash-4.3# gcc -dumpversion
5.5.0
bash-4.3# gcc -dumpmachine
i586-slackware-linux
bash-4.3# llvm-config --host-target
i686-pc-linux-gnu
bash-4.3#

using gcc to build (code change for Makefile.in)

tests/external.test (external-1 and external-2) will obviously fail without the change to LLVMTARGET

- LLVMCFLAGS = `${LLVMCONFIG} --cxxflags`
+ LLVMCFLAGS = `${LLVMCONFIG} --cxxflags | sed \
+  's/ -Werror=unguarded-availability-new//;s/ -Wcovered-switch-default//;s/ -Wstring-conversion//'`

- LLVMTARGET = `${LLVMCONFIG} --host-target`
+ LLVMTARGET = `${CC} -dumpmachine`
bash-4.3# grep "i686-pc-linux-gnu" /tmp/llvmtcl-3.9.2/libllvmtcl3.9.2.so
bash-4.3# grep "i586-slackware-linux" /tmp/llvmtcl-3.9.2/libllvmtcl3.9.2.so
Binary file /tmp/llvmtcl-3.9.2/libllvmtcl3.9.2.so matches
bash-4.3#

cf: https://nurmi-labs.blogspot.com/2019/04/tclquadcode.html

Can someone clarify running another Linux distribution and architecture what the following outputs?

gcc -dumpmachine

llvm-config --host-target

I cannot say what those commands (and 'clang --version') will output in terms of triples, on for example Red Hat and S.u.S.E., which are listed along with Slackware and a couple of other distributions, as having distribution specific triples in the following file.

cfe-6.0.1.src/lib/Driver/ToolChains/Gnu.cpp

Certainly, other software which has a dependency upon the Slackware Linux distributions' builds of llvm are not having a problem resultant of such triple disparity; so I wouldn't even consider a recompile [for different triples, if that were even feasible (?)] of llvm for Slackware and Slackware64 Linux.

Incidentally it's not clear why LLVMCFLAGS is used as a variable essentially for LLVMCXXFLAGS.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions