Hello,
this bug is from 2005-02-05. It was reported again (in this thread)
2005-02-10. I hit the same behavior 2005-09-08.
internal compiler error: segmentation fault during emerge Xorg
The bug is simply reproducible (emerge Xorg) at the same line of code.
The bug is still marked as NEW.
On Tue, 2005-09-13 at 15:14 +0100, Daniel Drake wrote:
Ivan Yosifov wrote:
On Tue, 2005-09-13 at 14:52 +0100, Daniel Drake wrote:
are running vesafb-tng and have =1GB RAM then try
turning off vesafb-tng
Why ?
Actually, this shouldn't matter, as this only occurs with 64gb
Hi,
It took me the whole weekend to build a stage1 system. (Took 5 hours
during last night ;)
I had to work around the bugs this way:
scripts/bootscripts.sh
emerge --oneshot --nodeps autoconf
emerge --oneshot --nodeps autoconf-wrapper
This solved the problem, that automake installed during
On Mon, 2005-09-12 at 14:47 +0200, Henrik Brix Andersen wrote:
On Mon, 2005-09-12 at 14:41 +0200, Frank Schafer wrote:
During ``emerge system'' python-fchksum failed with a not existing
i386-pc-linux-gnu-gcc on a i686 system. I don't know if python hard
codes the native compiler to the one
On Mon, 2005-09-12 at 08:01 -0500, Brian Harring wrote:
On Mon, Sep 12, 2005 at 02:13:43PM +0200, Frank Schafer wrote:
Hi,
I fought with a stage1 install during this weekend. Today in the morning
I succeeded.
I had to move a lot in /var/log/portage.
For the content
