Where do the linker look for shared libraries?

[Andreas Davour]

On Wed, 2 Mar 2005, Dan Nelson wrote:

>>>> and the errors I get looks like this:
>>>>
>>>> /usr/local/lib//liballeg.so: undefined reference to `_poly_zbuf_atex_trans8'
>>>> /usr/local/lib//liballeg.so: undefined reference to `_poly_scanline_atex_mask_lit32'
>>>
>>> This is the linker saying "there are symbols in liballeg.so that I
>>> cannot find anywhere".  Maybe you need to specify another library
>>> along with liballeg?  Are you using the allegro port?
>>
>> I have grep'ed for those symbols and they come from liballeg.so, no
>> place else. That's one of the very confusing things with those errors.
>
> A web search on "undefined reference _poly_zbuf_atex_trans8" comes up
> with a couple hits, including a post that says you need to use the
> allegro-config command to determine the correct flags and libraries to
> link allegro.  What does "allegro-config --libs" print?  The demo
> programs built by the allegro port must work, so you could always build
> the port again and determine what flags it used.

Allegro have indeed changed since I looked at it last. I think it's time 
to check the pkg-plist.

I didn't even think about Google!

That did indeed fix the problems. I wasn't far off, but it had to link 
with a file with the unfriendly name "unsharable".

>> I'm using the allegro port. BTW, there is a linux-allegro port as well.
>> Why is this needed if Allegro is a platform independant API?
>
> For linux programs that might need the library (same API, different
> ABI).  I assume there's at least one in the ports tree somewhere.

OK. Sounds strange, but I guess it makes sense.

I still wonder if there's a way to have ld not go looking for ar 
archives by deafault...

/Andreas

-- 
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?