Opened 14 years ago
Closed 14 years ago
#28501 closed defect (fixed)
UPDATE: atlas-3.9.37 (Fixes critical bugs!)
Reported by: | adfernandes (Andrew Fernandes) | Owned by: | jameskyle@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | Veence (Vincent), dershow, Garfield-fr (Bertrand Zuchuat), f.calboli@…, anddam (Andrea D'Amore), ryandesign (Ryan Carsten Schmidt) | |
Port: | atlas |
Description
Patch included. One "patchfile" no longer needed.
According to the changelog since 3.9.35 (the current port version):
ATLAS 3.9.37 released 02/15/11, changes from 3.9.36: * Fixed bug in all L2 kernel timers where timing loop not even entered, resulting in bogus time being returned * Fixed bug in gmmsearch.c; lat was set to bad value after K-unroll search * Added xtune_spawn_fp to study spawning strategies under load ATLAS 3.9.36 released 02/13/11, changes from 3.9.35: * ATLAS now only uses affinity when it provides speedup (empirically tuned) * Fixed bug in all ATL_PAFF_SELF implementations of affinity * Fixed bug in ATL_PAFF_SCHED affinity implementation * Fixed several bugs for when your affinity IDs are not contiguous * Fixed bug in gmmsearch.c, where lat was set to bad value in K-unroll search * Fixed l2install targs to ignore problems in deleting old values
Attachments (1)
Change History (11)
Changed 14 years ago by adfernandes (Andrew Fernandes)
Attachment: | Portfile.diff added |
---|
comment:1 Changed 14 years ago by Veence (Vincent)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 Changed 14 years ago by adfernandes (Andrew Fernandes)
Resolution: | fixed |
---|---|
Status: | closed → reopened |
Crap, crap, crap - SORRY - I just noticed that my 3.9.37 failed with a weird error. I think it is due to a conflict with the installed atlas. I'll test ASAP this morning and update! (I think that they may have changed more than is in the changelog!) :-(
ATLAS install complete. Examine ATLAS/bin/<arch>/INSTALL_LOG/SUMMARY.LOG for details. /usr/bin/make clean rm -rf *.dSYM rm -rf *.o x* config?.out *core* DEBUG: Executing proc-post-org.macports.build-build-0 Undefined symbols: "_ATL_DecAtomicCount", referenced from: _ATL_dyntlaunch in libatlas.a(ATL_dyntlaunch.o) _ATL_dyntlaunch in libatlas.a(ATL_dyntlaunch.o) ld: symbol(s) not found shell command "cd /opt/local/var/macports/build/_Users_andrew_Local_macports-trunk_dports_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/gcc45/x86_64 -L/opt/local/lib/gcc45 -ldylib1.o -dylib_install_name /opt/local/lib/libatlas.dylib libatlas.a -o libatlas.dylib -lSystem )" returned error 1 Error: Target org.macports.build returned: shell command failed (see log for details) DEBUG: Backtrace: shell command failed (see log for details) while executing "$post $targetname" Warning: the following items did not execute (for atlas): org.macports.destroot org.macports.build
comment:3 Changed 14 years ago by jmroot (Joshua Root)
Cc: | vince@… added |
---|
Vince, as this is not an openmaintainer port you should not have committed without giving the maintainer 3 days to respond.
comment:4 Changed 14 years ago by Veence (Vincent)
I know, I did that because the .37 fixed critical bugs, and so I deemed urgent to upgrade ASAP. We can revert to the previous version if needed.
comment:6 Changed 14 years ago by anddam (Andrea D'Amore)
Cc: | bertrand.zuchuat@… f.calboli@… added |
---|
comment:8 Changed 14 years ago by adfernandes (Andrew Fernandes)
I'm currently doing a fresh rebuild and clean to see if the build problem goes away. I did a diff between the last (.35) and current (.37) versions in MacPorts, and there are quite a number of changes.
I've been building since this morning; it takes hours, unfortunately.
Again, this is my fault for mistakenly thinking that my build had finished (too many terminals open at once).
It is a good question, though... the .37 won't build, but the .35 is buggy... what to do? I'll post when my build finishes.
comment:10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
This ticket was for the update to 3.9.37, which has been accomplished.
The build failures now being encountered with 3.9.37 can be handled in new ticket #28512.
Done in r76407. Thanks.