On Tue, Feb 22, 2011 at 1:31 PM, Marko Käning <[email protected]> wrote: > Same here and this is what I get: > > :info:build ATLAS install complete. Examine > :info:build ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details. > :info:build /usr/bin/make clean > :info:build rm -rf *.dSYM > :info:build rm -rf *.o x* config?.out *core* > :debug:build Executing proc-post-org.macports.build-build-0 > :info:build Undefined symbols: > :info:build "_ATL_DecAtomicCount", referenced from: > :info:build _ATL_dyntlaunch in libatlas.a(ATL_dyntlaunch.o) > :info:build _ATL_dyntlaunch in libatlas.a(ATL_dyntlaunch.o) > :info:build ld: symbol(s) not found > :info:build shell command "cd > /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_atlas/work/atlas-3.9.37/build/lib > && ( test ! -e libatlas.a || /usr/bin/ld -arch x86_64 -dynamic -dylib > -single_module -dead_strip -x -all_load -L. -L/opt/local/lib/gcc44/x86_64 > -L/opt/local/lib/gcc44 -ldylib1.o -dylib_install_name > /opt/local/lib/libatlas.dylib libatlas.a -o libatlas.dylib -lSystem )" > returned error 1 > :error:build Target org.macports.build returned: shell command failed (see > log for details) > :debug:build Backtrace: shell command failed (see log for details) >
So is this in the post-build phase where the portfile is manually creating the dylib? Also, Rodolfo replied to me off-list and said that some of his machines were actually crashing. Not sure if it was at this same place. Or perhaps just due to the large cpu load involved with building atlas. I don't see why this particular problem reported by Marko would actually crash a computer... Scott _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
