Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Ok, I just downloaded the source to look at it. It follows the same pattern that 99% of from-souce packages follow.
1. Untar the file
2. cd to the created dir (in this case splint-3.1.1)
3. Type: ./configure
4. Type: make
5. Type: make install
Obviously, don't proceed to the next step if there was an error reported in any of the phases. If an error was encountered, post it. Once you make it to the "make install" phase and it completes successfully, then you'll be able to use it like any other command (e.g. "splint source_code.c").
I didn't see anything in the documentation that referred to environment variables of any sort or dependencies. So, my suggestion would be to remove the directory you have now, repeat the process of untar'ing the file, and execute the commands above. Like I said, if you run into any problems, stop, and post them here. We'll get you going in no time.
As I was typing, I was compiling it in the background. During compilation, it runs a test suite to verify the compile. The header printed at the beginning of the tests mentioned that LARCH_PATH is not set. It then provided a listing of what the default value for it would be. This default value is simply a collection of directories that it will search in order. This is not an error per se, but if after running "make install" you keep getting the message, then you might consider setting the variable to get rid of the message. It's a simple matter to fix. And, btw, standard.lcd is a file created when you compile the package (I found it in splint-3.1.1/lib). More than likely, when you run make install, it (an other libraries) will be copied to the proper place. That's why I suggest waiting until after running make install to see if the LARCH_PATH message disappears.
I took your advice and tried it that way ... the configure worked, but when I did make, I got this error:
WARNING: `aclocal-1.6' is needed, and you do not seem to have it handy on your
system. You might have modified some files without having the
proper tools for further handling them. Check the `README' file,
it often tells you about the needed prerequirements for installing
this package. You may also peek at any GNU archive site, in case
some other package would contain this missing `aclocal-1.6' program.
I googled for this aclocal program or whatever, but I cant find anything about it ..
edit: also .. the readme doesnt mention anything about it
aclocal is a part of the GNU automake package. So what you'll need to do is download and install automake. Now, depending on what distribution you have, you might have an easier way. If you have a package manager installed (like Red Hat does), you can check to see if you can automate the install. It would probably be filed under "development" packages. If you can't find it, you can always download and install using the link the splint webpage mentioned.
You can get automake-1.8.5 from that link if you choose to download-and-install. There's no reason to install an older older copy if there's a newer one available
Last edited by Dark_Helmet; 06-11-2004 at 08:50 PM.
hmmm ... I just downloaded the 1.8.5 ... logged onto root ... ran ./configure, make, make install and I didnt get any errors during any of that process (for automake) ... then I went to install splint again and it still says I am missing aclocal 1.6
I am going to reboot now ... maybe they need to be restarted?? .. I have no clue.
I would kill the source tree for splint again (it's paranoia on my part, but whenever I get compile errors, I like to start from a clean slate), and run through the steps again. Also, double-check to make sure aclocal is intalled. If you have "which" installed on your system, just type: which aclocal
On my system, the output of which is:
As long as you get some output, then you're probably ok (it'll probably be in one of these: /bin, /usr/bin, or /usr/local/bin).
There's no need to reboot. aclocal is a program like any other; not a system daemon or anything.
Last edited by Dark_Helmet; 06-11-2004 at 09:28 PM.
Hmmmm... that's really very odd. If which can see it, then it's in your path. If it's in your path, then the make instructions should be able to see it.
I checked the aclocal on my system by typing: aclocal --version
aclocal (GNU automake) 1.6.3
..(plus some other irrelevant stuff)...
So, I have a 1.6.X version. It would be extremely bad form if splint requires exactly a 1.6.X version. Stranger (and stupider) things have happened though. Before you install the 1.6 version, go back to your source tree for 1.8.5 and issue this command: make uninstall
That ought to clean things up some.
The original message was just a warning. I don't know if it could safely be ignored, but seeing as how the splint site specifically mentions it, I would guess it shouldn't be. I'll keep my fingers crossed... just in case.