 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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] 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.
>
>
>
>========================
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> 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.
It did complain. The checking for this function has failed... Sorry, i
express myself wrong.
>
>> 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 resulting config.log file was sent to your email address
>
>> 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.
After "make install" i tried to render some scenes with default command
line parameter:
Example: POVRAY +Iscene.pov +Oscene.tga +FT +W160 +H200 +V -D +X
The default povray.ini in $HOME/.povray/3.6 wasn't used -> p.ex.
colors.inc not found
With following command line the render was successful (for Megapov 1.1,
the same with vanilla povay 3.6.1):
$ MEGAPOV $HOME/.povray/povray.ini +Ibear.pov +Otest.tga +FT +W640 +H480
+V -D
+X +L/usr/local/share/megapov-1.1\include
I think, this was a problem of my fresh cygwin installation and not of
povray itself.
Or is this a problem of "make install"?
Zan
>
> Thanks,
> - NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> It did complain. The checking for this function has failed.
Okay, thanks for the confirmation.
> The resulting config.log file was sent to your email address
This file says the main configuration succeeded. Since you are
on cygwin, libjpeg and libtiff were also configured. However, as
I didn't get the corresponding config.log files, I can only assume
their configuration succeeded (the next POV-Ray release will make
sure of that).
Therefore the path-with-blank-or-unusual-caracters problem
you report is likely happening either at build time ('make') or
at installation time ('make install'). Can you show me the context
in which the error happens ? Please report the last 50 lines of
the console output including the build error.
> After "make install" i tried to render some scenes with default command line
parameter:
> Example: POVRAY +Iscene.pov +Oscene.tga +FT +W160 +H200 +V -D +X
Note that the +Oscene.tga parameter is unnecessary here.
> The default povray.ini in $HOME/.povray/3.6 wasn't used -> p.ex. colors.inc not
found
("p.ex." -> do you happen to speak french ? ;-)
If the $HOME/.povray/3.6/povray.ini file exists, it will be used.
However, it might be that the Library_Path's are somewhat screwed up.
Please report the content of this file ('cat $HOME/.povray/3.6/povray.ini').
> With following command line the render was successful (for Megapov 1.1, the same
with vanilla povay 3.6.1):
>
> $ MEGAPOV $HOME/.povray/povray.ini +Ibear.pov +Otest.tga +FT +W640 +H480 +V -D
> +X +L/usr/local/share/megapov-1.1\include
Two things here:
1) If $HOME/.povray/povray.ini contains "bad" Library_Path entries as guessed
above, it won't help to specify it on the command-line.
2) I suppose you did a typo in +L/usr/local/share/megapov-1.1\include since
the last backslash is wrong*. Assuming you actually have "megapov-1.1/include"
and that it works as is, it means the installation managed to place the files
under /usr/local/share/megapov-1.1/include, but for some reason povray.ini
is missing this path.
(*) Not sure if and how cygwin copes with mixed POSIX and non-POSIX paths.
> I think, this was a problem of my fresh cygwin installation and not of povray
itself.
> Or is this a problem of "make install"?
In your case I'd say both :-) Cygwin should be in fault when you have
paths with spaces (first problem), and POV-Ray's install might do something bad
(second problem).
To summarize, I'd like you show me (or send, when adequate) the
following:
1) If they exist
C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1\libraries\libjpeg\config.log
C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1\libraries\libtiff\config.log
2) The error message + last 50 lines of running 'make' or 'make install' from the
C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1 directory
3) Content of $HOME/.povray/3.6/povray.ini that you obtained after installing
from D:\local_dev\Privat\cygwin\povray-3.6.1
Thanks again,
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>> $ MEGAPOV $HOME/.povray/povray.ini +Ibear.pov +Otest.tga +FT +W640
By the way, I'd rather expect $HOME/.povray/3.6/povray.ini here
(i.e. there's a missing 3.6/ in the path to povray.ini).
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
to 1.) I have found the according log files. Send to you by email.
to 2.)
ztv@ztv-0 /cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygwin/povray-3.6.1
$ make
make all-recursive
make[1]: Entering directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygw
in/povray-3.6.1'
Making all in libraries
make[2]: Entering directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygw
in/povray-3.6.1/libraries'
Making all in jpeg
make[3]: Entering directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygw
in/povray-3.6.1/libraries/jpeg'
make[3]: Nothing to be done for `all'.
make[3]: Leaving directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygwi
n/povray-3.6.1/libraries/jpeg'
Making all in tiff/port
make[3]: Entering directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygw
in/povray-3.6.1/libraries/tiff/port'
make[3]: *** No rule to make target `all'. Stop.
make[3]: Leaving directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygwi
n/povray-3.6.1/libraries/tiff/port'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygwi
n/povray-3.6.1/libraries'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/cygdrive/c/Programme/POV-Ray for Windows
v3.6/cygwi
n/povray-3.6.1'
make: *** [all] Error 2
to 3.)
; PERSISTENCE OF VISION RAY TRACER
;
; POV-Ray VERSION 3.6
;
; SAMPLE POVRAY.INI FILE
;
; The general form of the options is "Variable=value". Everything
; between the equals sign and the end of the line is considered part
; of the value. The spacing and layout is free-form but only one option
; per line is allowed. Variables and values are not case-sensitive.
;
; Note: characters after a semi-colon are treated as a comment
;
; Traditional POV-Ray switches beginning with + or - are also allowed
; and they may be given with more than one switch per line.
;
; Add your own options at the bottom and/or edit these to suit. See the
; general documentation for full instructions on how to use INI options.
;
; Width of image in pixels. Accepts integer values.
;
Width = 320
;
;
; Height of image in pixels. Accepts integer values.
;
Height = 240
;
; Sets minimum number of objects before auto bounding kicks in.
;
Bounding_Threshold = 3
;
;
; Turn display on
Display=On
;
; Turn verbose mode on
Verbose=On
;
;
; Specify path to search for any files not found in current
; directory. Up to 20 such paths may be specified. For example -
; Library_Path="C:\Program Files\POV-Ray for Windows\include"
; There may be some entries already here; if there are they were
; probably added by the install process or whoever set up the
; software for you. At the least you can expect an entry that
; points to the standard POV-Ray include files directory; on
; some operating systems there may also be one which points to
; the system's fonts directory.
;
; Note that some platforms (e.g. Windows, unless this feature is
; turned off via the configuration file) will automatically append
; standard locations like those mentioned above to the library
; path list after reading this file, so in those cases you don't
; necessarily have to have anything at all here.
;
;; Search path for #include source files or command line ini files not
;; found in the current directory. New directories are added to the
;; search path, up to a maximum of 25.
Library_Path="/usr/local/share/povray-3.6"
Library_Path="/usr/local/share/povray-3.6/ini"
Library_Path="/usr/local/share/povray-3.6/include"
Library_Path="/usr/local/share/megapov-1.1/include"
;; File output type control.
;; T Uncompressed Targa-24
;; C Compressed Targa-24
;; P UNIX PPM
;; N PNG (8-bits per colour RGB)
;; Nc PNG ('c' bit per colour RGB where 5 <= c <= 16)
Output_to_File=true
Output_File_Type=N8 ;; (+/-Ftype)
That's all.
Hope, this helps
>> It did complain. The checking for this function has failed.
>
> Okay, thanks for the confirmation.
>
>> The resulting config.log file was sent to your email address
>
> This file says the main configuration succeeded. Since you are
>on cygwin, libjpeg and libtiff were also configured. However, as
>I didn't get the corresponding config.log files, I can only assume
>their configuration succeeded (the next POV-Ray release will make
>sure of that).
> Therefore the path-with-blank-or-unusual-caracters problem
>you report is likely happening either at build time ('make') or
>at installation time ('make install'). Can you show me the context
>in which the error happens ? Please report the last 50 lines of
>the console output including the build error.
>
>> After "make install" i tried to render some scenes with default command
line parameter:
>> Example: POVRAY +Iscene.pov +Oscene.tga +FT +W160 +H200 +V -D +X
>
> Note that the +Oscene.tga parameter is unnecessary here.
>
>> The default povray.ini in $HOME/.povray/3.6 wasn't used -> p.ex.
colors.inc not found
>
> ("p.ex." -> do you happen to speak french ? ;-)
Only 3 years of french at german technical gymnasium -> my skills are more
worsed than english :-(((
Je ne compris pas francaise beaucoup... Un peu... ;-)
>
> If the $HOME/.povray/3.6/povray.ini file exists, it will be used.
>However, it might be that the Library_Path's are somewhat screwed up.
>Please report the content of this file ('cat
$HOME/.povray/3.6/povray.ini').
>
>> With following command line the render was successful (for Megapov 1.1,
the same with vanilla povay 3.6.1):
>>
>> $ MEGAPOV $HOME/.povray/povray.ini +Ibear.pov +Otest.tga +FT +W640
+H480 +V -D
>> +X +L/usr/local/share/megapov-1.1\include
>
> Two things here:
>
>1) If $HOME/.povray/povray.ini contains "bad" Library_Path entries as
guessed
>above, it won't help to specify it on the command-line.
>
>2) I suppose you did a typo in +L/usr/local/share/megapov-1.1\include
since
>the last backslash is wrong*. Assuming you actually have
"megapov-1.1/include"
>and that it works as is, it means the installation managed to place the
files
>under /usr/local/share/megapov-1.1/include, but for some reason povray.ini
>is missing this path.
Yes, this was a typo... :-(
>
>(*) Not sure if and how cygwin copes with mixed POSIX and non-POSIX paths.
>
>> I think, this was a problem of my fresh cygwin installation and not of
povray itself.
>> Or is this a problem of "make install"?
>
> In your case I'd say both :-) Cygwin should be in fault when you have
>paths with spaces (first problem), and POV-Ray's install might do
something bad
>(second problem).
>
> To summarize, I'd like you show me (or send, when adequate) the
>following:
>
>1) If they exist
>C:\Programme\POV-Ray for Windows
v3.6\cygwin\povray-3.6.1\libraries\libjpeg\config.log
>C:\Programme\POV-Ray for Windows
v3.6\cygwin\povray-3.6.1\libraries\libtiff\config.log
>
>2) The error message + last 50 lines of running 'make' or 'make install'
from the
>C:\Programme\POV-Ray for Windows v3.6\cygwin\povray-3.6.1 directory
>
>3) Content of $HOME/.povray/3.6/povray.ini that you obtained after
installing
>from D:\local_dev\Privat\cygwin\povray-3.6.1
>
> Thanks again,
> - NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> make[3]: Entering directory `/cygdrive/c/Programme/POV-Ray for Windows v3.6/cygw
> in/povray-3.6.1/libraries/tiff/port'
> make[3]: *** No rule to make target `all'. Stop.
Okay, so it's quite a different problem, and that one was already
reported before. I hope I will now be able to see what's wrong here too...
> Library_Path="/usr/local/share/povray-3.6"
> Library_Path="/usr/local/share/povray-3.6/ini"
> Library_Path="/usr/local/share/povray-3.6/include"
> Library_Path="/usr/local/share/megapov-1.1/include"
Well, I don't see any problem here...
- NC
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Nicolas Calimet wrote:
>>> 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 ?
bash
> 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).
Yes, I made sure I updated to the latest Cygwin installation before
reporting the problem with Povray. I later had to downgrade the Cygwin
DLL from 1.5.11 to 1.5.10 because the pthread bug in 1.5.11 broke some
other programs, but that didn't make any difference to Povray.
--
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
|
|
| |
| |
|
|
|
|
| |
|
|
