NSPR version check in configure script and pkg-config differ
Categories
(NSS :: Build, defect, P5)
Tracking
(Not tracked)
People
(Reporter: pmenzel+bugzilla.mozilla.org, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [nss-qm])
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0
Steps to reproduce:
Building NSS 3.43 against NSPR 4.12 works fine. But in the resulting pkg-config file, at least NSPR 4.20 is required.
$ less /usr/lib/pkgconfig/nss.pc
prefix=/usr
exec_prefix=${prefix}
libdir=${prefix}/lib
includedir=${prefix}/include/nss
Name: NSS
Description: Network Security Services
Version: 3.43.0
Requires: nspr >= 4.20
Libs: -L${prefix}/lib -lnss3 -lnssutil3 -lsmime3 -lssl3 -lsoftokn3
Cflags: -I${includedir}
Expected results:
Shouldn’t the configure script then also check that at least NSPR 4.20 is built against.
Comment 1•5 years ago
|
||
Note: This will need to go into the release process documentation.
Comment 2•5 years ago
|
||
Small brain dump for me later: automation/release/nspr-version.txt
is the only place in-tree where NSPR version data is kept. The .pc
files are apparently coming from that, so configure
should check it, too.
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Note: Assuming there's a process fix, we'll need to update https://wiki.mozilla.org/NSS/Release_Management accordingly.
Updated•3 years ago
|
Comment 4•2 years ago
|
||
The bug assignee didn't login in Bugzilla in the last months and this bug has priority 'P1'.
:beurdouche, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Comment 5•1 year ago
|
||
I don't see where we create nss.pc
during an NSS build. We have a template in nss/pkg/pkg-config/nss.pc.in
, and some Linux distributions (e.g. arch) use this to generate the nss.pc
that they ship.
I would take a patch w/ a script to generate nss.pc
from the template and the information in automation/release/nspr-version.txt
, but I don't think we'll do this ourselves.
Description
•