[Pkg-javascript-devel] Bug#1066409: Linker fails to find libraries in unstable but succeeds in testing

[Jérémy Lal]

Le ven. 15 mars 2024 à 11:17, Jérémy Lal <kapouer at melix.org> a écrit :

>
>
> Le ven. 15 mars 2024 à 08:46, Jochen Sprickerhof <jspricke at debian.org> a
> écrit :
>
>> Hi Andreas,
>>
>> * Andreas Tille <andreas at an3as.eu> [2024-03-15 07:31]:
>> >Hi,
>> >
>> >thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one
>> >package of the R pkg team is affected by some strange linker issue
>> >
>> >#1066409 r-cran-v8: FTBFS: ld: cannot find -lv8: No such file or
>> directory
>> >which boils down to[1]
>> >
>> >g++ -std=gnu++17 -shared -L/usr/lib/R/lib -Wl,-z,relro -o V8.so
>> RcppExports.o bindings.o -lv8 -lv8_libplatform -L/usr/lib/R/lib -lR
>> >/usr/bin/ld: cannot find -lv8: No such file or directory
>> >/usr/bin/ld: cannot find -lv8_libplatform: No such file or directory
>> >
>> >The Build-Depends libnode-dev provides both libraries and when I try to
>> >build the package under testing all is fine.  Is there any linker issue
>> >involved that might be introduced in unstable?
>>
>> I guess that's the same as #1066399.
>>
>> libnode-dev:
>> libv8.so -> libnode.so
>> libnode.so -> libnode.so.108t64
>>
>> But libnode.so.108t64 does not exist
>>
>
> That's fixed in nodejs 18.19.1+dfsg-5
>

rejected, I forgot to not do a source upload. Rebuilding...

Instead of suffixing the soname (not compatible with node's toolchain) I
> just bumped the soname number to 109,
> while node 20 has 115 so there won't be any conflict.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20240315/fc1c772c/attachment.htm>