On Sun, Jun 08, 2003 at 04:18:47PM +0200, Christian Marillat wrote: > Sven Luther <[EMAIL PROTECTED]> writes: > > [...] > > > Now, when first building the fixed libgtop2.0-1, libgtop-2.0.so.1.0.1 was > > linked not against the libgtop_common-2.0.so.1 and > > libgtop_sysdeps-2.0.so.1 which are also in the libgtop2 package, but > > against the system installed libgtop_common-2.0.so.0 and > > libgtop_sysdeps-2.0.so.0, which naturally were no more available when i > > installed the fixed package, and thus it was not really fixed. A second > > built resulted in the fixed packages i posted, but if i upload this to > > unstable, i will get loads of FTBFS, which would not be nice. I could > > build-conflict with libgtop2-dev (<< 2.0.2-1.1) or something such, but i > > don't think this is a good solution. > > > > I have quickly looked at the build system, but i am very unfamiliar with > > libtool and the various .am/.in stuff, so i would like it a lot if > > someone other took over from there and provided me with a build fix. > > > > So, i have tried to contact upstrem, which as Bastien Nocera pointed out > > is not the one actually listed in either copyright or AUTHORS, and hope > > they will provide a fix to this. > > Nothing related to upstream with this libtool feature. Search for glade > in that archive list for an answer.
Huh ? care to clarify this a bit ? I suppose you mean that it is libtool who is using the installed version of the libraries at build time, and that this is a bug in libtool ? A bug which did already happen for glade, and a solution/explanation/whatever can be found in 'that' mailing list ? which one, debian-gtk-gnome ? Friendly, Sven Luther
