#66933 closed defect (fixed)
nss @3.88.1 No rule to make target '../certhigh/Darwin13.4.0_clang_64_OPT.OBJ/certhtml.o', needed by 'Output.OBJD/libnss3.dylib'
Reported by: | cave-canem | Owned by: | Marius Schamschula <mschamschula@…> |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.8.1 |
Keywords: | Mavericks | Cc: | cave-canem, Schamschula (Marius Schamschula) |
Port: | nss |
Description
... echo Output.OBJD/libnss.a Output.OBJD/libnss.a grep -v ';+' nss.def | grep -v ';-' | sed -e 's; DATA ;;' -e 's,;;,,' -e 's,;.*,,' -e 's,^,_,' > Output.OBJD/nss.def make[3]: *** No rule to make target '../certhigh/Darwin13.4.0_clang_64_OPT.OBJ/certhtml.o', needed by 'Output.OBJD/libnss3.dylib'. Stop. make[3]: Leaving directory '/opt/MacPorts/var/macports/build/_opt_macports-ports_net_nss/nss/work/nss-3.88.1/nss/lib/nss' make[2]: *** [../coreconf/rules.mk:44: nss] Error 2 make[2]: Leaving directory '/opt/MacPorts/var/macports/build/_opt_macports-ports_net_nss/nss/work/nss-3.88.1/nss/lib' make[1]: *** [coreconf/rules.mk:44: lib] Error 2 make[1]: Leaving directory '/opt/MacPorts/var/macports/build/_opt_macports-ports_net_nss/nss/work/nss-3.88.1/nss' make: *** [manifest.mn:21: all] Error 2 make: Leaving directory '/opt/MacPorts/var/macports/build/_opt_macports-ports_net_nss/nss/work/nss-3.88.1/nss' Command failed: cd "/opt/MacPorts/var/macports/build/_opt_macports-ports_net_nss/nss/work/nss-3.88.1/nss" && /usr/bin/make -j1 -w all NSS_DISABLE_GTESTS=1 NSS_ENABLE_WERROR=0 USE_64=1 CPU_ARCH=x86_64 CC="/opt/MacPorts/bin/clang -Os -std=c99 -arch x86_64" CCC="/opt/MacPorts/bin/clang++ -Os -stdlib=libc++ -arch x86_64" NSPR_INCLUDE_DIR=/opt/MacPorts/include/nspr NSPR_LIB_DIR=/opt/MacPorts/lib/nspr NSS_USE_SYSTEM_SQLITE=1 USE_SYSTEM_ZLIB=1 BUILD_OPT=1 OPTIMIZER="-Os" OBJDIR_NAME="Output.OBJD" Exit code: 2 Error: Failed to build nss: command execution failed DEBUG: Error code: CHILDSTATUS 16527 2 DEBUG: Backtrace: command execution failed while executing "system {*}$notty {*}$callback {*}$nice $fullcmdstring" invoked from within "command_exec -callback portprogress::target_progress_callback build" (procedure "portbuild::build_main" line 8) invoked from within "$procedure $targetname"
Detailed log in attachment
Attachments (3)
Change History (14)
Changed 21 months ago by cave-canem
Attachment: | main.log.tar.xz added |
---|
comment:1 Changed 21 months ago by jmroot (Joshua Root)
Cc: | Schamschula added |
---|
comment:2 Changed 21 months ago by jmroot (Joshua Root)
Successful buildbot build, for comparison: https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/219617
comment:3 Changed 21 months ago by Schamschula (Marius Schamschula)
From main.log
it seems you're building for i386
, rather than for x86_64
. I have no idea why it's failing, as all build bots came back clean.
comment:4 Changed 21 months ago by jmroot (Joshua Root)
The compiler specified in the build command is certainly different, /usr/bin/clang
vs /opt/MacPorts/bin/clang
. That wouldn't normally be in the fallback list; have you made any modifications to the compiler selection in your installation?
comment:5 Changed 21 months ago by cave-canem
port select --summary | rg "(Name|====|clang|llvm)" Name Selected Options ==== ======== ======= clang none mp-clang-10 mp-clang-11 mp-clang-12 mp-clang-13 mp-clang-14 mp-clang-15 mp-clang-3.7 mp-clang-5.0 mp-clang-9.0 none llvm none mp-llvm-10 mp-llvm-11 mp-llvm-12 mp-llvm-13 mp-llvm-14 mp-llvm-15 mp-llvm-3.7 mp-llvm-5.0 mp-llvm-9.0 none
New detaled log (main.log_v2)
comment:6 Changed 20 months ago by cave-canem
I solved this problem simply by adding the line "port:legacy-support" to the port file (depends_lib).
Ticket can be closed.
Detailed log in attachment
comment:7 Changed 20 months ago by Schamschula (Marius Schamschula)
Close: use the legacysupport 1.1 PortGroup!
comment:8 Changed 20 months ago by Marius Schamschula <mschamschula@…>
Owner: | set to Marius Schamschula <mschamschula@…> |
---|---|
Resolution: | → fixed |
Status: | new → closed |
comment:9 Changed 20 months ago by kencu (Ken)
I have no idea as yet why cave-canem's build was failing, why it was using different compilers for the different builds, why it finally succeeded, and what, if anything, adding a port dependency on legacysupport without using the PortGroup might have might have had to do with anything here...
But mysteries do abound!
comment:10 Changed 20 months ago by cave-canem
Hello Ken!
I am Russian.
Russians know how to solve unsolvable problems.
(No matter how pathetic it may sound).
But mysteries do abound!
comment:11 Changed 20 months ago by kencu (Ken)
Indeed.
Whatever fixed your build, it’s hard to see how adding a build dep on legacysupport was the fix… adding it as a build dep doesn’t do anything, as it will not be used anyway.
And adding it would not alter your compiler choice.
And it built on the buildbot without legacysupport.
So what went on here is a mystery.
main.log