Opened 6 months ago

Last modified 5 months ago

#60953 assigned defect

atlas @3.10.2_2: ERROR: enum fam=3, chip=2, model=158, mach=0

Reported by: jfb007 Owned by: Veence (Vincent)
Priority: Normal Milestone:
Component: ports Version: 2.6.3
Keywords: catalina Cc:
Port: atlas

Description (last modified by ryandesign (Ryan Schmidt))

Dear maintainer

After upgrading to Catalina, I made a clean install of macports. Everything went fine, with the exception of atlas, which failed to build.

Unfortunately, I did not find any help to overcome this problem.

Can You help me? Thanks a lot and best Regards

Josef

This is what i did after cleaning atlas

$ sudo port install atlas
--->  Fetching archive for atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_19.x86_64.tbz2 from https://packages.macports.org/atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_19.x86_64.tbz2 from https://lil.fr.packages.macports.org/atlas
--->  Attempting to fetch atlas-3.10.2_2.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/atlas
--->  Fetching distfiles for atlas
--->  Verifying checksums for atlas
--->  Extracting atlas
--->  Applying patches to atlas
--->  Configuring atlas
Selected C compiler: /usr/bin/clang
Selected F77 compiler: gfortran9
Warning: reinplace s|-no-cpp-precomp||g didn't change anything in /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/work/ATLAS/CONFIG/src/atlcomp.txt
--->  Building atlas
Error: Failed to build atlas: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_math_atlas/atlas/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port atlas failed

Attachments (1)

main.log (546.6 KB) - added by jfb007 6 months ago.
main.log

Download all attachments as: .zip

Change History (5)

Changed 6 months ago by jfb007

Attachment: main.log added

main.log

comment:1 Changed 6 months ago by jfb007

Description: modified (diff)

comment:2 Changed 6 months ago by ryandesign (Ryan Schmidt)

Cc: vince@… removed
Description: modified (diff)
Keywords: catalina added; atlas build failure Catalina removed
Owner: set to Veence
Status: newassigned
Summary: atlas @3.10.2_2: failed to build on Catalinaatlas @3.10.2_2: ERROR: enum fam=3, chip=2, model=158, mach=0

The log says the build failed pretty much right away with:

:info:configure system(make IRun_GAS_x8632 args="-v 5" MYFLAGS="-DATL_OS_OSX" 2> /dev/null | fgrep SUCCESS)
:info:configure ierr=256 in command='make IRun_GAS_x8632 args="-v 5" MYFLAGS="-DATL_OS_OSX" 2> /dev/null | fgrep SUCCESS'!
:info:configure OUTPUT:
:info:configure =======
:info:configure system(make IRun_GAS_x8664 args="-v 5" MYFLAGS="-DATL_OS_OSX" 2> /dev/null | fgrep SUCCESS)
:info:configure ERROR: enum fam=3, chip=2, model=158, mach=0
:info:configure make[3]: *** [atlas_run] Error 44
:info:configure make[2]: *** [IRunArchInfo_x86] Error 2
:info:configure ERROR: enum fam=3, chip=2, model=158, mach=0
:info:configure make[3]: *** [atlas_run] Error 44
:info:configure make[2]: *** [IRunArchInfo_x86] Error 2
:info:configure ERROR: enum fam=3, chip=2, model=158, mach=0
:info:configure make[3]: *** [atlas_run] Error 44
:info:configure make[2]: *** [IRunArchInfo_x86] Error 2

My guess is it does not know what kind of processor you have. What Mac model are you using, and what processor does it have?

Atlas 3.10.2 is from mid 2014 so if your Mac is newer than that, that could explain why it does not know about your processor.

A similar error is reported by another user here. They were using atlas 3.10.3 which is from mid 2016.

comment:3 Changed 6 months ago by jfb007

I have a MacBook Pro (MacBookPro14,3, 15-inch, 2017) with 2.9 GHz Quad-Core Intel Core i7 processor.

comment:4 Changed 5 months ago by Veence (Vincent)

Atlas is at this time hopelessly outdated. The latest stable version is more than four years old, and the latest unstable will be a year old. I can try upgrading to the latest unstable, though I can’t guarantee it will work. Besides, Atlas uses a way to optimise its code that somehow interferes with the way modern versions of MacOS handle power consumption. I'd suggest ditching Atlas and turning to the Accelerate framework, at least for the time being. The Portfile needs a complete overhaul anyway.

Note: See TracTickets for help on using tickets.