Hi,

Marius Bakke <[email protected]> skribis:

> Ludovic Courtès <[email protected]> writes:
>
>> Marius Bakke <[email protected]> skribis:
>>
>>> I suggest we 'freeze' core-updates next weekend and start working on
>>> merging it.  It has been sitting idle for way too long already!
>>
>> +1!
>
> The weekend is here already!  But we are still missing glibc 2.29, so I
> suggest we postpone the freeze a bit.

Should we?  Attached is my current WIP for glibc 2.29, where Python now
fails to build with:

--8<---------------cut here---------------start------------->8---
LD_LIBRARY_PATH=/tmp/guix-build-python-minimal-3.7.3.drv-0/Python-3.7.3 CC='gcc 
-pthread' LDSHARED='gcc -pthread -shared 
-Wl,-rpath=/gnu/store/wxw0wbizbaiha0bisrqsdzg1ggf7kndc-python-minimal-3.7.3/lib 
  ' OPT='-DNDEBUG -g -fwrapv -O3 -Wall'        _TCLTK_INCLUDES='' 
_TCLTK_LIBS=''       ./python -E ./setup.py  build

[...]

libgcc_s.so.1 must be installed for pthread_cancel to work
libgcc_s.so.1 must be installed for pthread_cancel to work
libgcc_s.so.1 must be installed for pthread_cancel to work
/gnu/store/r28awwz5vvkn5fqfv8nww6wkxis1d1vs-bootstrap-binaries-0/bin/sh: line 
9:  9025 Aborted                 
LD_LIBRARY_PATH=/tmp/guix-build-python-minimal-3.7.3.drv-0/Python-3.7.3 CC='gcc 
-pthread' LDSHARED='gcc -pthread -shared 
-Wl,-rpath=/gnu/store/wxw0wbizbaiha0bisrqsdzg1ggf7kndc-python-minimal-3.7.3/lib 
  ' OPT='-DNDEBUG -g -fwrapv -O3 -Wall' _TCLTK_INCLUDES='' _TCLTK_LIBS='' 
./python -E ./setup.py $quiet build
make: *** [Makefile:626: sharedmods] Error 134
--8<---------------cut here---------------end--------------->8---

It looks like libgcc_s.so is not in the RUNPATH of ‘python’.  We
explicitly fix it in ‘gcc’ but here it’s:

      ("gcc-wrapper" . 
"/gnu/store/nidn7vgqr488iwmar9wan1gg8y6c399j-gcc-mesboot-wrapper-4.7.4")
      ("gcc" . "/gnu/store/7fpm7qm8n4wa7frgv13j9jrbcpwrxr99-gcc-mesboot-4.9.4")

and I’m not sure how to fix it.

(It’s surprising there are two distinct versions here.)

> There are also many TODOs and XXXs that mention rebuild cycles, now is
> the time to fix those!

Indeed!  I’ll take a look.

Thanks,
Ludo’.

Reply via email to