configure option ' --with-ld-shared' causes calling of 'yes' looping indefinitely.
|Reported by:||dreieck||Owned by:||warmerdam|
|Severity:||normal||Keywords:||build, compilation, ld-shared|
Description (last modified by )
When I compile gdal 2.1.1 on my arch linux system (64 bit) and I have the option
--with-ld-shared passed to
configure, at some point the process
yes runs for indefinite time and consumes all available CPU power. Compilation does not continue,
stdout outputs the same message over and over.
Looking at the output of the compilation, at some point the command
is issued where the compilation hang and looping output of
yes seems to occur.
yes loops, a look in a tree-like rendered
ps-output looks like (output of
ps -e --cumulative --forest --headers --lines 60 k +comm -o "pid=----PID,size,%mem,%cpu,args=COMMAND----"):
----PID SIZE %MEM %CPU COMMAND---- [...] 5438 2132 0.0 7.1 \_ /bin/bash -l 8356 540 0.0 0.2 | \_ /bin/sh ./build.sh 8358 2932 0.0 15.3 | \_ /usr/bin/bash /sbin/makepkg -f 3205 1372 0.0 7.3 | \_ make 5068 14352 0.2 1.9 | \_ make /var/abs/local/own/gdal-custom/src/gdal-2.1.1/libgdal.a /var/abs/local/own/gdal-custom/src/gdal-2.1.1/libgdal.so 5073 424 0.0 87.0 | \_ yes [...]
I use the following commands to build gdal (taken from the official Arch Linux PKGBUILD, and modified):
I attach the following additional information as files:
- The complete PKGBUILD to build the package in the way the error occurs,
- the log of
stderr(combined) when configuring and building the package that way,
- the log of
stderr(combined) when configuring and succesfully building the package without