From: Frank Schafer <frank.schafer@t-systems.cz>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Bug 80905
Date: Tue, 13 Sep 2005 15:24:38 +0200 [thread overview]
Message-ID: <1126617879.5910.42.camel@localhost.localdomain> (raw)
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. Donnie Berkholz replied 2005-02-10 with:
"Could you humor me and try with a vanilla kernel?"
My questions here: Does someone have a look at this? I think a not
installable Xorg is severe enough to mark it as CRITICAL.
Does someone know if it's worth a try with the vanilla and if vanilla
here means a really vanilla from kernel.org or if it's sufficient to get
the (too patched and thus not so vanilla) vanilla-sources.
Please be kind with me regarding to the fact that I'm posting here. On
the gentoo mailing list I get only replies like: "You probably have
faulty memory." If THIS would be the fact the bug would show up randomly
in different ebuilds or at least at different lines of code.
Thanks in advance for every hint
Frank
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2005-09-13 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 13:24 Frank Schafer [this message]
2005-09-13 13:43 ` [gentoo-dev] Bug 80905 Brian Harring
2005-09-13 13:52 ` Daniel Drake
2005-09-13 14:01 ` Ivan Yosifov
2005-09-13 14:14 ` Daniel Drake
2005-09-13 14:29 ` Frank Schafer
2005-09-14 3:23 ` Richard Fish
2005-09-13 14:15 ` Patrick Lauer
2005-09-14 14:45 ` Paul de Vrieze
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=1126617879.5910.42.camel@localhost.localdomain \
--to=frank.schafer@t-systems.cz \
--cc=gentoo-dev@lists.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