Opened 19 months ago

Closed 19 months ago

Last modified 19 months ago

#65916 closed defect (duplicate)

julia @1.8.2_0+gcc12.darwin_18.x86_64: build failure "unsupported tapi file type '!tapi-tbd' in YAML file"

Reported by: ednl (Ewoud Dronkert) Owned by:
Priority: Normal Milestone:
Component: ports Version: 2.7.2
Keywords: Cc:
Port: julia

Description

Tried to add julia which succeeded on my M1 Mini and x86-64 Macbook last week (julia version 1.8.1) but failed now on an iMac with MacOS Mojave 10.14.6 (x64) and MacPorts 2.7.2. Relevant lines from main.log seem to be:

:info:build ld: warning: text-based stub file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.8.2/src/mach_dyld_atfork.tbd and library file /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.8.2/src/mach_dyld_atfork.tbd are out of sync. Falling back to library file for linking.
:info:build ld: unsupported tapi file type '!tapi-tbd' in YAML file '/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_lang_julia/julia/work/julia-1.8.2/src/mach_dyld_atfork.tbd' for architecture x86_64
:info:build clang: error: linker command failed with exit code 1 (use -v to see invocation)

Attachments (1)

main.log (137.9 KB) - added by ednl (Ewoud Dronkert) 19 months ago.

Download all attachments as: .zip

Change History (4)

Changed 19 months ago by ednl (Ewoud Dronkert)

Attachment: main.log added

comment:1 Changed 19 months ago by kencu (Ken)

Please see 65550

comment:2 Changed 19 months ago by kencu (Ken)

Resolution: duplicate
Status: newclosed

comment:3 in reply to:  2 Changed 19 months ago by ednl (Ewoud Dronkert)

Replying to kencu: Thanks. I did search! But I didn't look back far enough, I'm afraid, because I thought it would be a new issue with version 1.8.2. I guess I'll download the standalone package from them directly.

Note: See TracTickets for help on using tickets.