DarwinPorts (MacPorts) Advisory: Stay with at least Xcode 2.2.1 on Intel (if not PPC)

"Tabitha McNerney" <[email protected]> Sat, 26 Aug 2006 20:10:06 -1000
Newsgroups gmane.os.opendarwin.darwinports
Message-ID <[email protected]>
Here is an example of where I reiterate to be careful using Xcode 2.4 with
DarwinPorts 1.3.2 (and probably 1.3.1). Take the same Mac Mini Intel machine
(duo core 1.67 GhZ), take Mac OS X 10.4.7 (client installed from the
installer DVDs that shipped with the Mac Mini -- starting with 10.4.5 and
then doing a software update to 10.4.7 -- the DVDs are for Intel
architecture only, not Universal Binary). Now take Xcode 2.4 and try to
build the DarwinPort gpgme and you get the failure below. However, swap out
Xcode 2.4 with 2.2.1 on the same exact platform and gpgme works fine. Looks
like the error below has something to do with Apple changing gcc (in Xcode
2.4 missing Fortran g77 parts?). Anyway, gpgme works gorgeous with Intel Mac
Mini, Darwin Ports 1.3.2, and 10.4.7 Intel with Xcode 2.2.1

I therefore highly encourage current DarwinPorts (MacPorts) users to stick
with 2.2.1 (unless Xcode 2.3 is fine but I have not tested it).

Best regards,

T.

port install gpgme
--->  Fetching gpgme
--->  Attempting to fetch gpgme-1.1.2.tar.bz2 from
http://ftp.gnupg.org/gcrypt/gpgme/
--->  Verifying checksum(s) for gpgme
--->  Extracting gpgme
--->  Applying patches to gpgme
--->  Configuring gpgme
Error: Target com.apple.configure returned: configure failure: shell command
"cd
"/opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_devel_gpgme/work/gpgme-
1.1.2" && CPPFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib"
./configure --prefix=/opt/local --infodir=/opt/local/share/info
--mandir=/opt/local/share/man --with-gpg=/opt/local/bin/gpg --enable-static"
returned error 1
Command output: checking dynamic linker characteristics... darwin8.7.1 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "RC" to libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... no
checking whether the g++ linker (/usr/bin/ld) supports shared libraries...
yes
checking for g++ option to produce PIC... -fno-common
checking if g++ PIC flag -fno-common works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries...
yes
checking dynamic linker characteristics... darwin8.7.1 dyld
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
checking for GNU Pth... *FAILED*
 | Found GNU Pth 2.0.6 under /opt/local, but
 | was unable to perform a sanity linker check. This means
 | the GNU Pth library libpth.a was not found.
 | We used the following build environment:
 |    CC="gcc"
 |    CFLAGS="-g -O2 -I/opt/local/include"
 |    LDFLAGS="-L/opt/local/lib -L/opt/local/lib"
 |    LIBS=" -lpth"
 | See config.log for possibly more details.

Error: Status 1 encountered during processing.