Let me start off by saying that I am by no means a unix person. I am tasked to install log4cxx on a brand new machine but it looks like we need the apr, apr-utils, libtool, make, autoconf, automake, and gcc packages just to install log4cxx. Our machine came with no c compiler so I couldn't build gcc, so I downloaded the binary from sunfreeware.com. My machine specs are:
uname -a
SunOS texas 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Blade-1500
The binaries that I have been downloading say they are for:
Freeware List for SPARC and Solaris 10
Are these binaries the correct ones?
I have used the pkgadd application to install all of the above applications except log4cxx, which I need to build.
The first step to build is to run ./autogen.sh
When I run this I get:
./autogen.sh: aclocal: not found
./autogen.sh: autoheader: not found
/usr/local/bin/autoconf: /usr/local/bin/autom4te: not found
./autogen.sh: automake: not found
I added /usr/local/bin to my PATH and I've checked to make sure all of these files exist and they do.
Could the binaries be wrong or is there something Im doing wrong?
I pkgrm'ed all the packages that I installed, downloaded the solaris 9 versions, and pkgadd'ed those. And I'm still getting the same message.
./autogen.sh: aclocal: not found
./autogen.sh: autoheader: not found
/usr/local/bin/autoconf: /usr/local/bin/autom4te: not found
./autogen.sh: automake: not found
Not sure what you are reading - or maybe you are doing something besides what it seems you state you are attempting:
Steps to build log4c should be (most of the time this is the process to build not just for log4c - of course, if I'm wrong, someone will be sure to say something!):
As of version 0.2.0 log4cpp can be build using autoconf on platforms that support it. Simply do:
./configure
make
make check
make install
This will install log4cpp under /usr/local. To install in another localation specify --prefix=<location> when running configure.
Suggest you double check your PATH - try using the which command to see if it finds the correct executable and also change your shell to sh (in case you are using csh)
$ which gcc
Make sure the output is where you expect it to be (/usr/local/bin/gcc or where ever you think it suppose to be - then go to the directory and make sure it's there)
Do that for all the files it states it needs.
Double check your packages - pkginfo -p will show any packages that were only partially installed - make sure all these new packages are okay.
Check that your LD_LIBRARY_PATH has the correct paths also (env|grep LIB)