Hi, ----- On 28 Nov, 2014, at 12:08, René J.V. Bertin [email protected] wrote:
>> > What would be best to troubleshoot, the terminal output from configure, or >> > config.log ? >> >> Configure output and config.log. > > Both attached in a zip archive. Thanks. Problem is checking for Apple Objective-C runtime... yes Why does the check for the Apple Objective-C runtime succeed on your Linux system? Where does the objc/objc-api.h header come from on your system? Do we need to adjust our check? > I'm thinking that would depend on what exactly my problem is. If it's a > missing > tcl dependency, the issue ought to disappear when using an existing tcl > interpreter. No, the issue isn't related to Tcl. It's MacPorts' Makefiles that add the offending -framework flags when the Apple Objective-C runtime is detected. There might be other issues related to Tcl, but you haven't encountered any yet, so I'd not jump to conclusions and try to use a different Tcl than MacPorts' bundled copy (which works just fine on Linux). > I noticed about 8.6 so installed tcl 8.5 explicitly because of that. Tcl 8.4 > is > still listed as a compatible version, though! Well, we should update that documentation then -- Tcl 8.4 can no longer be used to run MacPorts code. > It's been ages since I did anything with tcl other than a tiny bit of hacking > (and editing Portfiles :)). I guess that is because tcl has no central > repository like Python's "site-packages"? (Which would explain why the > tcl-thread is not offered in tcl 8.4, 8.5 etc. variants.) It does, but MacPorts doesn't install there (because that would make having multiple copies of MacPorts rather hard...) -- Clemens _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
