LibTiff Mailing List
TIFF and LibTiff Mailing List Archive
February 2011
Previous Thread
Next Thread
Previous by Thread
Next by Thread
Previous by Date
Next by Date
Contact
The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems
Thread
2011.02.14 16:51 "Re: How to set executable search path", by Daniel Mccoy
Setting your path:
http://kb.iu.edu/data/acar.html
From "Karri, Rasmi Teja" <RasmiTeja.Karri@xerox.com>, Mon, Feb 14, 2011 at 06:20:38AM -0500:
>
> Hi Bob,
>
> Thank you very much for letting me know the solution.
> I think this should work for me.
>
> But could you please let me know how to include /usr/ccs/bin into search
> path(PATH).
> I couldn't know how to set path in libtiff files.
> Is it the default path that will be set in .profile at root.
>
> But my congif.log(tiff folder) is not showing any one the paths that I
> included in default path variable at root.
>
> Please let me if I can include that path while bulding ./configure or
> anywhere else.
>
> Also Please let me know "is make uninstall at tiff folder will uninstall
> my old make".
>
> Thanks & Regards,
> Rasmi
>
>
> ------------------------------------------------------------------------
> ------------------------------------------------------------------------
> ----
> -----Original Message-----
> From: Bob Friesenhahn [mailto:bfriesen@simple.dallas.tx.us]
> Sent: Saturday, February 12, 2011 8:12 AM
> To: Karri, Rasmi Teja
> Cc: tiff@lists.maptools.org; Movva, Nageswararao
> Subject: RE: [Tiff] Error while make with libtiff
>
> On Fri, 11 Feb 2011, Karri, Rasmi Teja wrote:
> >
> > Could you please explain me in detail.
> >
> > And also what should we need to do in order to overcome it.
>
> It seems that my theory was wrong. This is what a good build in the
> port directory should end up with when using Solaris:
>
> libtool: link: ar cru .libs/libport.a dummy.o
> libtool: link: ranlib .libs/libport.a
> libtool: link: ( cd ".libs" && rm -f "libport.la" && ln -s
> "../libport.la" "libport.la" )
>
> Please make sure that /usr/ccs/bin is in your executable search path
> (PATH). That is the directory where the missing executable ('ar')
> should be coming from.
>
> If in doubt, doing 'which ar' should result like this:
>
> % which ar
> /usr/ccs/bin/ar
>
> Bob
> --
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us,
> http://www.simplesystems.org/users/bfriesen/
> GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
> _______________________________________________
> Tiff mailing list: Tiff@lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/tiff
> http://www.remotesensing.org/libtiff/