Opened 16 years ago

Closed 11 years ago

Last modified 11 years ago

#13890 closed defect (fixed)

curlhandle 1.9_0 won't build because libcurl.a is a fat file

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: cooljeanius (Eric Gallager)
Port: curlhandle

Description

$ sudo port install curlhandle
--->  Fetching curlhandle
--->  Verifying checksum(s) for curlhandle
--->  Extracting curlhandle
--->  Configuring curlhandle
--->  Building curlhandle
Error: Target org.macports.build returned: shell command "cd "/opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9" && xcodebuild -project CURLHandleSource/CURLHandle.pbproj -alltargets -configuration Deployment build OBJROOT=build/ SYMROOT=build/ " returned error 1
Command output:     exit ${_result}
=== Script ===
#!/bin/sh
# Sequence courtesy of Kevin Enderby.  Changes common symbol into a definition.
# The result is in /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/curl and you could move it back into /usr/local/lib; we
# just leave it here and statically link to it. 
mkdir /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/curl
cd /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/curl
ar x /opt/local/lib/libcurl.a
ld -r -d hostip.o
mv a.out hostip.o
libtool -o libcurl.a *.o
--- Output ---
ar: /opt/local/lib/libcurl.a is a fat file (use libtool(1) or lipo(1) and ar(1) on it)
ar: /opt/local/lib/libcurl.a: Inappropriate file type or format
ld: can't open: hostip.o (No such file or directory, errno = 2)
ld: no object files loaded
mv: rename a.out to hostip.o: No such file or directory
libtool: can't open file: *.o (No such file or directory)
=== Exit code: 1 ===

SymLink /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Versions/Current A
    /bin/ln  -sf A  /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Versions/Current 

Mkdir /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Versions/A/Headers
    /bin/mkdir  -p /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Versions/A/Headers 

SymLink /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Headers Versions/Current/Headers
    /bin/ln  -sf Versions/Current/Headers  /opt/local/var/macports/build/_Users_rschmidt_macports_dports_devel_curlhandle/work/CURLHandle_1.9/CURLHandleSource/build/Deployment/CURLHandle.framework/Headers 
** BUILD FAILED **

Error: Status 1 encountered during processing.
$

Change History (14)

comment:1 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)

I found a note here which says:

To use the source presently available for CURLHandle, you need to upgrade the target, set it to universal, remove the script which tries to link to the static library, and remove the reference to the static curl library in the Other Linker Flags setting (in build settings). After that it should work.

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

There appears to be a binary and source code for a universal curlhandle here.

comment:3 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)

Another source for a universal curlhandle is here.

comment:4 Changed 15 years ago by blb@…

Port: curlhandle added

Looks like curlhandle has been updated to 2.0 and moved to a new home. Maybe 2.0 works?

comment:5 Changed 15 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

comment:6 Changed 11 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

comment:7 in reply to:  1 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

I found a note here which says:

To use the source presently available for CURLHandle, you need to upgrade the target, set it to universal, remove the script which tries to link to the static library, and remove the reference to the static curl library in the Other Linker Flags setting (in build settings). After that it should work.

Once I remove the reference to the static curl library I get a bunch of missing symbols that were supposed to be in it...

comment:8 in reply to:  4 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to blb@…:

Looks like curlhandle has been updated to 3.1.1 and moved to a new home. Maybe 3.1.1 works?

comment:9 in reply to:  8 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

Looks like curlhandle has been updated to 3.1.1 and moved to a new home. Maybe 3.1.1 works?

Opened an issue asking them for help with this here: https://github.com/karelia/CurlHandle/issues/4

comment:10 in reply to:  8 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

Replying to ryandesign@…:

Looks like curlhandle has been updated to 3.1.1 and moved to a new home. Maybe 3.1.1 works?

Looks like it does. r103926

comment:11 in reply to:  10 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

Replying to ryandesign@…:

Looks like curlhandle has been updated to 3.1.1 and moved to a new home. Maybe 3.1.1 works?

Looks like it does. r103926

On all OSes? Last time I tried it, it only worked on Lion and up... (anyway, thanks for the update)

comment:12 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

I only tested Mountain Lion. It failed on the Lion and Snow Leopard buildbots and on my Leopard machine, different reasons in each case.

comment:13 in reply to:  12 Changed 11 years ago by cooljeanius (Eric Gallager)

Replying to ryandesign@…:

I only tested Mountain Lion. It failed on the Lion and Snow Leopard buildbots and on my Leopard machine, different reasons in each case.

So... are you going to try fixing it for those machines, or are you just going to mark it as incompatible with those OS versions?

comment:14 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

New tickets should be filed for any remaining issues, but filing them upstream might be best. I have filed a bug report with the developers about the build failure on Lion: https://github.com/karelia/CurlHandle/issues/8

Note: See TracTickets for help on using tickets.