public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
* Bootstrap build failure on Linux
@ 2015-10-24 17:07 Damian Rouson
  2015-10-24 17:15 ` Steve Kargl
  2015-10-24 17:21 ` Thomas Koenig
  0 siblings, 2 replies; 6+ messages in thread
From: Damian Rouson @ 2015-10-24 17:07 UTC (permalink / raw)
  To: GNU GFortran

All,

Could anyone provide guidance regarding the error message below from an attempt to build the latest trunk from source on Linux (Lubuntu)?  This has been happening for several days even though the exact same steps worked as recently as 28 September and still work on OS X.  My build steps are in lines 82-87 of the following bash script: 

https://github.com/sourceryinstitute/opencoarrays/blob/master/install_prerequisites/buildgcc

which I created in hopes of saving OpenCoarrays users the time of figuring out the build process themselves.  Any useful suggestions for improving the script are welcome.

Damian 




/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./prev-gcc/xg++ -B/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./prev-gcc/ -B/opt/gnu/6.0/x86_64-pc-linux-gnu/bin/ -nostdinc++ -B/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs -B/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs  -I/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu  -I/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/include  -I/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk/libstdc++-v3/libsupc++ -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs -no-pie   -g -O2 -DIN_GCC     -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common  -DHAVE_CONFIG_H -static-libstdc++ -static-libgcc  -o cc1plus \
	      cp/cp-lang.o c-family/stub-objc.o cp/call.o cp/decl.o cp/expr.o cp/pt.o cp/typeck2.o cp/class.o cp/decl2.o cp/error.o cp/lex.o cp/parser.o cp/ptree.o cp/rtti.o cp/typeck.o cp/cvt.o cp/except.o cp/friend.o cp/init.o cp/method.o cp/search.o cp/semantics.o cp/tree.o cp/repo.o cp/dump.o cp/optimize.o cp/mangle.o cp/cp-objcp-common.o cp/name-lookup.o cp/cxx-pretty-print.o cp/cp-cilkplus.o cp/cp-gimplify.o cp/cp-array-notation.o cp/lambda.o cp/vtable-class-hierarchy.o cp/constexpr.o cp/cp-ubsan.o cp/constraint.o cp/logic.o attribs.o incpath.o c-family/c-common.o c-family/c-cppbuiltin.o c-family/c-dump.o c-family/c-format.o c-family/c-gimplify.o c-family/c-indentation.o c-family/c-lex.o c-family/c-omp.o c-family/c-opts.o c-family/c-pch.o c-family/c-ppoutput.o c-family/c-pragma.o c-family/c-pretty-print.o c-family/c-semantics.o c-family/c-ada-spec.o c-family/c-cilkplus.o c-family/array-notation-common.o c-family/cilk.o c-family/c-ubsan.o i386-c.o glibc-c.o cc1plus-checksum.o libbackend.a main.o libcommon-target.a libcommon.a ../libcpp/libcpp.a ../libdecnumber/libdecnumber.a libcommon.a ../libcpp/libcpp.a   ../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a  -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./isl/.libs  -lisl -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./gmp/.libs -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./mpfr/.libs -L/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/./mpc/src/.libs -lmpc -lmpfr -lgmp -rdynamic -ldl  -L./../zlib -lz
collect2: fatal error: ld terminated with signal 9 [Killed]
compilation terminated.
make[3]: *** [cc1plus] Error 1
make[3]: *** Waiting for unfinished jobs....
rm cpp.pod gcov.pod gcov-tool.pod gpl.pod gfortran.pod fsf-funding.pod gfdl.pod gcc.pod
make[3]: Leaving directory `/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build/gcc'
make[2]: *** [all-stage3-gcc] Error 2
make[2]: Leaving directory `/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build'
make[1]: *** [stage3-bubble] Error 2
make[1]: Leaving directory `/home/rouson/Desktop/Code/opencoarrays/install_prerequisites/trunk-build'
make: *** [bootstrap] Error 2


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bootstrap build failure on Linux
  2015-10-24 17:07 Bootstrap build failure on Linux Damian Rouson
@ 2015-10-24 17:15 ` Steve Kargl
  2015-10-24 17:18   ` Damian Rouson
  2015-10-24 17:21 ` Thomas Koenig
  1 sibling, 1 reply; 6+ messages in thread
From: Steve Kargl @ 2015-10-24 17:15 UTC (permalink / raw)
  To: Damian Rouson; +Cc: GNU GFortran

On Sat, Oct 24, 2015 at 10:07:37AM -0700, Damian Rouson wrote:
> 
> Could anyone provide guidance regarding the error message below
> from an attempt to build the latest trunk from source on Linux
> (Lubuntu)?  This has been happening for several days even though the exact same steps worked as recently as 28 September and still work on OS X.  My build steps are in lines 82-87 of the following bash script: 
> 
> https://github.com/sourceryinstitute/opencoarrays/blob/master/install_prerequisites/buildgcc
> 
> which I created in hopes of saving OpenCoarrays users the time of figuring out the build process themselves.  Any useful suggestions for improving the script are welcome.
> 
> Damian 
> 

Are you doing a parallel build (e.g., make -j 4)?
If yes, the first step in debug is to not use
the -j option.

-- 
Steve

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bootstrap build failure on Linux
  2015-10-24 17:15 ` Steve Kargl
@ 2015-10-24 17:18   ` Damian Rouson
  0 siblings, 0 replies; 6+ messages in thread
From: Damian Rouson @ 2015-10-24 17:18 UTC (permalink / raw)
  To: Steve Kargl; +Cc: GNU GFortran


> On Oct 24, 2015, at 10:15 AM, Steve Kargl <sgk@troutmask.apl.washington.edu> wrote:
> 
> Are you doing a parallel build (e.g., make -j 4)?
> If yes, the first step in debug is to not use
> the -j option.
> 

Thanks for the quick reply!  Yes, I was using "-j 4”.  I tried a simple “make” with no -j argument immediately afterward (without deleting anything) and that produced the same result if I recall correctly, but I’ll launch a fresh build with no -j argument now and report the result.

Damian


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bootstrap build failure on Linux
  2015-10-24 17:07 Bootstrap build failure on Linux Damian Rouson
  2015-10-24 17:15 ` Steve Kargl
@ 2015-10-24 17:21 ` Thomas Koenig
  2015-10-24 18:21   ` Damian Rouson
  1 sibling, 1 reply; 6+ messages in thread
From: Thomas Koenig @ 2015-10-24 17:21 UTC (permalink / raw)
  To: Damian Rouson, GNU GFortran

Am 24.10.2015 um 19:07 schrieb Damian Rouson:

> collect2: fatal error: ld terminated with signal 9 [Killed]

Signal 9 is SIGKILL, which unconditionally kills a process.
It is not part of the normal boot process.

SIGKILL is something that is sent by the Linux OOM (Out Of Memory)
killer, so this is something that might have happened.  If so,
I would expect a corresponding message in the log file.

As to why - either your system was low on memory due to other reasons,
or there was a problem with the build which manifested itself by
using excessive memory during linking.

HTH

	Thomas

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bootstrap build failure on Linux
  2015-10-24 17:21 ` Thomas Koenig
@ 2015-10-24 18:21   ` Damian Rouson
  2015-10-25  2:16     ` Damian Rouson
  0 siblings, 1 reply; 6+ messages in thread
From: Damian Rouson @ 2015-10-24 18:21 UTC (permalink / raw)
  To: Thomas Koenig; +Cc: GNU GFortran


> On Oct 24, 2015, at 10:21 AM, Thomas Koenig <tkoenig@netcologne.de> wrote:
> 
> SIGKILL is something that is sent by the Linux OOM (Out Of Memory)
> killer, so this is something that might have happened.  If so,
> I would expect a corresponding message in the log file.
> 
> As to why - either your system was low on memory due to other reasons,
> or there was a problem with the build which manifested itself by
> using excessive memory during linking.
> 

Thanks!  My Linux build is inside a virtual machine so the memory limitation of the virtual machine would explain the difference between Linux and OS X.  I’m now doing a a serial build and monitoring the memory usage via the “top” command.  I see cc1plus going as high as 35% of the memory.  If all four threads tried to access that much memory at once, that could exhaust the memory. Possibly something in the build process requires more memory now than it used to require.


Damian

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Bootstrap build failure on Linux
  2015-10-24 18:21   ` Damian Rouson
@ 2015-10-25  2:16     ` Damian Rouson
  0 siblings, 0 replies; 6+ messages in thread
From: Damian Rouson @ 2015-10-25  2:16 UTC (permalink / raw)
  To: Thomas Koenig; +Cc: GNU GFortran


> On Oct 24, 2015, at 11:21 AM, Damian Rouson <damian@sourceryinstitute.org> wrote:
> 
> Thanks!  My Linux build is inside a virtual machine so the memory limitation of the virtual machine would explain the difference between Linux and OS X.  I’m now doing a a serial build and monitoring the memory usage via the “top” command.  

My serial build completed successfully.  Thanks for the assistance.

D

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2015-10-25  2:16 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-24 17:07 Bootstrap build failure on Linux Damian Rouson
2015-10-24 17:15 ` Steve Kargl
2015-10-24 17:18   ` Damian Rouson
2015-10-24 17:21 ` Thomas Koenig
2015-10-24 18:21   ` Damian Rouson
2015-10-25  2:16     ` Damian Rouson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).