I just finished compiling and installing POV-Ray 3.5c for Unix on a Solaris
8 box, and I get this error:

$ povray
ld.so.1: povray: fatal: libtiff.so: open failed: No such file or directory
Killed

I know I have libtiff.so in the /usr/lib directory. How can I tell POV-Ray
that?

MidnightLightning

Post a reply to this message

There's something odd with libtiff anyways, so you might want to link
libtiff.a statically into the povray binary (this is what I have to do
every time I compile POV-Ray for Solaris).
  That is, in the linking command replace "-ltiff" with
"/the/path/to/libtiff.a".

  By the way, if you write "echo $LD_LIBRARY_PATH" what does it say?

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

Warp wrote:
>  There's something odd with libtiff anyways, so you might want to link
>libtiff.a statically into the povray binary (this is what I have to do
>every time I compile POV-Ray for Solaris).
>  That is, in the linking command replace "-ltiff" with
>"/the/path/to/libtiff.a".
>
>  By the way, if you write "echo $LD_LIBRARY_PATH" what does it say?
>
>#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
>N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
>N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -
>

echo $LD_LIBRARY_PATH produces a blank line. I can add the -L switch to the
Makefile, but since the src directory has been 'make'd already, it won't
re-compile the packages with the new Makefile. Is there a flag to force the
make command to re-compile the packages?

Post a reply to this message

On Mon, 21 Apr 2003, Warp wrote:
>  There's something odd with libtiff anyways, so you might want to link
>libtiff.a statically into the povray binary (this is what I have to do
>every time I compile POV-Ray for Solaris).
>  That is, in the linking command replace "-ltiff" with
>"/the/path/to/libtiff.a".
>
>  By the way, if you write "echo $LD_LIBRARY_PATH" what does it say?
>
No need to link statically :

ldd src/povray_64bit
        libtiff.so =>    /opt/csw/lib/sparcv9/libtiff.so
        libjpeg.so.62 =>         /opt/csw/lib/sparcv9/libjpeg.so.62
        libpng.so.3 =>   /opt/csw/lib/sparcv9/libpng.so.3
        libz.so.1 =>     /usr/lib/sparcv9/libz.so.1
          .
          .
          .

ldd src/povray
        libtiff.so =>    /opt/csw/lib/libtiff.so
        libjpeg.so.62 =>         /opt/csw/lib/libjpeg.so.62
        libpng.so.3 =>   /opt/csw/lib/libpng.so.3
        libz.so.1 =>     /usr/lib/libz.so.1


Dennis

Post a reply to this message

MidnightLightning <nomail@nomail> wrote:
> echo $LD_LIBRARY_PATH produces a blank line.

  That's why ld can't find libtiff.so at runtime.

> I can add the -L switch to the
> Makefile, but since the src directory has been 'make'd already, it won't
> re-compile the packages with the new Makefile. Is there a flag to force the
> make command to re-compile the packages?

  You don't need to recompile, just to relink. Delete the povray binary
and run make.

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message

Warp wrote:
>  You don't need to recompile, just to relink. Delete the povray binary
>and run make.
>
>plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
>sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
>density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
><1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -
>

I deleted the file 'povray' in the src directory, and ran 'make' for that
directory again, which created a new 'povray' file, but that one had the
same linking errors. Are you sure that's the correct procedure?

Post a reply to this message

MidnightLightning <nomail@nomail> wrote:
> I deleted the file 'povray' in the src directory, and ran 'make' for that
> directory again, which created a new 'povray' file, but that one had the
> same linking errors. Are you sure that's the correct procedure?

  Did you replace "-ltiff" with "/path/to/libtiff.a" as I said?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

Warp wrote:
>
>  Did you replace "-ltiff" with "/path/to/libtiff.a" as I said?
>
>#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
>-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -
>

Yes, here's the result. Here's it without a -l or -L switch in front of it.
With the -l switch, it gets a similar error.

$ make
c++  -Wno-multichar -O3 -finline-functions -ffast-math -fomit-frame-pointer
-funroll-loops -fexpensive-optimizations -foptimize-sibling-calls
-Wno-multichar  -o povray  atmosph.o bbox.o bcyl.o benchmark.o bezier.o
blob.o  boxes.o bsphere.o camera.o chi2.o colour.o colutils.o cones.o csg.o
 discs.o express.o file_pov.o fncode.o fnintern.o fnpovfpu.o fnsyntax.o
fpmetric.o fractal.o function.o gif.o gifdecod.o hcmplx.o hfield.o
histogra.o iff.o image.o interior.o isosurf.o jpeg_pov.o lathe.o  lbuffer.o
lightgrp.o lighting.o matrices.o media.o mesh.o normal.o  objects.o
octree.o optin.o optout.o parse.o parsestr.o parstxtr.o  pattern.o pgm.o
photons.o pigment.o planes.o png_pov.o point.o poly.o  polygon.o polysolv.o
pov_mem.o povms.o povmscpp.o povmsend.o povmsrec.o  povray.o pov_util.o
ppm.o prism.o quadrics.o quatern.o rad_data.o  radiosit.o ray.o render.o
renderio.o sor.o spheres.o sphsweep.o  splines.o statspov.o super.o targa.o
texture.o tiff_pov.o tokenize.o  torus.o triangle.o truetype.o txttest.o
userdisp.o userio.o vbuffer.o  vlbuffer.o warps.o unix.o povxlib.o
-L/home/boydb/downloads/jpeg-6b -L/usr/lib -L/usr/local/lib -ljpeg
/usr/local/lib/libtiff.a -lpng -lz -lm  -lX11
$ povray
ld.so.1: povray: fatal: libtiff.so: open failed: No such file or directory
Killed

with a -L switch it does:

 povxlib.o  -L/home/boydb/downloads/jpeg-6b -L/usr/lib -L/usr/local/lib
-ljpeg -L/usr/local/lib/libtiff.a -lpng -lz -lm  -lX11
Undefined                       first referenced
 symbol                             in file
TIFFGetField                        tiff_pov.o
TIFFGetFieldDefaulted               tiff_pov.o
TIFFOpen                            tiff_pov.o
TIFFSetErrorHandler                 tiff_pov.o
TIFFClose                           tiff_pov.o
TIFFComputeStrip                    tiff_pov.o
TIFFReadRGBAImage                   tiff_pov.o
TIFFReadEncodedStrip                tiff_pov.o
TIFFGetVersion                      optout.o
TIFFScanlineSize                    tiff_pov.o
TIFFStripSize                       tiff_pov.o
TIFFSetWarningHandler               tiff_pov.o
ld: fatal: Symbol referencing errors. No output written to povray
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `povray'

each time I remove the povray file and the povray.o file before running
'make' again

Post a reply to this message

MidnightLightning <nomail@nomail> wrote:
> $ povray

  Are you sure you are running the binary you just compiled?

  In unix it's always a good idea to run "./povray" when you want to run
the one in the current directory.

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message

On Wed, 23 Apr 2003 23:04:34 -0400, MidnightLightning wrote:

> -L/usr/local/lib/libtiff.a

shouldn't that be a small l, i.e.

-l/usr/local/lib/libtiff.a

Dave

Post a reply to this message