From: Mark Haverkamp <markh@osdl.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Weird... 2.6.9 kills FC2 gcc
Date: 18 Oct 2004 18:49:48 -0700 [thread overview]
Message-ID: <1098150587.1384.0.camel@peabody> (raw)
In-Reply-To: <4174697B.90306@pobox.com>
On Mon, 2004-10-18 at 18:10, Jeff Garzik wrote:
> The following appears in 2.6.9 release kernel, building with stock FC2
> gcc on x86, but does not appear in 2.6.9-final:
>
> > AS arch/i386/kernel/vsyscall.o
> > cc1: internal compiler error: Segmentation fault
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://bugzilla.redhat.com/bugzilla> for instructions.
> > make[1]: *** [arch/i386/kernel/vsyscall.o] Error 1
> > make: *** [arch/i386/kernel] Error 2
>
>
>
> This is 100% reproducible, at the same location (vsyscall), which is
> strange because vsyscall didn't change AFAICS.
>
> I'll build a gcc 3.4.2 without Fedora Core patches and see if the
> behavior persists.
>
> But in the meantime, if anybody else knows what line of code causes this
> segfault, please speak up :)
As an experiment, I commented out the include of init.h and replaced the
__INITDATA and __FINIT with the .section and .previous. It then
compiled OK.
Mark.
>
> Jeff
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Mark Haverkamp <markh@osdl.org>
next prev parent reply other threads:[~2004-10-19 1:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 1:10 Weird... 2.6.9 kills FC2 gcc Jeff Garzik
2004-10-19 1:49 ` Mark Haverkamp [this message]
2004-10-19 2:21 ` [PATCH] " Jeff Garzik
2004-10-19 3:31 ` Jeff Garzik
2004-10-19 4:15 ` Dmitry Torokhov
2004-10-19 6:23 ` Meelis Roos
2004-10-19 14:48 ` Mark Haverkamp
2004-10-19 14:52 ` Jeff Garzik
2004-10-19 6:31 ` Gene Heskett
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=1098150587.1384.0.camel@peabody \
--to=markh@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.