Re: [gentoo-dev] Xfree-4.2.0-r9

[Spider]

cd
//var/tmp/portage/xfree-4.2.0-r9/work/xc/programs/Xserver/PEX5/ddpex/mi
/level1

source /etc/make.conf
export CFLAGS="${CFLAGS} -Wall"
make 

This will show you some more info on what went wrong. 

but yes, I've reported it, though I don't like GNATS and probably didn't
get it all right...
//Spider

begin  quote
On Sat, 01 Jun 2002 11:40:18 +0200
Marcel Martin <mmar@×××××××.de> wrote:

> On Saturday 01 June 2002 12:07, Jack Morgan wrote:
> > I'm having trouble compiling Xfree-4.2.0-r9. I've attached the tail
> > of the log. Any pointers would be appreciated.
>
> I had the same (or at least very similar) problem compiling
> xfree-4.2.0-r9 with gcc 3.1. I think doing one of the following helped
> me (don't remember very well...):
>
> - change your CFLAGS in /etc/make.conf to do less "agressive"
> optimizations. In my case, changing "-march=athlon -O3" to
> "-march=i686 -O3" worked. You might need to lower "-O3" as well. Then
> emerge the entire xfree again.
>
> - faster solution (that's what I did): go into the
> /var/tmp/portage/xfree-4.2.0-r9/work/xc/programs/Xserver/PEX5/ddpex/m
> i/level1 directory, then run make manually with a different CFLAGS
> setting. I suppose something in the line of
> make CFLAGS="-march=i686 -O2"
> should work. If this directory compiles successfully, you can then run
> ebuild /usr/portage/x11-base/xfree/xfree-4.2.0-r9.ebuild compile
> install \ qmerge
> (Should be in one line, but it's not because of automatic word-wrap.)
> This should compile the rest of xfree and install and merge it as
> "emerge" would have done.
>
> BTW: Has anyone reported the internal compiler error that's in Jack's
> logfiles?
>
> > Thanks,
>
> Hope I could help a bit,
> Marcel
> --
>  . .
> / V / Marcel Martin   Bielefeld
> \   \ mmar@×××××××.de Germany
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@g.o
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev


--
begin  .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end