public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Thomas Sobczynski <tsobczynski@werfen.com>
Cc: Xi Ruoyao <xry111@mengyan1223.wang>,
	"gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: [EXTERNAL] Re: Compiling GCC 11 for Windows targeting ARM on Linux
Date: Tue, 11 Jan 2022 11:09:34 +0000	[thread overview]
Message-ID: <CAH6eHdSz_pR7xGdPfG7DewPMb5McesmPtSF_PoAr5C9L10u4Fw@mail.gmail.com> (raw)
In-Reply-To: <VI1PR0402MB38539B8C96DD31D144AD9860CD519@VI1PR0402MB3853.eurprd04.prod.outlook.com>

On Tue, 11 Jan 2022 at 02:50, Thomas Sobczynski via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
>
> You need to install arm-none-eabi-gcc on Linux, because otherwise you
> won't be able to build libgcc for arm-none-eabi (note that "arm-none-
> eabi-gcc.exe", which is just compiled, can't run on Linux).  You may use
> "make all-gcc" and "make install-gcc" to skip libgcc, but a GCC build
> without libgcc is almost completely useless (such a build is only useful
> if you'll build libgcc manually later, or you are debugging GCC itself).
>
> --
> Xi Ruoyao <xry111@mengyan1223.wang>
> School of Aerospace Science and Technology, Xidian University
>
>
> Thank you, Xi, for pointing out the need for the native cross toolchain as well as clarifying the linker flags. I installed the native Linux toolchain for bare-metal ARM, removed my config file edits, and tried again to build for a Windows host targeting ARM.
>
> I am seeing a new error, but it seems to occur further in the build process, so I feel like I'm a step closer. More context around the error is pasted below.
>
> checking whether the arm-none-eabi-gcc     linker (/usr/lib/gcc/arm-none-eabi/9.2.1/../../../arm-none-eabi/bin/ld) supports shared libraries... yes
> checking dynamic linker characteristics... no
> checking how to hardcode library paths into programs... immediate
> checking for shl_load... configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
> make[1]: *** [Makefile:13331: configure-target-libstdc++-v3] Error 1
>
> I tried explicitly adding "--disable-shared" to the "configure" script parameters, so I'm confused about why I'm seeing "... supports shared libraries... yes".

Because the checks for dlopen are done whether or not you are building
.so files.

Adding --with-newlib will fix that error.

That's no longer necessary on the Git master branch, because I fixed
it yesterday, see https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103866

  parent reply	other threads:[~2022-01-11 11:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 16:47 Thomas Sobczynski
2022-01-10 17:16 ` Xi Ruoyao
2022-01-11  2:49   ` [EXTERNAL] " Thomas Sobczynski
2022-01-11  3:44     ` Thomas Sobczynski
2022-01-11  6:53       ` Xi Ruoyao
2022-01-11 11:19         ` Jonathan Wakely
2022-01-11 11:14       ` Jonathan Wakely
2022-01-12 18:39         ` Thomas Sobczynski
2022-01-12 19:09           ` Jonathan Wakely
2022-01-11 11:09     ` Jonathan Wakely [this message]
2022-01-10 17:24 ` Jonathan Wakely
2022-01-11  0:27   ` [EXTERNAL] " Thomas Sobczynski

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=CAH6eHdSz_pR7xGdPfG7DewPMb5McesmPtSF_PoAr5C9L10u4Fw@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tsobczynski@werfen.com \
    --cc=xry111@mengyan1223.wang \
    /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).