[squid-users] Re: squid-users Digest 23 Jan 2014 17:39:48 -0000 Issue 4421

Thank you Amos for your answer!

I am using these cross compiler flags (that seems right for me):
  --build=x86_64-linux
  --host=i586-oe-linux
  --target=i586-oe-linux

Configure exit with this error:
checking for GNU atomic operations support... configure: error: in
`/<real_long_path>/tmp-eglibc/work/x86-oe-linux/squid/3.3.11-r19.9/squid-3.3.11':
configure: error: cannot run test program while cross compiling

Here are some details of my build machine:
It was created by Squid Web Proxy configure 3.3.11, which was
generated by GNU Autoconf 2.69.

automake (GNU automake) 1.12.6

uname -m = x86_64
uname -r = 2.6.32-5-xen-amd64
uname -s = Linux
uname -v = #1 SMP Fri May 10 11:48:05 UTC 2013

What can be the issue?

Cheers,
Stefano.

On 01/23/2014 06:39 PM, squid-users-digest-help_at_squid-cache.org wrote:
>
> On 23/01/2014 10:39 p.m., Stefano Cordibella wrote:
>> >Hi list,
>> > I am trying to compile squid 3.3.11 in our openembedded environment,
>> >but the configure step fails due to a cross compile check.
>> >In version 3.1.23 there wasn't those checks and the build goes well...
>> >
>> >So my questions are:
>> >1) why from version 3.2 these checks are included in configure?
> The change in behaviour is from newer autoconf being used to generate
> the code tarballs. One of the reasons for that was to get better/easier
> cross-compiling support.
>
>
>> >2) are there any way to cross compile 3.3 (or 3.4)?
> You should only** have to specify the ./configure options to tell it
> which OS the compile is happening on (--build=X) and which OS type will
> run the binary (--host=Y).
>
> What exactly is the failure you are encountering?
>
>
> ** besides having the appropriate *-dev library versions installed for
> cross-compiling against and tools that can cross-compile.
>
>
>> >3) I read in the FAQ that from version 3.2 C++11 compilers is required,
>> >I am using gcc 4.7.2, is it a supported compiler?
> Not required. "Preferred" is the word for it. We have code to make use
> of some C++11 only when available. Mostly we are taking advantage of the
> increased compiler code checking in our build farm to remove bugs before
> anyone notices them:-)
>
> The switch to mandatory C++11 support for general builds is still being
> discussed on squid-dev and IRC as to when the timing would offer least
> pain for everyonea and how long we can procrastinate on it. It might
> happen around Squid-3.6.
>
> Any GCC 4.0+ (excluding 4.5 with broken stdlib definitions of
> auto_ptr/unique_ptr) should work fine for Squid-3.2 and later. The later
> versions are better though with more general C++11 support benfits than
> the older ones.
>
> Cheers
> Amos

-- 
*Stefano Cordibella*
EDALab s.r.l. - Networked Embedded Systems
Strada Le Grazie, 15 - 37134 Verona - Italy
email : stefano.cordibella_at_edalab.it
skype : stefano.cordibella
tel. : +39 045 802 70 85
web : www.edalab.it