[XERCESC-1853] configure incorrectly detects curl in cross-compile build

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.0.0
• Fix Version/s: 3.1.0
• Component/s: Build
• Environment: Linux 2.6.27-gentoo-r8 #1 SMP PREEMPT Tue Jan 27 11:07:48 CET 2009 i686 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
• Assignee: Unassigned
• Reporter: Miroslav Kes
• Created: 02/Feb/09 12:13
• Updated: 10/Nov/09 07:50
• Resolved: 10/Nov/09 07:50

Description

I' trying to cross-compile xerces-c for ARM/Xscale. Build host Linux x86, target platform Xcale BE.
The configure script detects presence of curl as the NetAccessor candidate based on presence of /usr/include/curl/* on the build host not in the cross-compile toolchain.

Example:
My cross compile toolchain is installed under /opt/clfs/armv5teb-softfloat-linux-gnueabi so when invoking configure scripte like

~/tmp/xerces-c-3.0.0 $ ./configure --host=armv5teb-softfloat-linux-gnueabi

I get this output:
...
checking for libcurl... /usr
checking whether we can support the libcurl-based NetAccessor... yes
checking whether we can support the sockets-based NetAccessor... yes
checking for which NetAccessor to use (choices: curl socket)... curl
...

The configure script should check headers and libraries under /opt/clfs/armv5teb-softfloat-linux-gnueabi/usr/include resp. /opt/clfs/armv5teb-softfloat-linux-gnueabi/usr/lib. In my case there is no curl directory under /opt/clfs/armv5teb-softfloat-linux-gnueabi/usr/include but the configure script detects curl as installed chooses it as the preferred NetAccessor.
Instead, it likely checks the /usr/include of the build host because If I rename it to let's say /usr/include/curl.bak the .configure script doesn't find curl and uses socket as the preferred NetAccessor.

There is a workaround to use the --disable-netaccessor-curl option but the configure script should work correctly with default settings.