From: William ML Leslie <william.leslie.ttg@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Building a cross compiler fails due to hardcoding host=target in gcc/Makefile.in
Date: Fri, 16 Oct 2020 23:39:03 +1100 [thread overview]
Message-ID: <CAHgd1hHmigCxsgG3AmsQskwYNkwbZMz31cXLnydN2CQVxfazgA@mail.gmail.com> (raw)
Greetings,
Please keep me CC'd as I'm not subscribed.
I've been trying to build a cross compilation toolchain (for a new OS)
and ran into a confusing error while building gcc 10.2.0. While
building libgcc, it fails running libgcc/config.host as it gets passed
my target instead of the actual host. I traced this back to the root
Makefile.in, for which the `configure-target-libgcc` rule ends with:
CONFIG_SITE=no-such-file $(SHELL) \
$$s/$$module_srcdir/configure \
--srcdir=$${topdir}/$$module_srcdir \
$(TARGET_CONFIGARGS) --build=${build_alias} --host=${target_alias} \
--target=${target_alias} \
|| exit 1
This is probably someone trying to be helpful when building a Canadian
Cross (host == target), however there is already a host_alias variable
defined at the very top of `Makefile.in`. When using a traditional
cross compiler, the host is equal to the build machine; but the
makefile ignores this case.
Have I missed something, or should I send a patch for this?
Snippet of make output where I hit this:
Checking multilib configuration for libgcc...
mkdir -p -- i386-unknown-capros/libgcc
Configuring in i386-unknown-capros/libgcc
...
checking for target glibc version... 0.0
*** Configuration i386-unknown-capros not supported
Makefile:12629: recipe for target 'configure-target-libgcc' failed
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory '/extra/wleslie/xenv2/build/gcc-10.2.0/build-capros'
Makefile:954: recipe for target 'all' failed
make: *** [all] Error 2
--
William Leslie
Q: What is your boss's password?
A: "Authentication", clearly
Notice:
Likely much of this email is, by the nature of copyright, covered
under copyright law. You absolutely MAY reproduce any part of it in
accordance with the copyright law of the nation you are reading this
in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without
prior contractual agreement.
next reply other threads:[~2020-10-16 12:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 12:39 William ML Leslie [this message]
2020-10-16 13:18 ` William ML Leslie
2020-10-17 11:59 ` William ML Leslie
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=CAHgd1hHmigCxsgG3AmsQskwYNkwbZMz31cXLnydN2CQVxfazgA@mail.gmail.com \
--to=william.leslie.ttg@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).