On Feb 11, 2010, at 4:38 PM, Ryan Schmidt wrote: > On Feb 11, 2010, at 14:32, Scott Haneda wrote: > >> DEBUG: Environment: CFLAGS='-O2 -arch x86_64' >> CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2 -arch x86_64' >> MACOSX_DEPLOYMENT_TARGET='10.6' LIBRARY_PATH='/opt/local/lib' >> CXX='/usr/bin/g++-4.2' F90FLAGS='-O2 -m64' LDFLAGS='-L/opt/local/lib' >> FCFLAGS='-O2 -m64' OBJC='/usr/bin/gcc-4.2' INSTALL='/usr/bin/install -c' >> C_INCLUDE_PATH='/opt/local/include' OBJCFLAGS='-O2 -arch x86_64' FFLAGS='-O2 >> -m64' CC='/usr/bin/gcc-4.2' > > You're trying to build p5-net-libidn for the architecture x86_64. > >> DEBUG: Assembled command: 'cd >> "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_perl_p5-net-libidn/work/Net-LibIDN-0.12" >> && /opt/local/bin/perl Makefile.PL INSTALLDIRS=vendor' >> ld: warning: in /opt/local/lib/libidn.dylib, file is not of required >> architecture > > But its dependency libidn is installed for a different architecture. Rebuild > libidn. > > The only way this should have happened is if you installed libidn while > running Mac OS X 10.5 or earlier, then upgraded to Mac OS X 10.6 and tried to > build p5-net-libidn. > > It could also happen if you deliberately set build_arch to, say, i386 in > macports.conf before building libidn, then set it back to x86_64 afterward, > but you probably wouldn't do that.
So if I get this correct, I should just remove libidn, then p5-net-libidn will install fine? $port installed libidn The following ports are currently installed: libidn @1.15_0 (active) $sudo port uninstall libidn ---> Deactivating libidn @1.15_0 ---> Uninstalling libidn @1.15_0 $port installed libidn None of the specified ports are installed. $sudo port -d install p5-net-libidn 2>&1 | tee ~/Desktop/p5-net-libidn.txt Results: http://dl.dropbox.com/u/340087/drops/02.11.10/p5-net-libidn-fc9f6575-172724.txt Still seems to be trying to go 64 DEBUG: Environment: CFLAGS='-O2 -arch x86_64' CPPFLAGS='-I/opt/local/include' CXXFLAGS='-O2 -arch x86_64' MACOSX_DEPLOYMENT_TARGET='10.6' CXX='/usr/bin/g++-4.2' F90FLAGS='-O2 -m64' LDFLAGS='-L/opt/local/lib' OBJC='/usr/bin/gcc-4.2' FCFLAGS='-O2 -m64' INSTALL='/usr/bin/install -c' OBJCFLAGS='-O2 -arch x86_64' FFLAGS='-O2 -m64' CC='/usr/bin/gcc-4.2' So this means I need to add +univeral to libidn, and install it by hand ahead of time? How so I solve this so that end users need not worry about this, when they just want to `sudo port install ASSP`. -- Scott * If you contact me off list replace talklists@ with scott@ * _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
