From: Zack Weinberg <zackw@panix.com>
To: Tulio Magno Quites Machado Filho <tuliom@ascii.art.br>
Cc: 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: Wed, 22 May 2019 10:16:18 -0400 [thread overview]
Message-ID: <CAKCAbMgoNaR8GUPB9yP870kELfa29CBVqBsqezcffHTyiLvyuA@mail.gmail.com> (raw)
In-Reply-To: <CAKCAbMiY4tsvJv+Uqh63SfFsd-7gmBFhGQFrtqNsM=DkApnJ8g@mail.gmail.com>
On Tue, May 21, 2019 at 4:40 PM Zack Weinberg <zackw@panix.com> wrote:
> On Tue, May 21, 2019 at 4:35 PM Tulio Magno Quites Machado Filho
> <tuliom@ascii.art.br> wrote:
> > 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__"
>
> Aha, yes, that might be the problem. I will restore that line,
> retest, and report back.
This was indeed the problem. I have posted a revised patch for the
removal of the SPE subarchitecture from glibc. Tulio, you may get two
copies because I fat-fingered the git send-email operation, sorry
about that.
zw
prev parent reply other threads:[~2019-05-22 14:16 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
2019-05-21 20:40 ` Zack Weinberg
2019-05-22 14:16 ` Zack Weinberg [this message]
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=CAKCAbMgoNaR8GUPB9yP870kELfa29CBVqBsqezcffHTyiLvyuA@mail.gmail.com \
--to=zackw@panix.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=tuliom@ascii.art.br \
/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).