Opened 14 years ago
Last modified 12 years ago
#28063 new defect
gnustep-base configure fails on 10.6, "I don't seem to be able to use your Objective-C compiler to produce working binaries" — at Initial Version
Reported by: | ivan@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | gnustep-base |
Description
Attempting to install "gnustep" results in a failure while configuring "gnustep-base" on 10.6.
configure fails on step "checking whether objc really works…".
I do not have GCC 4.2 installed from MacPorts; Apple's GCC 4.2 is installed, and used by GNUstep-base. Despite that, there are several references in the log to attempting to use MacPorts GCC 4.2: FFII library from /opt/local/include/gcc42 and /opt/local/lib/gcc42 is apparently used. See this line from the log:
:info:configure shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnustep_gnustep-base/work/gnustep-base-1.19.1" && ./configure --prefix=/opt/local CC=/usr/bin/gcc-4.2 GNUSTEP_MAKEFILES=/opt/local/GNUstep/System/Library/Makefiles --disable-tls --enable-libffi --with-ffi-include=/opt/local/include/gcc42 --with-ffi-library=/opt/local/lib/gcc42 " returned error 1
MP-GCC 4.2 failed to install for me several months ago (which was the previous reason for me failing to install and use GNUstep), and since it is not required for installation, I do not feel obliged to have it installed.
Forcing build system to use MP-GCC 4.4 resulted in a different behavior: configure phase completed successfully, but build phase kept using Apple's GCC 4.2.