Need some help linking to libraries (using ./configure and stuff).

[dayalsoap]

Basically, I was able to build and install this required library, and using libtool, I was able to put the library here:

/net/hu19/jxd1581/lib/libnssi_env.la

Now, I have this other project, that contains Makefile.am, Makefile.in configure.ac, configure, etc etc.

I do
./configure --prefix=$HOME, where $HOME is /net/hu19/jxd1581

However, when I run make, I get this

make[3]: Entering directory `/net/hu19/jxd1581/mware/fms/trunk/cod'
/bin/sh ./libtool --tag=CC   --mode=link gcc  -g -O2  -L/net/hu19/jxd1581/lib -o libcod.la -rpath /net/hu19/jxd1581/lib cod.lo cod_node.lo cg.lo standard.lo -ldild   -lm  -lnssi_env -latl ./../fm/libfm.la
grep: /usr/local/lib/libnssi_env.la: No such file or directory
/bin/sed: can't read /usr/local/lib/libnssi_env.la: No such file or directory
libtool: link: `/usr/local/lib/libnssi_env.la' is not a valid libtool archive

Why is it looking for libnssi_env.la (-lnssi_env) in /usr/local/lib??

How do I change the appropriate ./configure, configure.ac etc files to look for the library in /net/hu19/jxd1581/lib

Do I change the path variable?

Thanks a lot!

[dayalsoap]

I tried appending LD_LIBRARY_PATH to include the directory, but no such luck so far...

[dayalsoap]

Even BEFORE make errors, ./configure prints this:

checking needed link args for nssi_env package... /net/hu19/jxd1581/lib

So, during the configure, it seems to know where it is. Why is make STILL looking for it in /usr/local/lib?????

[Salem]

Who wrote your .configure (or where did you download it from)?

It's just a text file, perhaps open it in the editor and look for /usr/local ?

[dayalsoap]

It's part of an in-house repository. I looked for /usr/local/lib and there are a LOT of entries. I guess I could append my directory to those.

There has to be an easier way, though...

[dayalsoap]

There has to be some flag? this configure script is all part of autotools...

[anduril462]

The normal format for an archive name is lib<library name>.a, and you specify it as a linker parameter with -l<library name>. So what's up with libnssi_env.la? Should it just be libnssi_env.a? That's what is suggested by your linker parameter -lnssi_env (notice the lack of a .l).

[dayalsoap]

The normal format for an archive name is lib<library name>.a, and you specify it as a linker parameter with -l<library name>. So what's up with libnssi_env.la? Should it just be libnssi_env.a? That's what is suggested by your linker parameter -lnssi_env (notice the lack of a .l).

That's something that libtool creates.

[dayalsoap]

Maybe I'm asking the wrong question?

[Salem]

> It's part of an in-house repository.
Or you're asking in the wrong place.

Seriously, if you've got something which is proprietary, hidden from us, and has generally been mucked about with by person(s) unknown, there isn't a lot we can say.

The first thing to answer is what changed between when it worked last, and the appearance of the error message(s).

Perhaps next, learn enough bash to be able to get the general idea of what is going on inside the configure script.
BASH with Debugger and Improved Debug Support and Error Handling may be helpful in running it in a controlled manner; perhaps some earlier command is producing bad output which is mis-interpreted later on.

[dayalsoap]

> It's part of an in-house repository.
Or you're asking in the wrong place.

Seriously, if you've got something which is proprietary, hidden from us, and has generally been mucked about with by person(s) unknown, there isn't a lot we can say.

The first thing to answer is what changed between when it worked last, and the appearance of the error message(s).

Perhaps next, learn enough bash to be able to get the general idea of what is going on inside the configure script.
BASH with Debugger and Improved Debug Support and Error Handling may be helpful in running it in a controlled manner; perhaps some earlier command is producing bad output which is mis-interpreted later on.

I mean, it's clear from your first response, that you're not familiar with standard tools like autoconfig and libtool. These are standard tools, that's why I'm asking the community.

[rags_to_riches]

Why don't you ask...I don't know...your co-workers???

[Salem]

Until today, I'd never heard of a library being called .la, so I just rather assumed that someone had done some serious mucking about with it.

Also, have you figured out yet the delta between when it last worked and the current state?

[tabstop]

I mean, it's clear from your first response, that you're not familiar with standard tools like autoconfig and libtool. These are standard tools, that's why I'm asking the community.

If there was a problem with autotools, that would be one thing. (It still wouldn't belong on this forum, but on the GNU bug reporting list.) But your in-house configure script is just that, your in-house configure script. That's where the error is, so that's where you're going to have to look for it. And I'm pretty sure no one else here works at the same place you do, so no one else has a copy of your in-house configure script.