Regarding machines crashing The iMacs that actually crashed and froze were all machines that while I was updating MacPorts, they had students using the machines through the GUI The ones that were not being used by the GUI just failed at building Atlas Therefore Scott is right, the machines that crashed they probably did so because of CPU load??
Thanks to all of you who are working on getting this resolved --Rodolfo On Wed, Feb 23, 2011 at 09:00, <[email protected]> wrote: > Send macports-users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of macports-users digest..." > > > Today's Topics: > > 1. Re: macports-users Digest, Vol 54, Issue 22 (Rodolfo Aramayo) > 2. Problems building Atlas (Rodolfo Aramayo) > 3. Re: Problems building Atlas (Scott Webster) > 4. Re: Problems building Atlas (Marko K?ning) > 5. Re: Problems building Atlas (Scott Webster) > 6. Re: Problems building Atlas (Marko K?ning) > 7. Re: Problems building Atlas (Ryan Schmidt) > 8. Re: Problems building Atlas (Tim Bunnell) > 9. Re: Problems building Atlas (Ryan Schmidt) > 10. Re: Problems building Atlas (Tim Bunnell) > 11. Re: Problems building Atlas (Ryan Schmidt) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 22 Feb 2011 12:19:10 -0600 > From: Rodolfo Aramayo <[email protected]> > To: [email protected] > Subject: Re: macports-users Digest, Vol 54, Issue 22 > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > People, > > I am having problems building Atlas > > The last lines of the 'main.log' file state: > > == > :info:build > :info:build BEGIN STAGE 4-3-4: cLAPACK TUNING at 12:15 > :info:build make -f Makefile ILATune pre=z 2>&1 | ./xatlas_tee > INSTALL_LOG/zLATUNE.LOG > :info:build DONE STAGE 4-3-4 at 12:15 > :info:build DONE STAGE 4-3-0 at 12:15 > :info:build DONE STAGE 4-0-0 at 12:15 > :info:build > :info:build > :info:build BEGIN STAGE 5-0-0: FINAL LIBRARY UPDATE at 12:15 > :info:build > :info:build > :info:build BEGIN STAGE 5-1-0: FINAL STATIC LIBRARY UPDATE at 12:15 > :info:build make -f Makefile IBuildLibs IBuildPtlibs0 2>&1 | > ./xatlas_tee INSTALL_LOG/LIBUPDATE.LOG > :info:build DONE STAGE 5-1-0 at 12:15 > :info:build > :info:build > :info:build > :info:build > :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) > while executing > "$post $targetname" > :info:build Warning: the following items did not execute (for atlas): > org.macports.destroot org.macports.build > :notice:build Log for atlas is at: > /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_atlas/main.log > == > > Any Ideas? > > Thanks > > --Rodolfo > > > ------------------------------ > > Message: 2 > Date: Tue, 22 Feb 2011 15:21:44 -0600 > From: Rodolfo Aramayo <[email protected]> > To: [email protected] > Subject: Problems building Atlas > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=UTF-8 > > Guys, > > All my machines are crashing building Atlas > > I do not know what happened but this is serious as it is blocking the > update/installation of ports > > --Rodolfo > > > ------------------------------ > > Message: 3 > Date: Tue, 22 Feb 2011 13:26:28 -0800 > From: Scott Webster <[email protected]> > To: Rodolfo Aramayo <[email protected]> > Cc: [email protected] > Subject: Re: Problems building Atlas > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > On Tue, Feb 22, 2011 at 1:21 PM, Rodolfo Aramayo <[email protected]> wrote: >> Guys, >> >> All my machines are crashing building Atlas >> >> I do not know what happened but this is serious as it is blocking the >> update/installation of ports >> >> --Rodolfo > > The computers themselves are crashing, or the build is failing? I > built it fine yesterday on my Macbook. Maybe you can give some more > details? > > Scott > > > ------------------------------ > > Message: 4 > Date: Tue, 22 Feb 2011 22:31:13 +0100 > From: Marko K?ning <[email protected]> > To: MacPorts Users Mailing-list <[email protected]> > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > 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) > > > > ------------------------------ > > Message: 5 > Date: Tue, 22 Feb 2011 13:50:56 -0800 > From: Scott Webster <[email protected]> > To: Marko K?ning <[email protected]> > Cc: MacPorts Users Mailing-list <[email protected]> > Subject: Re: Problems building Atlas > Message-ID: > <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1 > > 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 > > > ------------------------------ > > Message: 6 > Date: Tue, 22 Feb 2011 22:54:40 +0100 > From: Marko K?ning <[email protected]> > To: MacPorts Users Mailing-list <[email protected]> > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=windows-1252 > >> building atlas. I don't see why this particular problem reported by >> Marko would actually crash a computer? > No crash, building just fails. > > ------------------------------ > > Message: 7 > Date: Tue, 22 Feb 2011 16:04:07 -0600 > From: Ryan Schmidt <[email protected]> > To: Rodolfo Aramayo <[email protected]> > Cc: [email protected] > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Atlas was recently updated to 3.9.33, then 3.9.35, then 3.9.37, in rapid > succession.3.9.35 built on my machine but apparently was buggy; 3.9.37 seems > to be having problems building, on my machine as well. > > You can monitor this ticket to be informed of the progress resolving this: > > https://trac.macports.org/ticket/28512 > > > > > ------------------------------ > > Message: 8 > Date: Tue, 22 Feb 2011 17:23:41 -0500 > From: Tim Bunnell <[email protected]> > To: Ryan Schmidt <[email protected]> > Cc: Rodolfo Aramayo <[email protected]>, > [email protected] > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Atlas has been in the process of building on my machine for several hours > now. Based on this discussion I'm inclined to stop it. Will the previous > 3.9.35 installation still be intact if I do so? > > Thanks, > > t > On Feb 22, 2011, at 5:04 PM, Ryan Schmidt wrote: > >> Atlas was recently updated to 3.9.33, then 3.9.35, then 3.9.37, in rapid >> succession.3.9.35 built on my machine but apparently was buggy; 3.9.37 seems >> to be having problems building, on my machine as well. >> >> You can monitor this ticket to be informed of the progress resolving this: >> >> https://trac.macports.org/ticket/28512 >> >> >> _______________________________________________ >> macports-users mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > Director, Center for Pediatric Auditory and Speech Sciences (CPASS) > Head, Speech Research Lab | Adjunct Associate Professor > duPont Hospital for Children | Comp. and Info. Sciences / Linguistics > Voice: 1+302+651-6835 | University of Delaware > Fax: 1+302+651-6895 | URL: www.asel.udel.edu/speech/ > > > > > > > ------------------------------ > > Message: 9 > Date: Tue, 22 Feb 2011 16:25:20 -0600 > From: Ryan Schmidt <[email protected]> > To: Tim Bunnell <[email protected]> > Cc: Rodolfo Aramayo <[email protected]>, > [email protected] > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Feb 22, 2011, at 16:23, Tim Bunnell wrote: > >> Atlas has been in the process of building on my machine for several hours >> now. Based on this discussion I'm inclined to stop it. Will the previous >> 3.9.35 installation still be intact if I do so? > > Yes, assuming you successfully installed it (i.e. "port installed atlas" > shows atlas @3.9.35_0 is installed and active) > > > > ------------------------------ > > Message: 10 > Date: Tue, 22 Feb 2011 17:30:50 -0500 > From: Tim Bunnell <[email protected]> > To: Ryan Schmidt <[email protected]> > Cc: Rodolfo Aramayo <[email protected]>, > [email protected] > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > Yup. Is there a specific form of port clean that would be good to use to tidy > up? > > Thanks, > > t > > > On Feb 22, 2011, at 5:25 PM, Ryan Schmidt wrote: > >> On Feb 22, 2011, at 16:23, Tim Bunnell wrote: >> >>> Atlas has been in the process of building on my machine for several hours >>> now. Based on this discussion I'm inclined to stop it. Will the previous >>> 3.9.35 installation still be intact if I do so? >> >> Yes, assuming you successfully installed it (i.e. "port installed atlas" >> shows atlas @3.9.35_0 is installed and active) > > Director, Center for Pediatric Auditory and Speech Sciences (CPASS) > Head, Speech Research Lab | Adjunct Associate Professor > duPont Hospital for Children | Comp. and Info. Sciences / Linguistics > Voice: 1+302+651-6835 | University of Delaware > Fax: 1+302+651-6895 | URL: www.asel.udel.edu/speech/ > > > > > > > ------------------------------ > > Message: 11 > Date: Tue, 22 Feb 2011 16:50:21 -0600 > From: Ryan Schmidt <[email protected]> > To: Tim Bunnell <[email protected]> > Cc: Rodolfo Aramayo <[email protected]>, > [email protected] > Subject: Re: Problems building Atlas > Message-ID: <[email protected]> > Content-Type: text/plain; charset=us-ascii > > On Feb 22, 2011, at 16:30, Tim Bunnell wrote: > >> On Feb 22, 2011, at 5:25 PM, Ryan Schmidt wrote: >> >>> On Feb 22, 2011, at 16:23, Tim Bunnell wrote: >>> >>>> Atlas has been in the process of building on my machine for several hours >>>> now. Based on this discussion I'm inclined to stop it. Will the previous >>>> 3.9.35 installation still be intact if I do so? >>> >>> Yes, assuming you successfully installed it (i.e. "port installed atlas" >>> shows atlas @3.9.35_0 is installed and active) >> >> Yup. Is there a specific form of port clean that would be good to use to >> tidy up? > > You can run "sudo port clean atlas" to clean out your build attempt to free > up disk space. But when the atlas port is fixed, you'll "sudo port > selfupdate" to receive the fix, and then when you try to upgrade atlas, > MacPorts would automatically clean it, because it notices that the portfile > is newer than your last build attempt. > > > > > > ------------------------------ > > _______________________________________________ > macports-users mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macports-users > > > End of macports-users Digest, Vol 54, Issue 23 > ********************************************** > _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
