From: Joseph Myers <joseph@codesourcery.com>
To: Xianmiao Qu <cooper.qu@linux.alibaba.com>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [committed] C-SKY: Define SYSROOT_SUFFIX_SPEC.
Date: Fri, 20 Jan 2023 17:27:26 +0000 [thread overview]
Message-ID: <22262a2-6de-923b-c4d7-5e1a855934a1@codesourcery.com> (raw)
In-Reply-To: <20230113124319.75544-1-cooper.qu@linux.alibaba.com>
On Fri, 13 Jan 2023, Xianmiao Qu via Gcc-patches wrote:
> The earlier patch
> https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575418.html
> refine the way to generate sysroot suffix, but it can't find the
> right path for all CPUs. The SYSROOT_SUFFIX_SPEC should be defined
> to fix it.
I think this caused the build failures with build-many-glibcs.py shown by
my bot. SYSROOT_SUFFIX_SPEC should not be defined for a
--disable-multilib build; in such a build you can expect a single sysroot
without a suffix involved. Thus, you should put the SYSROOT_SUFFIX_SPEC
definition in a separate header only used if test "x${enable_multilib}" =
xyes (as in the config.gcc code removed in the older patch you refer to
above), or something similar.
https://sourceware.org/pipermail/libc-testresults/2023q1/010706.html
The error is:
/scratch/jmyers/glibc-bot/install/compilers/csky-linux-gnuabiv2/csky-glibc-linux-gnuabiv2/bin/ld: cannot find -lc: No such file or directory
(linking shared libgcc).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-01-20 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 12:43 Xianmiao Qu
2023-01-20 17:27 ` Joseph Myers [this message]
2023-01-25 9:41 ` Cooper Qu
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=22262a2-6de-923b-c4d7-5e1a855934a1@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=cooper.qu@linux.alibaba.com \
--cc=gcc-patches@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).