Opened 2 years ago

Last modified 2 years ago

#64494 assigned defect

sqlite3 @3.37.2_0: configure fails installing +universal variant — at Version 4

Reported by: bal-agates Owned by: Schamschula (Marius Schamschula)
Priority: Low Milestone:
Component: ports Version: 2.7.1
Keywords: Cc:
Port: sqlite3

Description (last modified by ryandesign (Ryan Carsten Schmidt))

Attached are a sqlite3 config.log and main.log where the config failed. The failure appears to due to a compiler test trying to build an x86_64 object while linking against a library (/opt/local/lib/libunwind.dylib) that is only built for arm64.

I am not sure how to solve this. Is this a config tool problem or port problem? I suppose one of those could have a dependency added to make sure whatever port is providing libundind.dylib checks that it is built universal?

I put this at low priority because this doesn't really affect me. It was the result of another port errantly wanting to rebuild everything "+universal". See #64488.

Change History (6)

Changed 2 years ago by bal-agates

Attachment: sqlite3-config.log added

sqlite3 config.log showing failure

Changed 2 years ago by bal-agates

Attachment: sqlite3-main.log added

sqlite3 main.log showing failure

comment:1 Changed 2 years ago by jmroot (Joshua Root)

Keywords: sqlite3 universal removed
Owner: set to Schamschula
Status: newassigned

comment:2 Changed 2 years ago by jmroot (Joshua Root)

What does port provides /opt/local/lib/libunwind.dylib say?

comment:3 Changed 2 years ago by Schamschula (Marius Schamschula)

Or perhaps file /opt/local/lib/libunwind.1.dylib?

To my knowledge sqlite3 is not built using libunwind. Perhaps the configure script opportunistically finds it?

comment:4 Changed 2 years ago by ryandesign (Ryan Carsten Schmidt)

Description: modified (diff)

Right... libunwind probably gets used opportunistically by a lot of stuff. Either uninstall libunwind or build it universal before trying to build something else universal that might use it.

Note: See TracTickets for help on using tickets.