On Wed, 28 May 2008 08:02:46 -0700 Michael Schuster <Michael.Schuster at Sun.COM> wrote:
> Mark Wright wrote: > > Hello Michael, > > > > The lib*.a files are created on my box, but I thought that > > was because I am playing with libtool 2.2.4, which is not > > used in Dude (except for ncurses, so far). > > > > You could check the outputs of: > > > > which libtool > > libtool --version > > > > Which should find libtool 1.5.something in /opt/kdebld/bin. > > 1.5.24 Hello Michael, The hacked libtool 1.5.24 should be OK (mostly, if there are libtool problems it might be an idea to try 2.2.4). > > Another possibility is: maybe they might be created by > > some change in automake 1.10.1. > > would that be from upstream KDE? I don't know. Hopefully it is much the same as automake 1.10 with some bug fixes. > > Its trivial change to the .pspc files to fix the errors below, > > just search for the lib*.so*, copy the line, and change the > > duplicate lib*.so* line to lib*.a, like: > > > > Index: Dude/SPECS/gettext.pspc > > =================================================================== > > --- Dude/SPECS/gettext.pspc (revision 2029) > > +++ Dude/SPECS/gettext.pspc (working copy) > > [...] > > > On my box I have made the same mindless change to > > the following .pspc files so far: > > Can you check this into Dude, so we don't have to all repeat this > step? > > TIA > Michael If we don't need the lib*.a files, then Ade's (I think, from memory) alternative suggestion of removing then in the install.sh scripts with rm -f should work whether they are present or not. So that would seem better, assuming we don't want the lib*.a files anyway? I don't have the commit bit on Dude. It would take a while for me to rebuild everything and test it again. At the moment its probably better if I first see if I can compile hal. Thanks, Mark --
