From: "Enlight" <enlight@bentonrea.com>
To: "Catalin BOIE" <util@ns2.deuroconsult.ro>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Problem - See attached dmesg dump
Date: Wed, 29 Jan 2003 17:57:28 -0800 [thread overview]
Message-ID: <001401c2c802$f266ac20$0101a8c0@localdomain> (raw)
In-Reply-To: <Pine.LNX.4.33.0301281419510.10512-100000@hosting.rdsbv.ro>
I did test memory and found no problems.
I regressed to kernel-2.4.8 and gcc-2.96 and was able to successfully build
XFCE without a glitch.
I now plan to progress to kernel-2.4.19, which I have, and attempt build
with gcc-2.96. If that works or fails I will progress to kernel-2.4.20.
After that I will bump gcc up and see what happens. I suspect gcc really
works the system with recursive system calls and memory paging.
I tried ksymoops and it ran soooooo sloooooow. I am not sure I have it
right and I was not able to get results. I just need to study more I guess.
I don't do this for a living so I beg your forgiveness and appreciate the
input and patience from everybody.
Jerry DeLisle (enlight)
----- Original Message -----
From: "Catalin BOIE" <util@ns2.deuroconsult.ro>
To: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Cc: "Enlight" <enlight@bentonrea.com>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Sent: Tuesday, January 28, 2003 4:21 AM
Subject: Re: Problem - See attached dmesg dump
> > > While running make to build xfce3.8.18 I get an internal gcc error
> > > segmentation fault. Also got similar error running rpmdrake.
Needless to
> > > say I can't finish the build.
>
> I get this error too. gcc 3.2.1 seg faults a lot when compiling a kernel.
> Motherboard: gigabyte 7avx (I think) K400.
> Under Windows 2000 (don't ask why, please...) no BSOD.
>
> >
> > Send reports about vendor kernels to the vendor concerned. Vendors add
various
> > custom changes to the base kernel, they also know a lot more about the
patterns
> > of problems their users see
> >
> > -
> > 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/
> >
>
> ---
> Catalin(ux) BOIE
> catab@deuroconsult.ro
>
>
prev parent reply other threads:[~2003-01-30 1:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-27 5:36 Enlight
2003-01-28 11:50 ` Alan Cox
2003-01-28 12:21 ` Catalin BOIE
2003-01-29 8:30 ` Horst von Brand
2003-01-29 8:57 ` Catalin BOIE
2003-01-30 17:55 ` Bruce Harada
2003-01-31 7:11 ` Catalin BOIE
2003-01-30 1:57 ` Enlight [this message]
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='001401c2c802$f266ac20$0101a8c0@localdomain' \
--to=enlight@bentonrea.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=util@ns2.deuroconsult.ro \
/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
all inboxes | Powered by JetHome®