 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Has anyone managed to get Povray 3.6.1 to build under Cygwin? Configure
fails for me:
...
creating Makefile
creating jconfig.h
configure.gnu: editing Makefile
configure: configuring in libraries/tiff
configure: running /bin/bash './configure.gnu' --prefix=/usr/local
'COMPILED_BY=Ross Smith <ros### [at] pharos conz>' --cache-file=/dev/null
--srcdir=.
configure.gnu: configuring libtiff 3.6.1
configure.gnu: running ./configure --noninteractive --with-DSO=no
--prefix=/usr/local --srcdir=.
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.
Here we are again, this time on a i686-pc-cygwin system.
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.
===============================================================================
POV-Ray 3.6.1 has been configured with the following features:
I/O restrictions: enabled
X Window display: enabled
SVGAlib display : disabled
Type 'make' to build, and 'make install' to install all files in the
hierarchy
/usr/local
===============================================================================
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Has anyone managed to get Povray 3.6.1 to build under Cygwin?
Yes, as cygwin was part of my various testing platforms :-)
> Configuring TIFF Software v3.6.1
> [snip]
> Cannot locate a working ANSI C compiler.
I once or twice faced this situation, but cannot remember now
what was the precise cause. Please send me or post the following file:
libraries/tiff/config.log
Thanks,
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> Has anyone managed to get Povray 3.6.1 to build under Cygwin?
>
>
> Yes, as cygwin was part of my various testing platforms :-)
>
>> Configuring TIFF Software v3.6.1
>> [snip]
>> Cannot locate a working ANSI C compiler.
>
>
> I once or twice faced this situation, but cannot remember now
> what was the precise cause. Please send me or post the following file:
>
> libraries/tiff/config.log
>
> Thanks,
> - NC
Fri Sep 10 09:04:08 NZST 2004
Running ./configure with arguments: --noninteractive --with-DSO=no
--prefix=/usr/local --srcdir=.
This file contains information that is captured from running the configure
script. Lines that begin with a "+" are command lines echoed by the
shell. Other lines are the output of commands; usually the contents of
test case files or the output from compilers. If configure does the
wrong thing, you can use the information captured here to aid in debugging.
+ . ./config.site
+ cat dummy.c
main(int argc, char* argv) { exit(0); }
+ cat xgnu.c
#ifdef __GNUC__
yes;
#endif
+ gcc -E xgnu.c
+ egrep yes
yes;
+ gcc -o dummy -I.././../jpeg -L/usr/X11R6/lib dummy.c
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> + 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 (however libjpeg apparently was correctly
configured, right ?).
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 ;-)
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> 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.
Please try to run the following:
echo "main(int argc, char* argv) { exit(0); }" > dummy.c
gcc -o dummy dummy.c
It should report an error if there is a problem with the
Cygwin installation (such as some missing devel package maybe).
In this case, please run again gcc, this time with:
gcc -v -o dummy dummy.c
and report all the console messages that you get.
> Sorry, I don't know enough about the configure process to answer that.
The best would be to send me the config.log file you get in
the main POV-Ray source tree, as well as that of the support library
that is has configured. You can find all those config.log files
running the following command: find -type f -name config.log
You should get a subset of:
./config.log
./libraries/zlib/config.log
./libraries/png/config.log
./libraries/tiff/config.log
./libraries/jpeg/config.log
Please send me all of those files.
> Why is it trying to build libjpeg and libtiff anyway? Cygwin already
> has them.
This is answered if you look at what POV-Ray's configure outputs
on the console. Hint: look at the library versions. In case of cygwin,
libjpeg is always built, forcing libtiff to build as well. There are
good reasons for that.
>> ./configure LDFLAGS=/usr/local/include
> Doesn't work:
Yes, sorry I did a small mistake. Try again with:
./configure LDFLAGS=-I/usr/local/include
but honestly I don't think it will work either. That's why I'd
like to get your log files to check things carefully. Thanks.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>> 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.
>
>
> Please try to run the following:
>
> echo "main(int argc, char* argv) { exit(0); }" > dummy.c
> gcc -o dummy dummy.c
This runs without complaint. (I'd forgotten how permissive GCC
is in its default mode; I always turn up the warnings to 11 on
my own code.)
> It should report an error if there is a problem with the
> Cygwin installation (such as some missing devel package maybe).
> In this case, please run again gcc, this time with:
>
> gcc -v -o dummy dummy.c
>
> and report all the console messages that you get.
Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/specs
Configured with: /gcc/gcc-3.3.3-3/configure --verbose --prefix=/usr
--exec-prefix=/usr --sysconfdir=/etc --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--enable-languages=c,ada,c++,d,f77,java,objc,pascal --enable-nls
--without-included-gettext --enable-libgcj --with-system-zlib
--enable-interpreter --enable-threads=posix --enable-java-gc=boehm
--enable-sjlj-exceptions --disable-version-specific-runtime-libs
--disable-win32-registry
Thread model: posix
gcc version 3.3.3 (cygwin special)
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/cc1.exe -quiet -v -D__GNUC__=3
-D__GNUC_MINOR__=3 -D__GNUC_PATCHLEVEL__=3 -D__CYGWIN32__ -D__CYGWIN__
-Dunix -D__unix__ -D__unix -idirafter
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../include/w32api
-idirafter /usr/local/lib/../../include/w32api dummy.c -quiet -dumpbase
dummy.c -auxbase dummy -version -o
/cygdrive/d/DOCUME~1/rosss/LOCALS~1/Temp/ccNfogM4.s
GNU C version 3.3.3 (cygwin special) (i686-pc-cygwin)
compiled by GNU C version 3.3.3 (cygwin special).
GGC heuristics: --param ggc-min-expand=99 --param ggc-min-heapsize=131004
ignoring nonexistent directory "/usr/i686-pc-cygwin/include"
ignoring duplicate directory "/usr/local/include"
ignoring duplicate directory "/usr/include/w32api"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/include
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/include
/usr/include
/usr/include/w32api
End of search list.
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../../i686-pc-cygwin/bin/as.exe
--traditional-format -o
/cygdrive/d/DOCUME~1/rosss/LOCALS~1/Temp/ccUSHyX7.o
/cygdrive/d/DOCUME~1/rosss/LOCALS~1/Temp/ccNfogM4.s
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/collect2.exe -Bdynamic
--dll-search-prefix=cyg -o dummy.exe
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../crt0.o
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/crtbegin.o -L/usr/local/lib
-L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3
-L/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../..
/cygdrive/d/DOCUME~1/rosss/LOCALS~1/Temp/ccUSHyX7.o -lgcc -lcygwin
-luser32 -lkernel32 -ladvapi32 -lshell32 -lgcc
/usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/crtend.o
>> Sorry, I don't know enough about the configure process to answer that.
>
> The best would be to send me the config.log file you get in
> the main POV-Ray source tree, as well as that of the support library
> that is has configured. You can find all those config.log files
> running the following command: find -type f -name config.log
> You should get a subset of:
>
> ./config.log
> ./libraries/zlib/config.log
> ./libraries/png/config.log
> ./libraries/tiff/config.log
> ./libraries/jpeg/config.log
>
> Please send me all of those files.
Mailed separately.
>> Why is it trying to build libjpeg and libtiff anyway? Cygwin already
>> has them.
>
> This is answered if you look at what POV-Ray's configure outputs
> on the console. Hint: look at the library versions. In case of cygwin,
> libjpeg is always built, forcing libtiff to build as well. There are
> good reasons for that.
It doesn't say anything about version numbers. The relevant
output (I think) is:
Libraries
---------
checking whether to enable static linking... no
checking for sin in -lm... yes
checking for asinh... yes
checking for vga_init in -lvga... no
configure: SVGAlib display will be disabled
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... yes
checking for XFlush in -lX11... yes
checking for XpmCreatePixmapFromData in -lXpm... yes
checking whether to enable the watch cursor... no
checking for installed supporting libraries... yes
checking for library containing zlibVersion... -lz
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for libz version >= 1.2.1... 1.2.1, ok
checking for library containing png_get_libpng_ver... -lpng12
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for libpng version >= 1.2.5... 1.2.5, ok
checking for libjpeg... forced by cygwin
configure: libjpeg will be built and statically linked to POV-Ray
checking for libtiff... forced by libjpeg
configure: libtiff will be built and statically linked to POV-Ray
>>> ./configure LDFLAGS=/usr/local/include
>>
>> Doesn't work:
>
>
> Yes, sorry I did a small mistake. Try again with:
>
> ./configure LDFLAGS=-I/usr/local/include
>
> but honestly I don't think it will work either.
Nope.
--
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
i was able to compile Povray 3.6.1 under cygwin. Cygwin was a fresh
installation with ALL modules.
(Latest version of cygwin)
With the default installation of cygwin there was no C99 compatibility
(compiling failed due missing
vsnprintf()? function)
1st try failed because the source files were in a directory with spaces
C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1
2nd try with
D:\local_dev\Privat\cygwin\povray-3.6.1
was successful.
The same applies with megapov 1.1 sources.
After compiling i 've tried some test renders -> no problems (there was
some difficulties with the path to the .ini files).
Sorry for my poor english...
Hope, this helps...
Zan
PS.: for valid email adress, please remove "REMOVE"
>Has anyone managed to get Povray 3.6.1 to build under Cygwin? Configure
>fails for me:
>
>...
>creating Makefile
>creating jconfig.h
>configure.gnu: editing Makefile
>
>configure: configuring in libraries/tiff
>configure: running /bin/bash './configure.gnu' --prefix=/usr/local
'COMPILED_BY=Ross Smith <ros### [at] pharosconz>' --cache-file=/dev/null
--srcdir=.
>configure.gnu: configuring libtiff 3.6.1
>configure.gnu: running ./configure --noninteractive --with-DSO=no
--prefix=/usr/local --srcdir=.
>
>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.
>Here we are again, this time on a i686-pc-cygwin system.
>
>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.
>
>
>
>========================
D========================
D========================
D====
>POV-Ray 3.6.1 has been configured with the following features:
> I/O restrictions: enabled
> X Window display: enabled
> SVGAlib display : disabled
>
>Type 'make' to build, and 'make install' to install all files in the
hierarchy
>/usr/local
>========================
D========================
D========================
D====
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> echo "main(int argc, char* argv) { exit(0); }" > dummy.c
>> gcc -o dummy dummy.c
> This runs without complaint.
Mmmh this is getting interesting ;-)
Did you run a bash or (t)csh shell for doing this test ?
It could be that the environment is different than when running
the libtiff configure (but I don't think it is).
> gcc version 3.3.3 (cygwin special)
Okay, you probably have (one of) the latest cygwin release(s).
> #include "..." search starts here:
> #include <...> search starts here:
> /usr/local/include
> /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/include
> /usr/include
> /usr/include/w32api
Looks okay indeed.
> Mailed separately.
Thanks, I'm gonna inspect this today.
> checking for libjpeg... forced by cygwin
> configure: libjpeg will be built and statically linked to POV-Ray
> checking for libtiff... forced by libjpeg
> configure: libtiff will be built and statically linked to POV-Ray
So it corresponds to what I wrote before.
Hopefully, with the help of your log files I'll get an idea
of what's going on. Unfortunately I don't have cygwin again today,
so that'll be somewhat harder to do some real testing.
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> With the default installation of cygwin there was no C99 compatibility (compiling
failed due missing
> vsnprintf()? function)
POV-Ray's configure didn't complain it cannot find vsnprintf() ?
Normally it should.
> 1st try failed because the source files were in a directory with spaces
> C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1
Yes, that's an usual Cygwin problem. My testing environment was
also including paths with spaces to try to cope with this as much as
possible, but apparently I still missed some cases.
Could you send me the various config.log files you obtained in
this situation ?
> The same applies with megapov 1.1 sources.
That's expected :-)
> (there was some difficulties with the path to the .ini files).
Please describe this problem.
Thanks,
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
