From: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
To: Zack Weinberg <zackw@panix.com>,
GNU C Library <libc-alpha@sourceware.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: build-many-glibcs: powerpc-linux-gnu-soft configuration builds with hard float, link fails
Date: Tue, 21 May 2019 17:35:02 -0300 [thread overview]
Message-ID: <87mujfmtqh.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAKCAbMhozBC=7ae7BK-_ELNUCPFqMfwzVphGK7OSaTCBH1dEvg@mail.gmail.com>
Zack Weinberg <zackw@panix.com> writes:
> I'm seeing a build failure under build-many-glibcs for the
> powerpc-linux-gnu-soft configuration. The syndrome is that some (but
> not all) of the object files going into libc_pic.os are compiled with
> -mhard-float and so the final link of libc.so.6 blows up:
Is this happening after you apply your patch?
If so, please check if you removed the following line was removed from
sysdeps/powerpc/preconfigure:
with_fp_cond="!defined __NO_FPRS__"
This variable must be defined per configure.ac:
# A preconfigure script for a system that may or may not use fpu
# sysdeps directories sets this to a preprocessor conditional for
# whether to use such directories.
with_fp_cond=1
--
Tulio Magno
next prev parent reply other threads:[~2019-05-21 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 14:01 build-many-glibcs: powerpc-linux-gnu-soft configuration builds with hard float, link fails Zack Weinberg
2019-05-21 20:35 ` Tulio Magno Quites Machado Filho [this message]
2019-05-21 20:40 ` Zack Weinberg
2019-05-22 14:16 ` Zack Weinberg
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mujfmtqh.fsf@linux.ibm.com \
--to=tuliom@ascii.art.br \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=zackw@panix.com \
/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).