Re: Issue compiling last 3.1 squid in 64-bit platform

Just tried in Ubuntu 9.10 64-bit and it worked. I think it's something
specific to Slackware 13.0 64BIT...

Can I help, anyway?

Thanks!

> Sorry for the "Worked like a charm!" line in my email. It was a mistake. I
> was writing the email while the software was compiling and I thought it
> worked. When I saw it didn't, I forgot to erase the first line. Blame on
> me!
>
> Sorry!
>
>> Worked like a charm!
>>
>> I tried to compile it using no options in configure, but I still get the
>> same error in Slackware-64:
>>
>> rm -f libDiskDaemon.a
>> /usr/bin/ar cru libDiskDaemon.a DiskIO/DiskDaemon/DiskdFile.o
>> DiskIO/DiskDaemon/DiskdIOStrategy.o
>> DiskIO/DiskDaemon/DiskDaemonDiskIOModule.o
>> ranlib libDiskDaemon.a
>> make[3]: *** No rule to make target `-lpthread', needed by `all-am'.
>> Stop.
>> make[3]: Leaving directory `/home/sources/squid-3.1.0.14-BZR/src'
>> make[2]: *** [all-recursive] Error 1
>> make[2]: Leaving directory `/home/sources/squid-3.1.0.14-BZR/src'
>> make[1]: *** [all] Error 2
>> make[1]: Leaving directory `/home/sources/squid-3.1.0.14-BZR/src'
>> make: *** [all-recursive] Error 1
>>
>>
>> Is your Fedora 11 64-bit? I will install Ubuntu-64 and try to compile it
>> in the same server. As soon as I have the results I'll post back to you!
>>
>> Thanks again!
>>
>>
>>
>> No problems at all this time!
>>
>>> can you try ftp://ftp.squid-cache.se/private/squid-3.1.0.14-BZR.tar.bz2
>>> (snapshot of current sources in bzr)
>>>
>>> this is fixed so that it builds for me on Fedora 11.
>>>
>>>
>>> tis 2009-11-10 klockan 09:14 -0200 skrev renator_at_flash.net.br:
>>>> If you need me to do any type of specific test or use any compile
>>>> options,
>>>> please let me know and I would be glad to help!
>>>>
>>>> Thanks again for your effort!
>>>>
>>>> > tis 2009-11-10 klockan 23:41 +1300 skrev Amos Jeffries:
>>>> >
>>>> >> Yet I ported those fixes down and he still reports it in the
>>>> snapshot
>>>> >> built afterwards. :(
>>>> >
>>>> > I think something went wrong in that port, the build farm also
>>>> failed..
>>>> >
>>>> > was a number of iterations in trunk before it worked right.
>>>> >
>>>> > Regards
>>>> > Henrik
>>>> >
>>>> >
>>>>
>>>
>>>
>>
>>
>>
>
>
>
Received on Tue Nov 10 2009 - 16:38:39 MST