Hello Luc, I've built all of FOSS with libtool 2.2.4 now. It was not really that difficult.
It seems sort of easier using libtool 2.2.4 for FOSS KDE. While as with most other software at the moment, like JDS gnome 2.22.2 and SFE, its the opposite, libtool 2.2.4 tends to break things, for no gain if you are just trying to build stuff. JDS gnome 2.22.2 in particular likes doing stuff like: libtoolize --install autoreconf --install --force or something brutal like that with autotools. Which tends to break at the moment with libtool 2.2.4. If JDS could be convinced to compile C++ stuff with stdcxx and our compiler options, then it would probably be easier for JDS to use libtool 2.2.4 as well. But that would require fixing stuff. So what I mean is: its no point using libtool 2.2.4 for compiling other stuff not related to KDE if its just going to slow us down. To avoid that, I've taken advantage of how KBE and CBE are split at the moment, but not for much longer maybe. So I've using libtool 1.5.26 for compiling other stuff like JDS, and libtool 2.2.4 for compiling FOSS on KDE. Anyway, I can revert libtool 2.2.4 back to the hacked libtool 1.5.X and try compiling FOSS again to make sure I have not broken anything with the libtool 2.2.4 diffs. They sort of look like they would not break libtool 1.5.X, I can try it to make sure. Thanks, Mark On Fri, 6 Jun 2008 14:26:13 +0200 "Lukas Oboril" <oboril.lukas at gmail.com> wrote: > Hi, > > I would to know your opinion about %subject. Put libtool 2.2.4 to KBE > is easy, but impact across dude is not small. > > major things : > - libtool 2.2.4 needs a smarter shell then Bourne Shell, so we need > change in many places /bin/sh to /bin/bash > - migrate our modifications from SPECS/Tools/libtool (the old one > 1.5.x) to new libtool2 > > Ideas? Opinions ? > > > > --
