From: "lange@chello.at" <lange@chello.at>
To: gcc@gcc.gnu.org
Subject: libcc1 depencies
Date: Thu, 12 Feb 2015 13:12:00 -0000 [thread overview]
Message-ID: <860094712.2781809.1423746725723.open-xchange@upcmail.upc.at> (raw)
Hello,
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
multiple systems.
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++
--print-file-name libsupc++.a`,-Bdynamic"
*) 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
/home/build/toolchain-arm-none-eabi-5.0-5.0.0/gcc/libcc1/configure
--prefix=/opt/toolchain-5.0 --build=i686-pc-linux-gnu --host=i686-pc-linux-gnu
--target=arm-none-eabi
Note that this is an out-of-source-tree build!
The result is an error:
/home/build/toolchain-arm-none-eabi-5.0-5.0.0/gcc/libcc1/findcomp.cc:20:20:
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.
Kind Regards,
Norbert Lange
(I send one mail as HTML, apologies if this message will appear twice)
reply other threads:[~2015-02-12 13:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=860094712.2781809.1423746725723.open-xchange@upcmail.upc.at \
--to=lange@chello.at \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).