Opened 13 months ago

Last modified 3 months ago

#67262 assigned defect

lapack @3.11.0_0+accelerate+gcc10: Undefined symbols _scabs1_

Reported by: brolcz Owned by: tenomoto (Takeshi Enomoto)
Priority: Normal Milestone:
Component: ports Version: 2.8.1
Keywords: Cc: Dave-Allured (Dave Allured)
Port: lapack

Description

When attempting to update lapack, it fails to build. I have tried cleaning, and it still failed. I am using Mac OS 10.14.6. I am attaching the log below. Thank you!

Attachments (1)

main.log​ (1.4 MB) - added by brolcz 13 months ago.

Download all attachments as: .zip

Change History (6)

Changed 13 months ago by brolcz

Attachment: main.log​ added

comment:1 Changed 13 months ago by jmroot (Joshua Root)

Cc: tenomoto removed
Owner: set to tenomoto
Status: new → assigned 
:info:build Undefined symbols for architecture x86_64:
:info:build   "_scabs1_", referenced from:
:info:build       _scabs1sub_ in scabs1sub.f.o
:info:build ld: symbol(s) not found for architecture x86_64
:info:build collect2: error: ld returned 1 exit status
:info:build make[2]: *** [lib/libcblas.3.11.0.dylib] Error 1

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

Cc: Dave-Allured added
Summary: lapack @3.11.0_0+accelerate+gcc10 failed to build → lapack @3.11.0_0+accelerate+gcc10: Undefined symbols _scabs1_

comment:3 Changed 3 months ago by Dave-Allured (Dave Allured)

Lapack was recently updated to 3.12.0. Please run a port selfupdate, then try again with the updated lapack.

comment:4 Changed 3 months ago by Dave-Allured (Dave Allured)

Oh sorry, I did not look at the timeline on this ticket before replying. This is an old issue. It may no longer be a problem. If lapack is still getting this problem after update, then please follow up on this ticket, or else start a new ticket.

comment:5 in reply to:  4 Changed 3 months ago by Gandoon (Erik Hedlund)

Replying to Dave-Allured:

Oh sorry, I did not look at the timeline on this ticket before replying. This is an old issue. It may no longer be a problem. If lapack is still getting this problem after update, then please follow up on this ticket, or else start a new ticket.

As this ticket is still open and it seems to have something in common with my #69295 from the other day, I am including that reference here just in case they indeed are connected. This ticket are for a build on an even older OS than the one I am using, using an older gcc, and presumably older accelerate framework. Thus they may only superficially resemble each other, while the root cause lies somewhere else.

Note: See TracTickets for help on using tickets.