From: Kai Ruottu <kai.ruottu@wippies.com>
To: Christer Solskogen <christer.solskogen@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: Problem cross-compiling gcc
Date: Sun, 12 Feb 2023 22:01:57 +0200 [thread overview]
Message-ID: <d762217e-7155-42ed-e532-8a3aa855a8a0@wippies.com> (raw)
In-Reply-To: <tsb8ub$7ka$1@ciao.gmane.io>
Christer Solskogen via Gcc-help kirjoitti 12.2.2023 klo 19.51:
> 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
What is intersting in this case is WHICH GCC the build tries to use when
compiling libgcc. It should be the 'aarch64-centrix-linux-musl' targeted
cross-GCC, used for the becoming $host
system to create the executables and libraries for it. So what are the
CC_FOR_TARGET, GCC_FOR_TARGET, CXX_FOR_TARGET and GXX_FOR_TARGET in the
main Makefile and in the one
used for libgcc? My habit has been years to define these in environment
before running configure. Maybe these simply don't work in the "native
Canadian Cross" case. (To create a native
GCC with a cross-GCC).
next prev parent reply other threads:[~2023-02-12 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 17:51 Christer Solskogen
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 [this message]
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=d762217e-7155-42ed-e532-8a3aa855a8a0@wippies.com \
--to=kai.ruottu@wippies.com \
--cc=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).