[
https://issues.apache.org/jira/browse/XERCESC-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768375#action_12768375
]
James Berry commented on XERCESC-1892:
--------------------------------------
So we fixed two things:
- How we detect curl (I believe this is now correct)
- How we decide what to pass the compiler/linker
To address Boris' concern that curl-config may not be available on all
releases, we could test for the existence of curl-config in step 2, falling
back to the previous hard-coded -lcurl behavior if doesn't. Since we didn't
seem inundated with bug reports about that, presumably it was working
relatively well. If we do this, we'd want to remove the additional test I
added, where we check for a curl-config while searching for a curl to use.
I'll point out that the primary bug identified in this bug report is arguably
not a bug at all. I don't believe there's necessarily a requirement that we
should search prefix for curl, and there's an easy workaround, which is to pass
--with-curl=$prefix to configure. In any event, we now _do_ look in $prefix for
curl.
As a further note, curl-config has apparently been around since curl 7.7.2 in
2001: http://marc.info/?l=curl-announce&m=100204193222862&w=2
> configure irationally forces -L/usr/local/lib
> ----------------------------------------------
>
> Key: XERCESC-1892
> URL: https://issues.apache.org/jira/browse/XERCESC-1892
> Project: Xerces-C++
> Issue Type: Bug
> Affects Versions: 3.0.1
> Reporter: Philip Brown
>
> I am building two sets of tool chains. one 32bit, in /usr/local.
> Another one, 64bit, in /usr/local/64
> I have taken everything referencing /usr/local out of my environment, and
> have successfully compiled other software. However, when it comes to xerces-c
> 3.0.1, even though I have explicitly told it
> --prefix=/usr/local/64
> it insists on adding -L/usr/local/lib for curl or something.
> I dont know for sure that curl is the reason why it is added.. but it PICKS
> UP /usr/local/lib/libcurl.la from that, and then screws up my nice 64bit
> build, by attempting to link in /usr/local/lib/libcurl.so
> When I temporarily remove libcurl.la from there, it compiles. but this is not
> an acceptible workaround.
> Actually, it would appear that specifying --with-curl=/usr/local/64
> overrides, but this is inappropriate! it should check in $prefix FIRST, not
> decide to go look in /usr/local for curl before anything else.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
