From: Marcel Martin <mmar@freenet.de>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Xfree-4.2.0-r9
Date: Sat, 01 Jun 2002 11:40:18 +0200 [thread overview]
Message-ID: <200206011140.18453.mmar@freenet.de> (raw)
In-Reply-To: <20020601100739.GA2086@c3p0.bonyari.com>
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/mi/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@freenet.de Germany
next prev parent reply other threads:[~2002-06-01 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 10:07 [gentoo-dev] Xfree-4.2.0-r9 Jack Morgan
2002-06-01 1:41 ` Spider
2002-06-01 9:40 ` Marcel Martin [this message]
2002-06-01 13:00 ` Spider
2002-06-02 22:14 ` Jack Morgan
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=200206011140.18453.mmar@freenet.de \
--to=mmar@freenet.de \
--cc=gentoo-dev@gentoo.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