tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: libstdc++ dependency mis-detection in gcc packages?



On Tue 02 May 2023 at 12:55:46 +0200, Havard Eidnes wrote:
> and pkg_summary.gz for this says:
> 
> PKGNAME=gcc10-10.4.0
> ...
> PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so
> PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so.7
> PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so.7.28
> ...
> REQUIRES=/usr/lib/libstdc++.so.7
> ...
> 
> But ... is the last one accurate?  I suspect not.

For comparison, if I look in my own-built gcc10 in
/var/db/pkg/gcc10-10.4.0nb1/+BUILD_INFO I have

./+BUILD_INFO:PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so
./+BUILD_INFO:PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so.7
./+BUILD_INFO:PROVIDES=/usr/pkg/gcc10/lib/libstdc++.so.7.28

./+BUILD_INFO:REQUIRES=/usr/pkg/gcc10//lib/./libstdc++.so.7

and the PROVIDES lines match what I have in my pkg_summary.gz file.
The REQUIRES is missing from the summary in any variation.
So somehow this depends on how the package was built, it seems.

-Olaf.
-- 
___ "Buying carbon credits is a bit like a serial killer paying someone else to
\X/  have kids to make his activity cost neutral." -The BOFH    falu.nl@rhialto

Attachment: signature.asc
Description: PGP signature



Home | Main Index | Thread Index | Old Index