Re: [Mesa3d-dev] libtool (was CVS and SSE)

[Marcelo E. M. <mar...@bi...>]

>> "Sven M. Hallberg" <pe...@gm...> writes:

 > OK. So we let libtool do its work and (constructively) interfere with
 > it only where the necessity pops up, right?

 Yes, I guess that's the safest solution.
 
 > >  Like I said, what's important is the SONAME contained in the library,
 > >  what this file is called is not important.  Like this:
 > 
 > Really?? I thought it was like this:
 >  SONAME of library X = Y.
 >  compile executable Z with -lX
 >   -> linker puts SONAME(X)=Y to NEEDED(Z)
 >  execute Z
 >   -> linker looks up library of _name_ Y.
 >      If lib Y doesn't exist, linker fails.
 > 
 > Is it different?

 No, it's like that.  I meant that you have to check that the SONAME is
 set right and that there's a link SONAME(lib) ->
 whatever_libtool_called_it (e.g. libGL.so.1 -> libGL.1.2.350) and
 another one PUBLIC_NAME(lib) -> whatever_libtool_called_it (e.g.,
 libGL.so -> libGL.1.2.350)
 
 > libGL already gets these dependencies from the various convenience libs.
 > Can anyone see whether there are any missing? Since I built the si-glu
 > Makefile.am's I'll just add -lGL there, right?

 Funny that it doesn't list libstdc++, but appart from libGL, no, it
 doesn't need anything else ...

 > Ugh. Do you have any indication why that fails? Maybe it doesn't like
 > the high REVISION number?

 Libtool tries to pass something like 'sgi350.0:sgi349.0:...:sgi2.0:sgi1.0'
 to the linker, and the linker doesn't seem to like that and terminates
 with a bus error...

-- 
Marcelo