OK. Trying to build libtiff here. Info from http://www.asteriskguru.com/tutorials/spandsp.html Libtiff from tar: ftp://ftp.remotesensing.org/pub/libtiff 3.8.2 put tiff-3.8.2.tar.gz in /root then tar -zxvf tiff-3.8.2.tar.gz followed by: /configure make clean make But the make had the following error: ./libtool: line 837: g++: command not found make[2]: *** [tif_stream.lo] Error 1 make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' make[1]: *** [all] Error 2 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [all-recursive] Error 1 and make install did not work: Making install in port make[1]: Entering directory `/root/tiff-3.8.2/port' make[2]: Entering directory `/root/tiff-3.8.2/port' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/tiff-3.8.2/port' make[1]: Leaving directory `/root/tiff-3.8.2/port' Making install in libtiff make[1]: Entering directory `/root/tiff-3.8.2/libtiff' source='tif_stream.cxx' object='tif_stream.lo' libtool=yes \ DEPDIR=.deps depmode=none /bin/sh ../config/depcomp \ /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c -o tif_stream.lo tif_stream.cxx libtool: compile: g++ -DHAVE_CONFIG_H -I. -I. -I. -I. -c tif_stream.cxx -o .libs/tif_stream.o ./libtool: line 837: g++: command not found make[1]: *** [tif_stream.lo] Error 1 make[1]: Leaving directory `/root/tiff-3.8.2/libtiff' make: *** [install-recursive] Error 1 So what is missing? And where do I start from. It looks like things are not 'broken' from how far it got. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20060601/45353c8b/attachment-0003.html>
> ./configure > make clean > makeNot going to get into how much of a bad idea this is, or how it should really be in an rpm.> But the make had the following error: > > ./libtool: line 837: g++: command not foundThis one line has your winner. You lack the proper build tools to complete your desired task. You're missing the gcc-c++, and probably several other things you'll need.> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff'This line would seem to imply that you're building software as root. This is generally a very bad idea. If the code's cleanup scripts are wrong, or if there's a typo... it's running as root and could very easily rm -rf your system, instead or rm -rf the buildroot or tmp files its using, not to mention other nefarious code tricks that make this a bad idea.> and make install did not work:that's because you had prior errors.> So what is missing? And where do I start from.You should really consider reading up on compiling software and/or building custom rpms.> It looks like things are not 'broken' from how far it got.They're not broken because they haven't gotten that far yet. You're missing the compiler required to make/break them. -- This message has been double ROT13 encoded for security. Anyone other than the intended recipient attempting to decode this message will be in violation of the DMCA
It would be nice if the world were flat... At 02:48 PM 6/1/2006, Jim Perrin wrote:>> ./configure >> make clean >> make > >Not going to get into how much of a bad idea this is, or how it should >really be in an rpm.But there is no rpm for libtiff v 3.8.2 for Centos. Every indication is that I need this. Well we will see what is supplied in the new Trixbox (Asterisk at home's new name).>> But the make had the following error: >> >> ./libtool: line 837: g++: command not found > >This one line has your winner. You lack the proper build tools to >complete your desired task. You're missing the gcc-c++, and probably >several other things you'll need.?? yum groupinstall gcc-c++>> make[2]: Leaving directory `/root/tiff-3.8.2/libtiff' > >This line would seem to imply that you're building software as root. >This is generally a very bad idea. If the code's cleanup scripts are >wrong, or if there's a typo... it's running as root and could very >easily rm -rf your system, instead or rm -rf the buildroot or tmp >files its using, not to mention other nefarious code tricks that make >this a bad idea.So I log in as user foo. I do all the makes as foo. But everything in /usr/var is owned by root... ??>> and make install did not work: > >that's because you had prior errors.Just making sure. Obvious answer, but I have been seeing some non-obvious stuff lately.>> So what is missing? And where do I start from. > >You should really consider reading up on compiling software and/or >building custom rpms.I have looked for some reasonable howtos but so far have come up short.>> It looks like things are not 'broken' from how far it got. > >They're not broken because they haven't gotten that far yet. You're >missing the compiler required to make/break them.Again, obvious from: 1104 -r--r--r-- 1 root root 1126338 May 9 07:38 libtiff.a 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so -> libtiff.so.3.6 0 lrwxrwxrwx 1 root root 14 May 24 11:07 libtiff.so.3 -> libtiff.so.3.6 308 -rwxr-xr-x 1 root root 311088 May 9 07:38 libtiff.so.3.6 thanks.>-- >This message has been double ROT13 encoded for security. Anyone other >than the intended recipient attempting to decode this message will be >in violation of the DMCAIllegitimi non Carborundum