Re: bad package build of gcc10

[Greg Troxel <gdt%lexort.com@localhost>]

Greg Troxel <gdt%lexort.com@localhost> writes:

> Rooting around destdir, I found a file that references quadmath:
>
>   $ objdump -x work/.destdir/usr/pkg/gcc10/lib/libgfortran.so.5.0|egrep NEED\|RPATH
>   NEEDED               libquadmath.so.0
>   NEEDED               libm.so.0
>   NEEDED               libgcc_s.so.1
>   NEEDED               libc.so.12
>   RPATH                /usr/pkg/gcc10//lib/.:/usr/pkg/gcc10/lib/.:/usr/pkg/gcc10/lib:/usr/pkg/lib
>   VERNEED              0x0000000000017a98
>   VERNEEDNUM           0x0000000000000002
>
> and that seems to be the issue: //lib/. instead of /lib, leading to a
> REQUIRES that should have been a match to the PROVIDES and hence
> omittted.  Basically, the checking code is not using the same resolution
> rules that the dynamic linker does.

I am not entirely sure yet, but it is looking like

  building with -j1 ==> leads to a package without the bad REQUIRES
  building with -j12 ==> leads to a packaeg with the bad REQUIRES

could somebody else on netbsd-10 amd64 build gcc10 with -j12, and see if
the resulting package has the bad REQUIRES?

(I am building on a 12-core machine, i7-12700.  On a xen dom0 in
particular.)