Closed Bug 1833428 Opened 2 years ago Closed 1 year ago

NSS does not build on windows

Categories

(NSPR :: NSPR, defect)

All
Windows
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: anna.weine, Unassigned)

References

(Blocks 1 open bug)

Details

TLDR: NSS does not build on NSS.

Copy-paste from the user:

I have been trying to build NSS 3.89.1 on windows
nss/build.sh does not work

This time I am trying (on my last attempt) -- that is on the mozillabuild shell
build.sh -v --enable-64bit --msvc

I understand it supposed to build nspr first
the scripts appears to have 5 steps
Seems to be crashing in the middle of step 2
The last attempt says failed to find st command

calling build.sh --rebuild --enable-64bit --msvc
This is the output

Step 2/5 of NSPR configure does not seem to complete properly

NSPR [1/5] configure ...
verbose = 1
/w/nspr/Debug
../configure --prefix=/w/dist/Debug --enable-64bit
../configure --prefix=/w/dist/Debug --enable-64bit
configure: loading site script /etc/config.site
checking build system type... x86_64-pc-msys
checking host system type... x86_64-pc-msys
checking target system type... x86_64-pc-msys
checking for cl... cl

MSC_VER=1932
MSMT_TOOL=Microsoft (R) Manifest Tool
_MSMT_VER_FILTER=s|.* ([0-9][0-9].[0-9][0-9].[0-9][0-9].[0-9][0-9]).*|\1|p

configure: WARNING: Unknown version of the Microsoft (R) Manifest Tool.
CPU_ARCH=x86
OS_TARGET=WINNT
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config/Makefile
config.status: creating config/autoconf.mk
config.status: creating config/nsprincl.mk
config.status: creating config/nsprincl.sh
config.status: creating config/nspr-config
config.status: creating config/nspr.pc
config.status: creating lib/Makefile
config.status: creating lib/ds/Makefile
config.status: creating lib/libc/Makefile
config.status: creating lib/libc/include/Makefile
config.status: creating lib/libc/src/Makefile
config.status: creating lib/tests/Makefile
config.status: creating pkg/Makefile
config.status: creating pr/Makefile
config.status: creating pr/include/Makefile
config.status: creating pr/include/md/Makefile
config.status: creating pr/include/obsolete/Makefile
config.status: creating pr/include/private/Makefile
config.status: creating pr/src/Makefile
config.status: creating pr/src/io/Makefile
config.status: creating pr/src/linking/Makefile
config.status: creating pr/src/malloc/Makefile
config.status: creating pr/src/md/Makefile
config.status: creating pr/src/md/windows/Makefile
config.status: creating pr/src/memory/Makefile
config.status: creating pr/src/misc/Makefile
config.status: creating pr/src/threads/Makefile
config.status: creating pr/tests/Makefile
config.status: creating pr/tests/dll/Makefile
config.status: creating pr/src/threads/combined/Makefile
config.status: executing default commands
NSPR [1/5] configure DONE!!!
NSPR [2/5] make ...
make



BASED on the nspr.sh script -- I am supposed to see if the tests were executed or not for step 3

if [ "$build_nspr_tests" = 1 ]; then
  echo "NSPR [3/5] build tests ..."
  run_verbose make -C "$nspr_dir/pr/tests"
else
    echo "NSPR [3/5] NOT building tests"
fi
Assignee: nobody → nobody
Component: Build → NSPR
Product: NSS → NSPR
Version: 3.89 → other

Probably the problem is in NSPR.

The severity field is not set for this bug.
:KaiE, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(kaie)
See Also: → 1831552

(In reply to Anna Weine from comment #0)

TLDR: NSS does not build on NSS.

I think you mean NSS doesn't build on Windows?

Flags: needinfo?(kaie)
Severity: -- → S3

(In reply to Kai Engert (:KaiE:) from comment #3)

(In reply to Anna Weine from comment #0)

TLDR: NSS does not build on NSS.

I think you mean NSS doesn't build on Windows?

Exactly..

NSS does build on Windows-latest with the correct setup... The documentation is out of date though.

https://github.com/beurdouche/nss/actions/runs/7139099956/workflow

Blocks: nss-external
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.