[ 
https://issues.apache.org/jira/browse/XERCESC-1892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768415#action_12768415
 ] 

Scott Cantor commented on XERCESC-1892:
---------------------------------------

I happen to agree and actually would prefer it didn't search $prefix by 
default, as I think that's not intended behavior, but I won't go to the mat 
over it.

It's absolutely a bug to search non-system locations for anything by default 
(/usr/local). It's arguably a bug to search anything but the path that way, 
since /usr/bin might give you a 32-bit version with a 64-bit version located 
elsewhere. So my suggestion remains to search the path and nothing else, and 
force use of --with if you want explicit control.

Regarding curl-config, that's now standard as you saw, so a fallback isn't 
really needed. It's also inadvisable because curl can be built with a lot of 
options that may require flags downstream, and the last thing you want is a 
build that appears to work but doesn't.

Just my 2 cents.

> 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]

Reply via email to