Opened 2 years ago

Closed 2 years ago

#65537 closed defect (fixed)

hdf5 +fortran +gfortran +cxx +hl fails to build

Reported by: cmstuber (Chris Stuberg) Owned by: eborisch (Eric A. Borisch)
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: monterey arm Cc: mike142wood, cjones051073 (Chris Jones)
Port: hdf5

Description

On macOS 12, arm64, this is failing to build. Prior to the recent updates to major updates of gcc10,11, 12, this seemed to build just fine. I've uninstalled all ports and reattempted, tried to build against gcc10, reinstalled CLTs 13.4 and continue to see this build error. Building without +fortran builds properly.

end of main.log looks like:

:info:build ld: warning: argument missing after -rpath
:info:build ld: can't map file, errno=22 file '/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk' for architecture arm64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)
:info:build make[2]: *** [libhdf5.la] Error 1
:info:build make[2]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hdf5/hdf5/work/hdf5-1.12.2/src'
:info:build make[1]: *** [all] Error 2
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hdf5/hdf5/work/hdf5-1.12.2/src'
:info:build make: *** [all-recursive] Error 1
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hdf5/hdf5/work/hdf5-1.12.2'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hdf5/hdf5/work/hdf5-1.12.2" && /usr/bin/make -j8 -w all 
:info:build Exit code: 2
:error:build Failed to build hdf5: command execution failed
:debug:build Error code: CHILDSTATUS 72591 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$callback {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec -callback portprogress::target_progress_callback build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_science_hdf5/hdf5/main.log for details.

I'll attach the main.log

I can gather additional artifacts as needed. Help, suggestions, or workarounds would be very welcomed.

Attachments (1)

main.log (1.1 MB) - added by cmstuber (Chris Stuberg) 2 years ago.
main.log

Download all attachments as: .zip

Change History (6)

Changed 2 years ago by cmstuber (Chris Stuberg)

Attachment: main.log added

main.log

comment:1 Changed 2 years ago by mike142wood

similar failure occurs with Monterey on x86 (model Macmini7,1 processor "2.6GHz Dual-Core Intel Core i5") -- error line reads
:info:build ld: can't map file, errno=22 file '/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk' for architecture x86_64
Is there a problem that Monterey OS version is 12.4 but SDK version shows as MacOSX12.3.sdk

comment:2 Changed 2 years ago by mike142wood

Cc: mike142wood added

comment:3 Changed 2 years ago by mascguy (Christopher Nielsen)

Cc: cjones051073 added
Owner: set to eborisch
Status: newassigned

comment:4 Changed 2 years ago by mascguy (Christopher Nielsen)

Keywords: monterey arm added

comment:5 Changed 2 years ago by cjones051073 (Chris Jones)

Resolution: fixed
Status: assignedclosed

Issue is nothing to do with the SDKs, that just a red herring.

Problem in fact was a small oversight I made when I added support recently to the compilers PG to automatically handle the new gcc rpath. Fixed with

https://github.com/macports/macports-ports/commit/9712a6f0bbea20b6676bd03c4701793317b71d81

hdf5 +cxx+fortran+gfortran+hl builds then fine for me.

Note: See TracTickets for help on using tickets.