|
|
I haven't found a bug reporting mechanism, so I hope that the
person who maintains the unix version checks this list now and then.
On Solaris 9 with the compiler in /opt/SUNWspro (i.e NOT GCC)
I get a mismatch between the prototypes in config.h and the
actual functions in unix.cpp
The functions in question are
UNIX_Allow_File_Read()
UNIX_Allow_File_Write()
and the problem is that the version in config.h has a "const" that
the actual function definition is missing. This means the names
mangle differently, and results in a link error.
Post a reply to this message
|
|
|
|
Just for more info, to fix this problem remove the second const in the
prototypes in config.h
config.h
--------------------------
UNIX_Allow_File_Write PARAMS((const char *Filename, const unsigned int
FileType));
UNIX_Allow_File_Read PARAMS((const char *Filename, const unsigned int
FileType));
goes to
UNIX_Allow_File_Write PARAMS((const char *Filename, unsigned int FileType));
UNIX_Allow_File_Read PARAMS((const char *Filename, unsigned int FileType));
Also thanks for the info Richard. I was getting a linker error with the Sun
compiler on file_pov.o and it would compile fine under Gcc and I had no idea
where to look since the function was not defined in file_pov.cpp!
Also I had to download libtiff (www.libtiff.org) and compile it myself with
cc. The version that was on the system was compiled with GCC and would not
link with the sun compiled code.
-James
"richard.berlin" <ric### [at] suncom> wrote in message
news:web.3d6fe509f869d21c7d693b520@news.povray.org...
> I haven't found a bug reporting mechanism, so I hope that the
> person who maintains the unix version checks this list now and then.
>
> On Solaris 9 with the compiler in /opt/SUNWspro (i.e NOT GCC)
> I get a mismatch between the prototypes in config.h and the
> actual functions in unix.cpp
>
> The functions in question are
>
> UNIX_Allow_File_Read()
> UNIX_Allow_File_Write()
>
> and the problem is that the version in config.h has a "const" that
> the actual function definition is missing. This means the names
> mangle differently, and results in a link error.
>
>
Post a reply to this message
|
|