Bug#1042029: graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]

2023-12-14 Thread Santiago Vila

tags 1042029 - patch
thanks

El 29/10/23 a las 22:46, Jerome BENOIT escribió:

Please keep in mind that graph-tool is scientific tool for big-data,
so the choice of the optimization option is relevant.


Fair enough. I'm removing the patch tag accordingly.


I downgraded the severity to normal as this issue is before all
a resource issue. I have no problem to build it on a 24 CPUs amd64 box
with 64 GB of RAM (and with ~ 4/3 of 64 GB of SWAP).


Well, let me describe our build environments:

Lucas Nussbaum usually starts a bunch of machines of type
t3.2xlarge from AWS, which have 8 CPUs and 32 GB of RAM,
then have three "workers" in each of them building packages
in parallel (so each package has 10.66 GB of RAM to build
on average, but since lots of them build with a lot less
than that, it is very rare that a package may not be built
because of lack of memory).

I do it differently: I start machines with 4GB, 8GB or 16GB
and build a single package at a time. Because I monitor
/proc/meminfo during build and collect the data, I know
which packages build with only 4GB and which packages
need 8 GB or 16 GB. For all the 35000 packages in trixie,
I have never seen any of them requiring 32 GB so far.

So, if it were the case that this package needs 64 GB of RAM
to build (which honestly I don't think it's really the case),
that would be a problem for us, because that would force
to do our QA work differently, just for a single package.

In other words, if it were the case that this package needs
so much memory, requesting some change (not necessarily
removing the -O3 thing) would be legitimate, in my opinion.

In this case, I have successful build logs which were made
after I said that it failed for me, so it is still possible
that there was a compiler bug or something suboptimal
in the build chain which has been fixed since then.

So, I am adding to my todo list to check this package again
in both the environment by Lucas and my own one.

(Please Cc me and Lucas on replies, messages which are just
sent to the bug address are never forwarded to the bug
submitters or casual participants).

Thanks.



Bug#1042029: graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]

2023-10-29 Thread Jerome BENOIT

Hi all,
I downgraded the severity to normal as this issue is before all
a resource issue. I have no problem to build it on a 24 CPUs amd64 box
with 64 GB of RAM (and with ~ 4/3 of 64 GB of SWAP).
Please keep in mind that graph-tool is scientific tool for big-data,
so the choice of the optimization option is relevant.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1042029: graph-tool: FTBFS: collect2: fatal error: ld terminated with signal 9 [Killed]

2023-07-25 Thread Lucas Nussbaum
Source: graph-tool
Version: 2.45+ds-10
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230724 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> /bin/bash ./libtool  --tag=CXX   --mode=link g++ -std=gnu++17  -fopenmp -O3 
> -fvisibility=default -fvisibility-inlines-hidden -Wno-deprecated -Wall 
> -Wextra -ftemplate-backtrace-limit=0 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -module -avoid-version -export-dynamic -no-undefined 
> -Wl,-E -Wl,--as-needed -Wl,-z,relro -Wl,-z,now -o libgraph_tool_util.la 
> -rpath /usr/lib/python3.11/dist-packages/graph_tool/util 
> src/graph/util/graph_search.lo src/graph/util/graph_util_bind.lo 
> -L/usr/lib/x86_64-linux-gnu -lpython3.11 -L/usr/lib/x86_64-linux-gnu 
> -lboost_iostreams -lboost_python311 -lboost_regex -lboost_context 
> -lboost_coroutine -lexpat-lgmp -lgmp 
> libtool: link: g++  -fPIC -DPIC -shared -nostdlib 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/13/crtbeginS.o  
> src/graph/util/.libs/graph_search.o src/graph/util/.libs/graph_util_bind.o   
> -L/usr/lib/x86_64-linux-gnu -lpython3.11 -lboost_iostreams -lboost_python311 
> -lboost_regex -lboost_context -lboost_coroutine -lexpat -lgmp 
> -L/usr/lib/gcc/x86_64-linux-gnu/13 
> -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/13/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/../lib -L/usr/lib/gcc/x86_64-linux-gnu/13/../../.. 
> -lstdc++ -lm -lc -lgcc_s /usr/lib/gcc/x86_64-linux-gnu/13/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/13/../../../x86_64-linux-gnu/crtn.o  -fopenmp 
> -O3 -g -O2 -fstack-protector-strong -Wl,-E -Wl,--as-needed -Wl,-z -Wl,relro 
> -Wl,-z -Wl,now   -fopenmp -Wl,-soname -Wl,libgraph_tool_util.so -o 
> .libs/libgraph_tool_util.so
> libtool: link: ( cd ".libs" && rm -f "libgraph_tool_util.la" && ln -s 
> "../libgraph_tool_util.la" "libgraph_tool_util.la" )
> collect2: fatal error: ld terminated with signal 9 [Killed]
> compilation terminated.
> make[2]: *** [Makefile:3339: libgraph_tool_inference.la] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/24/graph-tool_2.45+ds-10_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230724;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230724=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.