
Hi!
KC> It worked fine in that it created the programs and such in the KC> work directory I was working in. All the subdirectories were made, KC> the compiles worked, and the install tests were done. After KC> testing the programs myself to make sure they worked, I tried to KC> move only the relavent files into the bin directory where everyone KC> goes to. The smilint script tries to call the smilint program KC> from the wrong directory.
KC> I am missing something on how to get it to point the correct KC> directory. I did move the .libs directory also under the bin, but KC> that did not help.
Yes. Don't do that. It's libtool magic only relevant during development and compilation/linking.
libsmi uses GNU automake/autoconf and libtool. The general concept is to configure and compile the sources on the target platform. During the configure run a number of checks are done and you cannot expect the resulting code works on another platform where the result of these checks would be different.
If you are really just talking about different target directories on the same platform, then why don't you follow the usual configure and install procedure and let the prefix be /usr/local (or whereever 'everyone goes' at your site) instead of your work directory?
-frank -- !! This message is brought to you via the `libsmi' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to libsmi-request@ibr.cs.tu-bs.de. !! See http://www.ibr.cs.tu-bs.de/projects/libsmi/ for more information.