On 8/31/05, Philip Dillon-Thiselton <[EMAIL PROTECTED]> wrote: > Aaron Griffin wrote: > > >On 8/31/05, Matthias-Christian Ott <[EMAIL PROTECTED]> wrote: > > > > > >>Hi, > >>I read the issue about libtool on the website, but I asking myself howto > >>get my packages built during the switch. Have a look tomboy for example: > >> > >>/bin/sed: can't read /opt/gnome/lib/libgnomeprint-2-2.la: No such file or > >>directory > >>libtool: link: `/opt/gnome/lib/libgnomeprint-2-2.la' is not a valid libtool > >>archive > >> > >>This does this damn libtool want this files in this case. What do I have to > >>do to fix it? I don't want to care about this GNU stuff in the future, so I > >>think a common solution would be the best. > >> > >>Matthias-Christian Ott > >> > >> > > > >tomboy is in the [community] repo. It's slightly out of date, but > >will be updated later tonight (I hope) > > > > > But how will you build it? ;p > > I have a question too - how does the libtool slay operation affect > [community] and AUR pkgs? Surely we should be taking certain action. > Will pacman be updated to remove libtool files later or will all > PKGBUILDs need find -name "*.la" ...
I'm not using testing, and therefore have no effects of the libtool-slay when building. This will not affect binaries at all. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
