#15116 closed defect (fixed)
curl-config returns inappropriate flags
Reported by: | jmroot (Joshua Root) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: |
Description
With curl built universal:
% curl-config --libs -L/opt/local/lib -lcurl -L/opt/local/lib -arch i386 -arch ppc -L/opt/local/lib -L/opt/local/lib -lssl -lcrypto -lssl -lcrypto -lz -lz % curl-config --static-libs /opt/local/lib/libcurl.a -L/opt/local/lib -arch i386 -arch ppc -L/opt/local/lib -L/opt/local/lib -lssl -lcrypto -lssl -lcrypto -lz -lz
The output from all the other options seems OK. The redundancy isn't a real problem, but the -arch flags are, when building something non-universal that uses curl-config.
Change History (5)
comment:1 follow-up: 2 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
comment:2 Changed 17 years ago by jmroot (Joshua Root)
Replying to ryandesign@macports.org:
What software are you building that's using curl-config?
I noticed it with gnupg2.
comment:3 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | new → closed |
Should be fixed in r36442; please verify.
Note: See
TracTickets for help on using
tickets.
Oh. I fixed this for curl's pkg-config file with r33404, see #14077. curl-config should be easy to patch in a similar way.
What software are you building that's using curl-config?