On Sun, Feb 02, 2003 at 01:06:02AM +0100, Sundance wrote:
> I heard Richard Kilgore said:
>
> > If you get a seg fault while compiling qt or libkde because of bad
> > memory or a cpu overheat, I think you would get it when compiling
> > anything of any size.
>
> This is an often made and legitimate assumption, but it almost always
> ends up getting proven wrong.
>
> See this thread:
> http://marc.theaimsgroup.com/?l=gentoo-user&m=104334984122667&w=2
That looks convincing, but didn't the original post (which I no
longer have) say that it seg faulted while running libtool?
Somehow I doubt that particular step is terribly rigorous. But
maybe the C++ compilation heated the thing up and then it just
happened to fail while running libtool?
I'd say that if it happens at different places in the build each
time, it's a hardware problem, and if it happens at exactly the
same place each time, the problem is probably in QT or libtool.
Sound reasonable?
- richard
> Once more, Qt and KDE are *bitches* to compile. They're huge, they're in
> C++, and C++ compilation is a lot more CPU-intensive. They will often
> trigger temperature-caused crashes in computers that are otherwise hot
> but fine.
>
> So a good idea is generally to open the box (and possibly the window of
> your room as well if needed) during their compilation and see if it
> works better. Simple solution, always worth trying. :)
>
> -- S.
--
Richard Kilgore
[EMAIL PROTECTED]
--
[EMAIL PROTECTED] mailing list
