> -----Mensagem original-----
> De: news [mailto:news@...] Em nome de Duncan
> Enviada: quinta-feira, 8 de Dezembro de 2005 14:30
> Para: firstname.lastname@example.org
> Clemente Aguiar posted
> excerpted below, on Thu, 08 Dec 2005 12:02:31 +0000:
> > How can I solve this problem?<!DOCTYPE HTML PUBLIC
> "-//W3C//DTD HTML
> > 4.0 Transitional//EN"> <HTML><HEAD><TITLE>Mensagem</TITLE>
> First, please turn off HTML. Many on FLOSS (Free, Libre, and
> Open Source
> Software) type lists consider HTML posts the mark of spammers
> and malware authors, and may kill filter it or simply refuse
> to reply. I reply, but I make it a point of asking folks to
> please turn it off, and may not reply (and indeed, killfile)
> future posts if the HTML remains.
I am sorry, I use TEXT by default, I dont know how that one got away.
> > I did a new instalattion of Gentoo 2005.r1 (AMD64).
> ??? You mean 2005.0-r1, correct?
> > After the basic stage3 instalation, kernel compilation and reboot,
> > everything was fine. I then decided to recompile all:
> > Code:
> > emerge -e world
> > and I get an error when it gets to compile gcc
> > Code:
> > -Wold-style-definition -isystem ./include -fPIC -DHAVE_SYSLOG -g
> > -Wl,--version-script=libgcc/32/libgcc.map -o
> 32/libgcc_s.so.1.tmp -m32
> > libgcc/32/_muldi3.o libgcc/32/_negdi2.o libgcc/32/_lshrdi3.o
> -fPIC with -m32? To my knowledge, that's not a good
> combination. 64-bit requires -fPIC on some stuff (but it
> should be added by the ebuild where necessary, don't do it
> yourself), but -m32 indicates it's compiling the 32-bit stuff
> here, and that shouldn't get -fPIC, AFAIK.
I did NOT add any of the compilation flags myself (-fPIC or -m32).
> > Here is my emerge --info
> > Code:
> > Portage 188.8.131.52-r3 (default-linux/amd64/2005.1, gcc-3.4.4,
> > glibc-2.3.5-r2, 2.6.12-gentoo-r10 x86_64)
> > =================================================================
> > System uname: 2.6.12-gentoo-r10 x86_64 Intel(R) Xeon(TM) CPU 3.60GHz
> > ACCEPT_KEYWORDS="amd64"
> > AUTOCLEAN="yes"
> > CBUILD="x86_64-pc-linux-gnu"
> > CFLAGS="-O2 -march=nocona -pipe"
> OK, -fPIC isn't in your CFLAGS, so that isn't the problem. I
> wonder why it's adding it for 32-bit compilation? Someone
> else feel free to step in here, but that doesn't look at all
> right, to me. Perhaps a bug in the ebuild? If no one says
> -fPIC is supposed to be there for 32-bit, I'd consider filing
> a bug, as I'm /almost/ positive it shouldn't be there, and
> it's not in your cflags, so it's gotta be an issue with the ebuild.
> Duncan - List replies preferred. No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master." Richard
> Stallman in
So far nobody else said anything about this issue.
I am considering filling a bug. I am a newbie on these matters (never
filed a bug before).
How should I go about it?
What should I mention about the bug? (what is the bug)
email@example.com mailing list