[MacPorts] #20838: gcc44, gcc45 on snow leopard: can't open file: ./libgcc_s.1.dylib.tmp: No such file or directory
MacPorts
noreply at macports.org
Sat Sep 12 23:52:59 PDT 2009
#20838: gcc44, gcc45 on snow leopard: can't open file: ./libgcc_s.1.dylib.tmp: No
such file or directory
---------------------------------------+------------------------------------
Reporter: andrius.laikina@… | Owner: mww@…
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: gcc44, gcc45
---------------------------------------+------------------------------------
Comment(by blb@…):
On 10.5.8 Intel, Xcode 3.1.4, configure stage says:
{{{
DEBUG: Executing org.macports.configure (gcc44)
DEBUG: Environment: CPATH='/mp/include' CXXFLAGS='-pipe -O2'
CPPFLAGS='-I/mp/include' CFLAGS='-pipe -O2' AS_FOR_TARGET='/usr/bin/as'
LIBRARY_PATH='/mp/lib' MACOSX_DEPLOYMENT_TARGET='10.5'
CXX='/usr/bin/g++-4.0' F90FLAGS='-pipe -O2 -m32'
LD_FOR_TARGET='/usr/bin/ld' RANLIB_FOR_TARGET='/usr/bin/ranlib'
LDFLAGS='-L/mp/lib' CFLAGS_FOR_BUILD='-O2'
OBJDUMP_FOR_TARGET='/usr/bin/objdump' FCFLAGS='-pipe -O2 -m32'
OBJC='/usr/bin/gcc-4.0' INSTALL='/usr/bin/install -c'
AR_FOR_TARGET='/usr/bin/ar' NM_FOR_TARGET='/usr/bin/nm' FFLAGS='-pipe -O2
-m32' OBJCFLAGS='-pipe -O2' STRIP_FOR_TARGET='/usr/bin/strip'
CC='/usr/bin/gcc-4.0'
DEBUG: Assembled command: 'cd
"/mp/var/macports/build/_Users_blb_devel_macports_trunk_dports_lang_gcc44/work/build"
&& ../gcc-4.4.1/configure --prefix=/mp --enable-
languages=c,c++,objc,obj-c++,java,fortran --libdir=/mp/lib/gcc44
--includedir=/mp/include/gcc44 --infodir=/mp/share/info
--mandir=/mp/share/man --with-local-prefix=/mp --with-system-zlib
--disable-nls --program-suffix=-mp-4.4 --with-gxx-include-
dir=/mp/include/gcc44/c++/ --with-gmp=/mp --with-mpfr=/mp --disable-
libjava-multilib --with-arch=nocona --with-tune=generic --build=i686
-apple-darwin9 --host=i686-apple-darwin9 --target=i686-apple-darwin9'
}}}
so looks like the args are as expected (didn't do an actual build though).
For testing, you can either define
[http://guide.macports.org/#reference.phases.test a test phase] or simply
run a phase before {{{install}}} like {{{sudo port build}}} which will
leave the results up to that phase in the work dir.
--
Ticket URL: <http://trac.macports.org/ticket/20838#comment:50>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list