Opened 14 years ago
Closed 14 years ago
#23559 closed defect (fixed)
log4shib doesn't build universal
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | scantor (Scott Cantor) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.8.2 |
| Keywords: | Cc: | scantor (Scott Cantor) | |
| Port: | log4shib |
Description
log4shib doesn't succeed at building universal x86_64/i386 on Snow Leopard. See attached debug output. This should be fixed either by allowing log4shib to build universal properly, or by disabling the universal variant with "universal_variant no".
Attachments (1)
Change History (6)
Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
| Attachment: | log4shib.txt added |
|---|
comment:1 follow-up: 2 Changed 14 years ago by scantor (Scott Cantor)
comment:2 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to scantor@…:
Is there a non-default option involved in asking it to be built this way?
Yes; you request the port to build using the universal variant:
sudo port install log4shib +universal
I don't believe any autoconf-based projects handle universal builds very well
The default universal variant that MacPorts provides is specifically designed for autoconf-based projects, so I cannot agree with your assessment here.
and I have no plans to try, so I guess I'll take your suggestion, but I don't want the "standard" use of the package to be impacted. Thx...
It looks like it would be pretty simple, maybe as simple as using the muniversal portgroup, but it's up to you.
comment:3 Changed 14 years ago by scantor (Scott Cantor)
I was basing my assessment on the specfile patches I got that allowed an RPM-based build to be universal, and it was a mess and required patches in some cases to the underlying makefiles. If there's a macport shortcut that just does it automatically, could you point me to any documentation on it?
comment:4 Changed 14 years ago by scantor (Scott Cantor)
| Owner: | changed from snc@… to scantor@… |
|---|
The bug here is that the libtool used in this (and some other related) packages is old enough that it doesn't allow the -arch parameter when linking. Using the OS X glibtool in place of the generated version seems to work so I'll test that as a workaround.
Using the muniversal portgroup doesn't fix anything, it just runs into the same bug.
comment:5 Changed 14 years ago by scantor (Scott Cantor)
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Added a temporary workaround that copies in macports glibtool. Universal build appears to work for this port and the xml-security-c port. Will update embedded libtool in future releases and remove workaround.
Is there a non-default option involved in asking it to be built this way?
I don't believe any autoconf-based projects handle universal builds very well, and I have no plans to try, so I guess I'll take your suggestion, but I don't want the "standard" use of the package to be impacted. Thx...