From: Christer Solskogen <christer.solskogen@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Problem cross-compiling gcc
Date: Sun, 12 Feb 2023 18:51:06 +0100 [thread overview]
Message-ID: <tsb8ub$7ka$1@ciao.gmane.io> (raw)
While cross compiling gcc with musl I see this:
checking for exported symbols... /home/solskogen/gcc/libcc1/configure:
line 15053: -T: command not found
yes
checking for -rdynamic... /home/solskogen/gcc/libcc1/configure: line
15063: -T: command not found
no
checking for library containing dlopen... none required
checking for -fPIC -shared... yes
configure: error:
Building GCC with plugin support requires a host that supports
-fPIC, -shared, -ldl and -rdynamic.
make[1]: *** [Makefile:11890: configure-libcc1] Error 1
This is the configure line: /home/solskogen/gcc/configure --prefix=/usr
--libexecdir=/lib --host=aarch64-centrix-linux-musl
--target=aarch64-centrix-linux-musl --build=x86_64-pc-linux-gnu
--enable-languages=c,c++ --disable-multilib --enable-checking=release
--disable-nls --with-gcc-major-version-only --enable-plugin
--disable-libstdcxx-pch --enable-default-pie --enable-default-ssp
--disable-libsanitizer --enable-host-shared
I can't figure out that it doesn't find. But a google search suggests
objdump.
gcc is at version 12.2.0. Worth submitting a bug report?
next reply other threads:[~2023-02-12 17:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 17:51 Christer Solskogen [this message]
2023-02-12 19:24 ` Jonathan Wakely
2023-02-13 7:19 ` Christer Solskogen
2023-02-13 8:37 ` Christer Solskogen
2023-02-12 20:01 ` Kai Ruottu
2023-02-13 7:23 ` Christer Solskogen
2023-02-13 10:30 ` Kai Ruottu
2023-02-13 8:16 ` Segher Boessenkool
2023-02-13 8:35 ` Christer Solskogen
2023-02-13 8:47 ` Segher Boessenkool
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='tsb8ub$7ka$1@ciao.gmane.io' \
--to=christer.solskogen@gmail.com \
--cc=gcc-help@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).