problem when installing macports
hi :-) i don't understand : i have exactly the same config on 2 computers, on one it ran perfectly, and on the other it crashed :-( here is my install script : http://dl.free.fr/dCGpwSdBw/installer-macports here is what i get on the computer where it crashes : + cd /Users/thomas/Documents/prgm/temporaire/ + rsync -azv rsync://rsync.macports.org/release/base/ macports/ + cd macports/ + ./configure --prefix=/Users/thomas/Documents/prgm/bin/autoinstall/ macports/ --with-install-user=thomas --with-install-group=thomas configure: creating ./config.status config.status: creating src/programs/daemondo/Makefile config.status: WARNING: src/programs/daemondo/Makefile.in seems to ignore the --datarootdir setting config.status: creating Makefile config.status: creating Mk/macports.autoconf.mk config.status: WARNING: Mk/macports.autoconf.mk.in seems to ignore the --datarootdir setting config.status: creating doc/prefix.mtree config.status: creating doc/macosx.mtree config.status: creating doc/macports.conf config.status: creating src/Makefile config.status: creating src/macports1.0/macports_autoconf.tcl config.status: creating src/tclobjc1.0/Makefile config.status: creating src/port1.0/port_autoconf.tcl config.status: creating src/registry1.0/registry_autoconf.tcl config.status: creating src/programs/Makefile config.status: creating src/macports1.0/macports_fastload.tcl config.status: creating src/config.h + make ===> making all in config make[1]: Nothing to be done for `all'. ===> making all in doc make[1]: Nothing to be done for `all'. ===> making all in src ===> making all in src/macports1.0 gcc -c -DUSE_TCL_STUBS -g -O2 -W -Wall -pedantic -g -Os - DHAVE_CONFIG_H -I.. -I. -I"/usr/include" -DTCL_THREADS=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 - DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1 - DHAVE_READDIR_R=1 -DMAC_OSX_TCL=1 -DHAVE_CFBUNDLE=1 -DUSE_VFORK=1 - DTCL_DEFAULT_ENCODING=\"utf-8\" -DTCL_WIDE_INT_TYPE=long\ long - DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 - DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 - DNO_VALUES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 - DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 - DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 - DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 - DHAVE_SIGNED_CHAR=1 -DHAVE_PUTENV_THAT_COPIES=1 -DHAVE_LANGINFO=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -fno-common macports.c -o macports.o gcc -c -DUSE_TCL_STUBS -g -O2 -W -Wall -pedantic -g -Os - DHAVE_CONFIG_H -I.. -I. -I"/usr/include" -DTCL_THREADS=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 - DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1 - DHAVE_READDIR_R=1 -DMAC_OSX_TCL=1 -DHAVE_CFBUNDLE=1 -DUSE_VFORK=1 - DTCL_DEFAULT_ENCODING=\"utf-8\" -DTCL_WIDE_INT_TYPE=long\ long - DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 - DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 - DNO_VALUES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 - DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 - DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 - DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 - DHAVE_SIGNED_CHAR=1 -DHAVE_PUTENV_THAT_COPIES=1 -DHAVE_LANGINFO=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -fno-common portconf.c -o portconf.o gcc -c -DUSE_TCL_STUBS -g -O2 -W -Wall -pedantic -g -Os - DHAVE_CONFIG_H -I.. -I. -I"/usr/include" -DTCL_THREADS=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 - DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1 - DHAVE_READDIR_R=1 -DMAC_OSX_TCL=1 -DHAVE_CFBUNDLE=1 -DUSE_VFORK=1 - DTCL_DEFAULT_ENCODING=\"utf-8\" -DTCL_WIDE_INT_TYPE=long\ long - DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 - DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 - DNO_VALUES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 - DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 - DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 - DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 - DHAVE_SIGNED_CHAR=1 -DHAVE_PUTENV_THAT_COPIES=1 -DHAVE_LANGINFO=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -fno-common session.c -o session.o gcc -c -DUSE_TCL_STUBS -g -O2 -W -Wall -pedantic -g -Os - DHAVE_CONFIG_H -I.. -I. -I"/usr/include" -DTCL_THREADS=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 - DHAVE_PTHREAD_ATTR_SETSTACKSIZE=1 -DHAVE_PTHREAD_ATFORK=1 - DHAVE_READDIR_R=1 -DMAC_OSX_TCL=1 -DHAVE_CFBUNDLE=1 -DUSE_VFORK=1 - DTCL_DEFAULT_ENCODING=\"utf-8\" -DTCL_WIDE_INT_TYPE=long\ long - DHAVE_GETCWD=1 -DHAVE_OPENDIR=1 -DHAVE_STRSTR=1 -DHAVE_STRTOL=1 - DHAVE_STRTOLL=1 -DHAVE_STRTOULL=1 -DHAVE_TMPNAM=1 -DHAVE_WAITPID=1 - DNO_VALUES_H=1 -DHAVE_LIMITS_H=1 -DHAVE_UNISTD_H=1 - DHAVE_SYS_PARAM_H=1 -DHAVE_SYS_TIME_H=1 -DTIME_WITH_SYS_TIME=1 - DHAVE_TM_ZONE=1 -DHAVE_GMTIME_R=1 -DHAVE_LOCALTIME_R=1 - DHAVE_TM_GMTOFF=1 -DHAVE_ST_BLKSIZE=1 -DSTDC_HEADERS=1 - DHAVE_SIGNED_CHAR=1 -DHAVE_PUTENV_THAT_COPIES=1 -DHAVE_LANGINFO=1 - DHAVE_SYS_IOCTL_H=1 -DHAVE_SYS_FILIO_H=1 -fno-common util.c -o util.o cc -dynamiclib -L/usr/local/lib macports.o portconf.o session.o util.o -o MacPorts.dylib -L/System/Library/Frameworks/Tcl.framework/ Versions/8.4 -ltclstub8.4 -L/usr/local/lib ld: Undefined symbols: _snprintf$LDBLStub /usr/bin/libtool: internal link edit command failed make[2]: *** [MacPorts.dylib] Error 1 make[1]: *** [all] Error 1 make: *** [all] Error 1 + exit i have deleted from this log what i thought to be not important tell me if you need the complete log does sb see what could be the pb ? -- j'agis contre l'assistanat, je travaille dans une SCOP !
Le 19 sept. 07 à 06:14, Thomas De Contes a écrit :
i don't understand :
i have exactly the same config on 2 computers,
on one it ran perfectly, and on the other it crashed :-(
does sb see what could be the pb ?
the 2 computers have a G4, but not the same speed nor the same quantity of RAM on one, the login shell is tcsh (it works), and on the other, the login shell is bash (it doesn't work) could it be the cause ?? on both, i have installed the last version of xcode (2.4.1), but only devtools software, gcc 3.3, and software dev kits oh yes, i just remember, on the computer where it works, i have installed gcc 4.0 instead of gcc 3.3 so, is it required to have gcc 4.0 to compile macports ?? why ? do you need to know sth more ? -- j'agis contre l'assistanat, je travaille dans une SCOP !
Thomas De Contes wrote:
on one, the login shell is tcsh (it works), and on the other, the login shell is bash (it doesn't work) could it be the cause ??
Probably not: bash is the supported shell, since it's now the default...
on both, i have installed the last version of xcode (2.4.1), but only devtools software, gcc 3.3, and software dev kits oh yes, i just remember, on the computer where it works, i have installed gcc 4.0 instead of gcc 3.3 so, is it required to have gcc 4.0 to compile macports ?? why ?
You need the Universal system compiler (gcc-4.0) for Mac OS X 10.4 / Xcode, not the gcc-3.3 cross-compiler - that's only for building for Mac OS X 10.3 Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" LDFLAGS="-arch ppc", but that seemed to have work... (i.e. it didn't give any snprintf errors) --anders
On Sep 20, 2007, at 05:02, Anders F Björklund wrote:
Thomas De Contes wrote:
on one, the login shell is tcsh (it works), and on the other, the login shell is bash (it doesn't work) could it be the cause ??
Probably not: bash is the supported shell, since it's now the default...
on both, i have installed the last version of xcode (2.4.1), but only devtools software, gcc 3.3, and software dev kits oh yes, i just remember, on the computer where it works, i have installed gcc 4.0 instead of gcc 3.3 so, is it required to have gcc 4.0 to compile macports ?? why ?
You need the Universal system compiler (gcc-4.0) for Mac OS X 10.4 / Xcode, not the gcc-3.3 cross-compiler - that's only for building for Mac OS X 10.3
Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" LDFLAGS="- arch ppc", but that seemed to have work... (i.e. it didn't give any snprintf errors)
Anders, he didn't say what OS version he was using. Also, he's on G4, so gcc 3.3 is a native compiler, not a cross-compiler. But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode 1.5, which installs gcc 3.3 and that's supposed to be fine for MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 which installs gcc 4.0, and your gcc_select should be set to use gcc 4.0, which is the default. Using gcc 3.3 as your system compiler on Mac OS X 10.4 is not supported by MacPorts, and I don't recommend it for any reason.
Le 21 sept. 07 à 20:05, Ryan Schmidt a écrit :
On Sep 20, 2007, at 05:02, Anders F Björklund wrote:
Thomas De Contes wrote:
on both, i have installed the last version of xcode (2.4.1), but only devtools software, gcc 3.3, and software dev kits oh yes, i just remember, on the computer where it works, i have installed gcc 4.0 instead of gcc 3.3 so, is it required to have gcc 4.0 to compile macports ?? why ?
You need the Universal system compiler (gcc-4.0) for Mac OS X 10.4 / Xcode, not the gcc-3.3 cross-compiler - that's only for building for Mac OS X 10.3
Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" LDFLAGS="-arch ppc", but that seemed to have work... (i.e. it didn't give any snprintf errors)
Anders, he didn't say what OS version he was using. Also, he's on G4, so gcc 3.3 is a native compiler, not a cross-compiler.
But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode 1.5, which installs gcc 3.3 and that's supposed to be fine for MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 which installs gcc 4.0, and your gcc_select should be set to use gcc 4.0, which is the default. Using gcc 3.3 as your system compiler on Mac OS X 10.4 is not supported by MacPorts, and I don't recommend it for any reason.
thank you very much for all the details :-) i have 10.4, two remote computers with ppc, and my local computer with intel but, if on 10.4 the "core" is gcc 4.0, why is there "This package contains the Apple version of the gcc 4.0 compiler." and "This package contains the Apple version of the gcc 3.3 compiler, and is required to use the Developer Tools on Mac OS X." even on intel, which let us suppose that the "core" is gcc 3.3 ? -- j'agis contre l'assistanat, je travaille dans une SCOP !
On Oct 1, 2007, at 20:26, Thomas De Contes wrote:
Le 21 sept. 07 à 20:05, Ryan Schmidt a écrit :
On Sep 20, 2007, at 05:02, Anders F Björklund wrote:
Thomas De Contes wrote:
on both, i have installed the last version of xcode (2.4.1), but only devtools software, gcc 3.3, and software dev kits oh yes, i just remember, on the computer where it works, i have installed gcc 4.0 instead of gcc 3.3 so, is it required to have gcc 4.0 to compile macports ?? why ?
You need the Universal system compiler (gcc-4.0) for Mac OS X 10.4 / Xcode, not the gcc-3.3 cross-compiler - that's only for building for Mac OS X 10.3
Trying to reproduce the issue with CC="gcc-3.3 -arch ppc" LDFLAGS="-arch ppc", but that seemed to have work... (i.e. it didn't give any snprintf errors)
Anders, he didn't say what OS version he was using. Also, he's on G4, so gcc 3.3 is a native compiler, not a cross-compiler.
But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode 1.5, which installs gcc 3.3 and that's supposed to be fine for MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 which installs gcc 4.0, and your gcc_select should be set to use gcc 4.0, which is the default. Using gcc 3.3 as your system compiler on Mac OS X 10.4 is not supported by MacPorts, and I don't recommend it for any reason.
thank you very much for all the details :-)
i have 10.4, two remote computers with ppc, and my local computer with intel
but, if on 10.4 the "core" is gcc 4.0, why is there "This package contains the Apple version of the gcc 4.0 compiler." and "This package contains the Apple version of the gcc 3.3 compiler, and is required to use the Developer Tools on Mac OS X." even on intel, which let us suppose that the "core" is gcc 3.3 ?
Regardless of whether you have an Intel or PowerPC Mac, Apple's gcc 3.3 makes only PowerPC binaries, and Apple's gcc 4.0 can make either Intel or PowerPC or universal binaries. It is useful for developers who wish to create universal binaries of their programs to use gcc 3.3 for the PowerPC parts and gcc 4.0 for the Intel parts and to later combine them using lipo. This ensures that the software works with earlier Mac OS X releases on PowerPC.
Thomas De Contes:
Anders, he didn't say what OS version he was using. Also, he's on G4, so gcc 3.3 is a native compiler, not a cross-compiler.
Actually I meant platform cross-compiler rather than architecture cross-compiler, but it doesn't matter much...
But, Thomas, if you're running Mac OS X 10.3.9, then you need Xcode 1.5, which installs gcc 3.3 and that's supposed to be fine for MacPorts. If you're on Mac OS X 10.4.10, then you need Xcode 2.4.1 which installs gcc 4.0, and your gcc_select should be set to use gcc 4.0, which is the default. Using gcc 3.3 as your system compiler on Mac OS X 10.4 is not supported by MacPorts, and I don't recommend it for any reason.
thank you very much for all the details :-)
i have 10.4, two remote computers with ppc, and my local computer with intel
but, if on 10.4 the "core" is gcc 4.0, why is there "This package contains the Apple version of the gcc 4.0 compiler." and "This package contains the Apple version of the gcc 3.3 compiler, and is required to use the Developer Tools on Mac OS X." even on intel, which let us suppose that the "core" is gcc 3.3 ?
It probably just wasn't updated since it really was the required one... Like Ryan says, Mac OS X 10.3.9 (with Xcode 1.5) is also still OK to use. Mac OS X 10.4.10 (actually Xcode 2.4.1) comes with *four* compilers, one for each version of Mac OS X: gcc2, gcc3, gcc-3.3 and gcc-4.0 The recommended one is gcc-4.0, since it can't build Universal binaries with the gcc-3.3 (and since GCC 4 is much better than GCC 3 anyway, but) Usually you just install the "XcodeTools.mpkg", instead of individual pkg ? And that will install *both* of gcc4.0.pkg and gcc3.3.pkg, by default... --anders
Le 2 oct. 07 à 08:51, Anders F Björklund a écrit :
It probably just wasn't updated since it really was the required one...
Mac OS X 10.4.10 (actually Xcode 2.4.1) comes with *four* compilers, one for each version of Mac OS X: gcc2, gcc3, gcc-3.3 and gcc-4.0 The recommended one is gcc-4.0, since it can't build Universal binaries with the gcc-3.3 (and since GCC 4 is much better than GCC 3 anyway, but)
thank you all :-)) -- j'agis contre l'assistanat, je travaille dans une SCOP !
participants (3)
-
Anders F Björklund
-
Ryan Schmidt
-
Thomas De Contes