From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: linux-mips@linux-mips.org
Subject: Re: mips linux glibc-2.3.3 build - Assembler errors in rtld.c
Date: Tue, 5 Oct 2004 22:40:08 +0200 [thread overview]
Message-ID: <20041005204008.GU5033@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.58L.0410052114230.26193@blysk.ds.pg.gda.pl>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
On Tue, 2004-10-05 21:15:14 +0100, Maciej W. Rozycki <macro@linux-mips.org>
wrote in message <Pine.LNX.4.58L.0410052114230.26193@blysk.ds.pg.gda.pl>:
> On Tue, 5 Oct 2004, Jan-Benedict Glaw wrote:
> > > > Also, you might have to pass -fno-unit-at-a-time to gcc 3.4. (at
> > > > least glibc 2.3.2 requires it).
> > >
> > > Which is also fixed in the CVS. ;-)
> >
> > So that inline mess is also gone? Find... Or is that about a different
> > thing?
>
> Could you please elaborate? What current glibc does is adding
> -fno-unit-at-a-time where appropriate.
Some weeks ago, I had a build error (gcc+glibc head) which was because
of some function being first forced to be inline, then it's address was
taken... Didn't work :-)
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
fuer einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-05 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-05 9:50 mips linux glibc-2.3.3 build - Assembler errors in rtld.c T. P. Saravanan
2004-10-05 10:16 ` Atsushi Nemoto
2004-10-05 10:53 ` Maciej W. Rozycki
2004-10-05 12:17 ` Jan-Benedict Glaw
2004-10-05 20:15 ` Maciej W. Rozycki
2004-10-05 20:40 ` Jan-Benedict Glaw [this message]
2004-10-07 4:26 ` T. P. Saravanan
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=20041005204008.GU5033@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linux-mips@linux-mips.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