Re: compilation problem 0.9.14

On 10/8/05, Valter Toffolo <[email protected]> wrote:
> 2005/10/8, Laurent Malvert <[email protected]>:
> > Hi
> >
> >
> > I've got a compilation problem with fluxbox 0.9.14 on a NetBSD 2.0
> > with either gcc-3.3, 3.4 or 4.0.2
> >
> > everything goes fine until I reach this line during the compilation process:
> >
> > if g++ -DHAVE_CONFIG_H -I. -I. -I..  -I./FbTk   -O3
> > -I/usr/X11R6/include -DSHAPE  -DXTHREADS -I/usr/pkg/include
> > -I/usr/pkg/include/freetype2 -I/usr/X11R6/include   -MT fluxbox.o -MD
> > -MP -MF ".deps/fluxbox.Tpo" -c -o fluxbox.o fluxbox.cc; \
> > then mv -f ".deps/fluxbox.Tpo" ".deps/fluxbox.Po"; else rm -f
> > ".deps/fluxbox.Tpo"; exit 1; fi
> >
> as you've aready tried several gcc versions, i assume the error is
> always in this line....
> >
> > which outputs a nice:
> > fluxbox.cc: In constructor `Fluxbox::Fluxbox(int, char**, const char*, const
> >    char*)':
> > fluxbox.cc:414: internal compiler error: Segmentation fault
> >
> > (this is the gcc 4.0.2 error output, it's quite similar with other versions)
> >
> >
> > anyone faced this problem before ?
> >
> well.... this may sound stupid, but here it goes.. i've already got
> "internal compiler error" more than once, on different machines, and
> the problem was always memory. this might not be the case, specially
> because the error occurs always compiling the same file, and in the
> same line... but that's just a guess.

thanks, I might have a look at this possibility.
but that's really weird because it does the same on several computers
with the same configuration.


> > never had any problems compiling any other fluxbox sources until
> > 0.9.14, therefore I was wondering from what the problem could come
> > from.
> >
> that's weird, but if the problem is really memory, maybe it got
> screwed up just before trying to compile it. in my case, i had an
> almost stable system, and just found out i had memory problems when i
> tried to compile a kernel. it's a quick test, as compiling a kernel
> requires a lot of memory r/w... if it fails, you can try memtest86...
> if not, probably my guess is wrong.

I don't have administrator access on these computers but I'll check it
eventually, it sounds to me like your guess could be good, I'll try to
check this as soon as I can
and if it still doesn't work, well, I guess I could still cross
compile it on another computer.

thanks.

--
Laurent Malvert [[email protected]]


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl