From bug-octave-request at bevo dot che dot wisc dot edu Mon Nov 2 13:17:54 1998 Subject: Troubles compiling octave From: "Pascal A. Dupuis" To: bug-octave at bevo dot che dot wisc dot edu Date: Mon, 2 Nov 1998 13:17:58 -0600 (CST) Hello, I'm trying to compile octave on my i486 machine, where big compilations result in a segmentation fault in gcc every hour or every compilation, whichever is more problematic :-( Standard cure is to delete the lastly compiled file, and start back again. Usually, I succeed in compilign big packages this way. Unfortunately, it seems that there is a bug in one of octave Makefiles. If I restart a compilation, 'make' tries to rebuild liboctave/pic/*.o and src/pic/*.o before going further. As the compilation time is much higher than one hour, I have no hope to see it reachs the end :-( [BTW, gcc got SIG11. I tried everything in the SIG11-Howto, without any succes] Doing a 'make -d all 2>&1 | tee make.report', I got this : Considering target file `liboctave.so'. Considering target file `pic/Bounds.o'. Looking for an implicit rule for `pic/Bounds.o'. [...] Found dependency `Bounds.cc' as VPATH `../../liboctave/Bounds.cc' Found an implicit rule for `pic/Bounds.o'. Considering target file `../../liboctave/Bounds.cc'. File `../../liboctave/Bounds.cc' was considered already. Considering target file `pic'. Finished dependencies of target file `pic'. No need to remake target `pic'. [...] Finished dependencies of target file `pic/Bounds.o'. Dependency `pic' is newer than dependent `pic/Bounds.o'. [...] Must remake target `pic/Bounds.o' And so on... Platform : i486-pc-linux-glibc2, kernel 2.1.126, glibc-2.0.6, gcc-2.8.1, libstdc++-2.8.1.1, make 3.77, and octave-2.0.13. Further details upon request, and thanks for any help Pascal Dupuis -- feature, n: A surprising property of a program. Occasionaly documented. To call a property a feature sometimes means the author did not consider that case, and the program makes an unexpected, though not necessarily wrong response. See BUG. "That's not a bug, it's a feature!" A bug can be changed to a feature by documenting it.