ghostscript @9.25: ld: file not found: /usr/lib/system/libsystem_network.dylib for architecture x86_64

[jswoboda (John Swoboda)]

ghostscript @ @9.25_1 (print) fails to build, on MacOS Mojave.

Build output log:

:info:build     /bin/sh <./soobj/ldt.tr
:info:build ld: file not found: /usr/lib/system/libsystem_network.dylib for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build make[2]: *** [sobin/libgs.9.25.dylib] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
:info:build make[1]: *** [so-only-subtarget] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
:info:build make: *** [so] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25" && /usr/bin/make -j8 -w so
:info:build Exit code: 2
:error:build Failed to build ghostscript: command execution failed
:debug:build Error code: CHILDSTATUS 92242 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_print_ghostscript/ghostscript/main.log for details.}}}

[kencu (Ken)]

We'll need the whole log, John. Can you attach it to this ticket please?

[kencu (Ken)]

FYI:

$ port -v installed ghostscript
The following ports are currently installed:
  ghostscript @9.25_0+x11 platform='darwin 18' archs='x86_64' date='2018-09-27T19:39:05-0700'
  ghostscript @9.25_1+x11 (active) platform='darwin 18' archs='x86_64' date='2018-10-26T18:53:03-0700'

[jswoboda (John Swoboda)]

Build log

[kencu (Ken)]

I take it you might be running a pre-release darwin beta? :

OS darwin/18.2.0 (Mac OS X 10.14) arch i386

I get this on my (up-to-date) system:

OS darwin/18.0.0 (Mac OS X 10.14) arch i386

[jswoboda (John Swoboda)]

I updated mine on Oct 30 and it wasn't the beta. This was the darwin version that they pushed with 10.14.1 update.

[kencu (Ken)]

I am learning something new. On my App Store Updates pane there is nothing new listed.

But from the About This Mac Software Update button, on first click it says no updates available. Then on second click it finds the 10.14.1 update...

So indeed, my OS is .1 behind right now, although who knows when I would have found out :>

Updating now. I dunno if that is why your build failed at present.

[ryandesign (Ryan Carsten Schmidt)]

I agree with the error message—there is no /usr/lib/system/libsystem_network.dylib on Mojave—but I don't know why the build is looking for it. There's no mention of that file in the log before the error message. I don't see this build failure on Mojave 10.14.0 with Xcode 10.0. I will update and see if I see the problem with 10.14.1 and 10.1.

[kencu (Ken)]

I don't think that libsystem_network.dylib has been around for a while, so the question indeed is why is your ld looking for it all of a sudden.

I just upgraded to 10.14.1 and rebuilt ghostscript without issues:

if [ x != x ]; then LD_RUN_PATH=; export LD_RUN_PATH; fi; \
	XCFLAGS= XINCLUDE= XLDFLAGS= XLIBDIRS= XLIBS= \
	PSI_FEATURE_DEVS= FEATURE_DEVS= DEVICE_DEVS= DEVICE_DEVS1= DEVICE_DEVS2= DEVICE_DEVS3= \
	DEVICE_DEVS4= DEVICE_DEVS5= DEVICE_DEVS6= DEVICE_DEVS7= DEVICE_DEVS8= \
	DEVICE_DEVS9= DEVICE_DEVS10= DEVICE_DEVS11= DEVICE_DEVS12= \
	DEVICE_DEVS13= DEVICE_DEVS14= DEVICE_DEVS15= DEVICE_DEVS16= \
	DEVICE_DEVS17= DEVICE_DEVS18= DEVICE_DEVS19= DEVICE_DEVS20= \
	DEVICE_DEVS_EXTRA= \
	/bin/sh <./soobj/ldt.tr
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
/Applications/Xcode.app/Contents/Developer/usr/bin/make -f Makefile DISPLAY_DEV=./soobj/display.dev STDIO_IMPLEMENTATION=c BUILDDIRPREFIX=so GENOPT='' LDFLAGS='-Lsobin -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -arch x86_64  '\
	 CFLAGS='-O2 -isystem/opt/local/include -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk  -Wall -Wstrict-prototypes -Wundef -Wmissing-declarations -Wmissing-prototypes -Wwrite-strings -fno-strict-aliasing -Werror=declaration-after-statement -fno-builtin -fno-common -Werror=return-type -DHAVE_STDINT_H=1 -DHAVE_DIRENT_H=1 -DHAVE_SYS_DIR_H=1 -DHAVE_SYS_TIME_H=1 -DHAVE_SYS_TIMES_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_LIBDL=1 -DGX_COLOR_INDEX_TYPE="unsigned long long" -D__USE_UNIX98=1  -pipe -Os -isysroot/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.14.sdk -arch x86_64 -DHAVE_RESTRICT=1 -DUSE_LIBICONV_GNU -DUSE_LIBPAPER  -fno-strict-aliasing -DHAVE_POPEN_PROTO=1  ' prefix=/opt/local\
	 ./sobin/gsc ./sobin/gsx -so-loader -so-loader -so-loader
make[2]: Entering directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_print_ghostscript/ghostscript/work/ghostscript-9.25'
--->  Staging ghostscript into destroot
. changed
	gid expected 0 found 80 modified

[kencu (Ken)]

John, can you show us exactly what version of ld64 you have installed?

port -v installed ld64

[jswoboda (John Swoboda)]

I have this installed

ld64 @3_1+ld64_xcode (active) platform='darwin 18' archs='x86_64' date='2018-10-31T11:53:48-0400'

[kencu (Ken)]

are you perhaps setting a deployment_target somewhere, like in your macports.conf ?

[ryandesign (Ryan Carsten Schmidt)]

Replying to kencu:

I don't think that libsystem_network.dylib has been around for a while,

It is present on Lion through High Sierra.

[ryandesign (Ryan Carsten Schmidt)]

Replying to kencu:

are you perhaps setting a deployment_target somewhere, like in your macports.conf ?

His log shows that the deployment target is 10.14 as it should be.

[kencu (Ken)]

OK. Something is wrong here.

I assume the migration instructions were followed, and we're not left with any stuff built on 10.13 still installed. Also, I assume no personal modifications have been made to any of macports *.conf files, and there is nothing in /usr/local to cause trouble.

Next step I would do is to clean and try a trace mode build.

sudo port clean ghostscript
sudo port -v -t install ghostscript

If that works, then some offending installed port is most likely messing with you, somehow.

If that doesn't work -- after several days with no success, I'd most likely blow out MacPorts (there are instructions how to do that) and reinstall from scratch. Something has to be wrong here, and it looks like something local on your end. Reinstalling MacPorts takes only a few minutes and eliminates almost all local issues.

[jswoboda (John Swoboda)]

Hi I did a clean reinstall of mac ports and it fixed the problem. This ticket can be closed out.

[kencu (Ken)]

Great! Glad we got you working. We will never probably know exactly what the issue was...