MacPorts-2.4.2 linker command failed for libthread2.7.3.dylib with undefined symbols _Tcl_InitStubs...

[wojtekcz (Wojciech Czarnowski)]

MacPorts-2.4.2
System macOS High Sierra, Xcode 9.2, Command Line Tools macOS 10.13 for Xcode 9.2

Compilation commands:

MP_PREFIX=$HOME/macports
./configure --prefix $MP_PREFIX --with-applications-dir=$MP_PREFIX/Applications --with-install-user=$(id -u -n) --with-install-group=$(id -g -n) --with-no-root-privileges
make

...
gcc -dynamiclib -pipe  -Os -DNDEBUG -Wall -fno-common   -prebind -headerpad_max_install_names -Wl,-search_paths_first  -Wl,-single_module -current_version 2.7.3 -compatibility_version 2.7.3 -o libthread2.7.3.dylib threadNs.o threadCmd.o threadSvCmd.o threadSpCmd.o threadPoolCmd.o psGdbm.o threadSvListCmd.o threadSvKeylistCmd.o tclXkeylist.o threadUnix.o  -L/Users/wcz/technologies/macports/MacPorts-2.4.2/vendor/tcl/unix -ltclstub8.5
ld: warning: ignoring file /Users/wcz/technologies/macports/MacPorts-2.4.2/vendor/tcl/unix/libtclstub8.5.a, file was built for archive which is not the architecture being linked (x86_64): /Users/wcz/technologies/macports/MacPorts-2.4.2/vendor/tcl/unix/libtclstub8.5.a
Undefined symbols for architecture x86_64:
  "_Tcl_InitStubs", referenced from:
      _Thread_Init in threadCmd.o
  "_tclStubsPtr", referenced from:
      _Thread_Init in threadCmd.o
      _ThreadCreateObjCmd in threadCmd.o
      _ThreadSendObjCmd in threadCmd.o
      _ThreadBroadcastObjCmd in threadCmd.o
      _ThreadExitObjCmd in threadCmd.o
      _ThreadUnwindObjCmd in threadCmd.o
      _ThreadIdObjCmd in threadCmd.o
      ...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libthread2.7.3.dylib] Error 1
make[1]: *** [all-tclthread] Error 2
make: *** [all] Error 1

[ryandesign (Ryan Carsten Schmidt)]

Please attach a log of the entire transcript, including the configuration and compilation.

[wojtekcz (Wojciech Czarnowski)]

Replying to ryandesign:

Please attach a log of the entire transcript, including the configuration and compilation.

Attached.

[jmroot (Joshua Root)]

Does it work if you start from a clean source tree with PATH=/usr/bin:/bin:/usr/sbin:/sbin?

[wojtekcz (Wojciech Czarnowski)]

Replying to jmroot:

Does it work if you start from a clean source tree with PATH=/usr/bin:/bin:/usr/sbin:/sbin?

It does :-) Thank you very much!

[ryandesign (Ryan Carsten Schmidt)]

It's recommended to use ./standard_configure.sh, because it will set a default PATH for you.