This is the mail archive of the
mailing list for the GCC project.
- From: "lange at chello dot at" <lange at chello dot at>
- To: gcc at gcc dot gnu dot org
- Date: Thu, 12 Feb 2015 14:12:05 +0100 (CET)
- Subject: libcc1 depencies
- Authentication-results: sourceware.org; auth=none
- Reply-to: "lange at chello dot at" <lange at chello dot at>
I am trying to build a cross-compiler for arm, like I did so for years. I am
keen on not having depencies on libraries, so that the compiler can be used on
Up until 4.9 the only depency is libc, I tried using the gcc-5-20150208
snapshot, and now I get depencies on the build-compilers libstdc++ and libgcc_s.
This is double annoying because this is not the default compiler of the OS, and
those paths might not exist and there is a chance of mixing versions.
The rest of gcc is adhering to the configuration, but for libcc1 this seems to
be lacking. I use this configuration to statiscally link C++:
--with-host-libstdcxx="-Wl,-Bstatic,`g++ --print-file-name libstdc++.a`,`g++
*) I tried setting -static-libstdc++ via LDFLAGS, but libtool is linking the
explicit libraries with the path to the build-compiler (not the system library)
*) I tried compiling libcc1 seperately
--prefix=/opt/toolchain-5.0 --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu
Note that this is an out-of-source-tree build!
The result is an error:
fatal error: config.h: No such file or directory
I would want to at least be able to statically link libstdc++. Ideally the
reference to libgcc_s would be gone aswell, or atleast be pointing to the system
library. Right now I dont find the measures to do that.
(I send one mail as HTML, apologies if this message will appear twice)