Opened 2 hours ago
Last modified 56 minutes ago
#71119 assigned defect
ruby33: error: something wrong with LDFLAGS
| Reported by: | ttelford (Troy Telford) | Owned by: | kimuraw (kimura wataru) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.10.2 |
| Keywords: | sequoia arm64 | Cc: | fhgwright (Fred Wright) |
| Port: | ruby33 |
Description (last modified by ttelford (Troy Telford))
On arm64 & Sequoia, I'm seeing ruby33 builds fail:
config.log and main.log attached.
(edit: I had something that turned out to be a red herring for what I thought was wrong - removing noise)
Attachments (2)
Change History (6)
Changed 2 hours ago by ttelford (Troy Telford)
| Attachment: | config.log added |
|---|
comment:1 Changed 2 hours ago by ttelford (Troy Telford)
After reading the log (more) I'm going to revise: "Error not android" isn't the real problem, it's just configure finding what features are available... <sigh>. Time to keep reading.
comment:2 Changed 2 hours ago by ttelford (Troy Telford)
| Description: | modified (diff) |
|---|
comment:3 Changed 73 minutes ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | fhgwright added |
|---|---|
| Owner: | set to kimuraw |
| Port: | ruby33 added |
| Status: | new → assigned |
| Summary: | ruby33: on arm64 & Sequoia - fails in configure during `checking whether it is Android` → ruby33: error: something wrong with LDFLAGS |
The main.log says:
:info:configure checking whether LDFLAGS is valid... no :info:configure configure: error: something wrong with LDFLAGS="-L/opt/local/libexec/openssl3/lib -L/opt/local/lib -Wl,-headerpad_max_install_names -Wl,-syslibroot,/Library/Developer/CommandLineTools/SDKs/MacOSX15.sdk -arch arm64"
Not sure what they mean by "valid" or why they're checking it; this is unusual of this project.
There is no error in the result of that configure check but there is a warning; maybe they consider warnings to make things "invalid". The warning is:
ld: warning: reexported library with install name '/opt/local/lib/libunwind.1.dylib' found at '/opt/local/lib/libunwind.1.dylib' couldn't be matched with any parent library and will be linked directly
This will be because you have the libunwind port installed, which we already know will break a lot of ports. Recommend you uninstall it. See #66250.
comment:4 Changed 56 minutes ago by ttelford (Troy Telford)
I can certainly deactivate libunwind; it's not a requested port.
Unfortunately it's a dependency of a number of ports, probably the most notable is watchman.
I'll give it a try and report back.
config.log