Re: Windows compilation error

On 31/07/2013 12:43 p.m., Henrik Nordström wrote:
> Found this expired in the list moderation queue.
>
> Sorry, can't really help much with mingw build environment issues but
> maybe someone on the list knows? or at least what mingw installation
> documentation to read?
>
>
> ons 2013-05-15 klockan 14:25 +0100 skrev Srini:
>> Hi,
>>
>> I am trying to compile Squid 3.3.4 on Windows following the
>> instructions found in the following page:
>>
>> http://wiki.squid-cache.org/KnowledgeBase/Windows#Compiling_with_MinGW
>>
>> I was asked to download OpenSSL, libcrypt, TinyCOBOL. The page
>> apparently does mention anything about what to do with the downloaded
>> stuff. I assume that I should copy them to c:\mingw\inclides and lib.

TinyCOBOL is referenced because that project offer a Berkley DB library
suitable for MinGW. It is that library which Squid needs, not the
TinyCOBOL system itself. That said their library is very old and Squid
3.3 needs a version 4.6 or later, not the 2.x/1.85 which they provide.
If you don't need the session helper you can skip this dependency.

There are ./configure --with-* flags to tell Squid where the you placed
them. So there may be some best place, but it does not matter a lot
where they go. It helps avoid problems if there are no whitespaces in
the path you choose though.

>> However after copying the lib and includes I tried running the
>> ./configure from a MinGW Shell. I get the following error:
>>
>> checking whether to build shared libraries... yes
>> checking whether to build static libraries... yes
>> checking how to run the C++ preprocessor... /lib/cpp
>> configure: error: in
>> `/c/Users/srini/SoftwareInstallers/Windows/SquidCompilation
>> /squid-3.3.4':
>> configure: error: C++ preprocessor "/lib/cpp" fails sanity check
>> See `config.log' for more details
>>
>> I have also attached the config.log.
>>
>> I have also tried creating a softlink to the C:\MinGW\bin\cpp.exe in
>> /lib from the MinGW Shell
>>
>> Please help me in getting this compiled. Please let me know if you need
>> more information in this regard.

Sounds like MinGW is corrupted or missing something.

If the OpenSSL and libcrypt files were moved over the top of existing
MinGW files that may be related. It might be better to keep each in a
separate directory, or perhapse the libarry packages have some install
system to insert their details into the correct places?

Amos
Received on Wed Jul 31 2013 - 01:23:35 MDT