From: Sven M. H. <pe...@gm...> - 2001-05-22 21:59:24
|
On Tue, May 22, 2001 at 09:19:53PM +0200, Marcelo E. Magallon wrote: > >> "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. Alright. Brian, is this OK with you? > > > 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) Right. Since we can't influence the SONAME directly, we don't have any other option than to check whether libtool did what we wanted and issue an error message otherwise. > > 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 ... I don't think GLU uses the STL. > > 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... Did you try it with a lower revision number? What does a "bus error" mean exactly, do you know? I don't. Regards, Sven -- "Would the All-Seeing Eye please look in my direction?" [ KeyID........: 0xC297FEAB ] [ Fingerprint..: FEA5 0F93 7320 3F39 66A5 AED3 073F 2D5F C297 FEAB ] |