Opened 10 years ago

Closed 8 years ago

#28758 closed defect (fixed)

fail to build atlas in i7 mac

Reported by: high07@… Owned by: jameskyle@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc: otto.hasselblad@…, j.bugzilla2@…, SlaunchaMan (Jeff Kelley), Veence (Vincent)
Port: atlas

Description (last modified by mf2k (Frank Schima))

To set up py26-nltk, I was trying to setup atlas as it is a dependency for nltk.

However, it constantly fails, although I tried most things suggested by related thread. I am not sure what should I do for this. any help will be greatly appreciated.

sudo port clean --all atlas
Password:
--->  Cleaning atlas

 sudo port install atlas
--->  Computing dependencies for atlas
--->  Fetching atlas
--->  Attempting to fetch atlas3.9.37.tar.bz2 from http://voxel.dl.sourceforge.net/math-atlas
--->  Attempting to fetch lapack-3.3.0.tgz from http://www.netlib.org/lapack
--->  Verifying checksum(s) for atlas
--->  Extracting atlas
--->  Applying patches to atlas
--->  Configuring atlas
--->  Building atlas

Error: Target org.macports.build returned: shell command failed (see log for details)
Log for atlas is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_math_atlas/main.log
Error: Status 1 encountered during processing.
To report a bug, see <http://guide.macports.org/#project.tickets>

Attachments (1)

main.log (4.1 MB) - added by high07@… 10 years ago.
log file

Change History (13)

Changed 10 years ago by high07@…

Attachment: main.log added

log file

comment:1 Changed 10 years ago by Veence (Vincent)

You should try to compile with gcc45 instead of gcc44. It would not even surprise me if, for these newest model, gcc46 is not required.

comment:2 Changed 10 years ago by mf2k (Frank Schima)

Description: modified (diff)
Owner: changed from macports-tickets@… to jameskyle@…
Port: atlas added

comment:3 in reply to:  1 Changed 10 years ago by high07@…

Replying to vince@…:

You should try to compile with gcc45 instead of gcc44. It would not even surprise me if, for these newest model, gcc46 is not required.

Yes somebody suggested the same thing so i tried to do that. I successfully downloaded and built gcc45 but i got those result after setting up gcc45

comment:4 Changed 10 years ago by Veence (Vincent)

The log you've posted indicates you've tried to build atlas using gcc44, not gcc45. You should use the +gcc45 option. I'm going to see if it is worth adding a +gcc46 new option. But, as a general rule, ports like Atlas, which rely heavily on the knowledge of the underlying hardware (in this case, CPU), always lag a bit after a new hardware release. You may have to wait several months for an updated version. In this case, except signaling it upstream, there is little we can do.

comment:5 Changed 10 years ago by Veence (Vincent)

It seems a 3.9.38 version is out that corrects a bug and is compatible with the new Sandy bridge processors. I will propose an update ASAP.

comment:6 Changed 10 years ago by Veence (Vincent)

3.9.38 seems to be buggy, I've signaled it upstream, but it may take a little while to be fixed (assuming this is a real bug and not a configure trick).

comment:7 Changed 10 years ago by otto.hasselblad@…

Cc: otto.hasselblad@… added

Cc Me!

comment:8 Changed 10 years ago by Veence (Vincent)

I have reported some bugs to Atlas' maintainer, and they should be fixed in the new 3.9.41 release I am currently testing, I'll keep you posted.

comment:9 Changed 10 years ago by j.bugzilla2@…

Cc: j.bugzilla2@… added

Cc Me!

comment:10 Changed 10 years ago by SlaunchaMan (Jeff Kelley)

Cc: SlaunchaMan@… added

Cc Me!

comment:11 Changed 9 years ago by jmroot (Joshua Root)

Cc: vince@… added

Does this still happen with 3.9.47?

comment:12 Changed 8 years ago by Veence (Vincent)

Resolution: fixed
Status: newclosed

I assume it works now…

Note: See TracTickets for help on using tickets.