Nicolas Calimet wrote:
>> + gcc -o dummy -I.././../jpeg -L/usr/X11R6/lib dummy.c
> 
> 
>     I'm suprised you don't get any warning or error message after
> this last line (maybe you did miss it when copying-pasting the
> file content...).
> 
>     While I cannot test at the moment, I kinda remember that this
> test can fails because of the dummy.c file created by the libtiff's
> configure:
> 
> main(int argc, char* argv) { exit(0); }
> 
>     It should have a "#include <stdlib.h>" before main().  Here,
> it's likely that gcc cannot find stdlib.h and fails to compile dummy.c
> because of the call to  exit().  That somehow tells you have a problem
> with your Cygwin installation

How do you make that out? I can't see how it's a problem with Cygwin
if it fails to compile an invalid program.

 > (however libjpeg apparently was correctly
> configured, right ?).

Sorry, I don't know enough about the configure process to answer that.

Why is it trying to build libjpeg and libtiff anyway? Cygwin already
has them.

>     You might try to configure libtiff alone, passing LDFLAGS
> that contains the path to the stdlib.h header, usually /usr/local/include
> 
> cd libraries/tiff
> ./configure LDFLAGS=/usr/local/include
> 
>     I know it's weird to pass LDFLAGS here (and I don't guaranty it
> will solve the problem), but libtiff is weird anyway  ;-)

Doesn't work:

Configuring TIFF Software v3.6.1

If configure does the wrong thing, check the file config.log for
information that may help you understand what went wrong.

Reading site-wide parameters from ./config.site.

Cannot locate a working ANSI C compiler.

We attempted to compile the following test program:

----------------------------------------------------------
main(int argc, char* argv) { exit(0); }
----------------------------------------------------------

with these compilers:

      gcc

but none of them were successful.

If your compiler is in a non-standard location, you can specify its
location in several ways:

     o set the environment variable CC
     o create a config.local or config.site file that includes a
       definition for CC
     o supply it on the command line using -with-CC=<pathname>

If command line options are required for ANSI C compilation, set the
ENVOPTS parameter to these options in a similar way (either through
an environment variable or config.local/config.site) and then rerun
this script.
configure:
configure: Unrecoverable error!  Once you've corrected the problem rerun 
this script.


-- 
Ross Smith ...................... Pharos Systems, Auckland, New Zealand
"Carelessly planned projects take three times longer to complete than
expected. Carefully planned projects take four times longer to
complete than expected, mostly because the planners expect their
planning to reduce the time it takes." -- Anon.

Post a reply to this message