Thanks Bill there was no way this was going to compile on 9.2,I'd got to the point of so many conflicts between libs and prog dependancies that urpmi just would'nt play. There really needs to be added to th mcc gui on s/w management a do as your told function, force it. On an earlier ver circa 8.1 there was, now its gone The app dependant on this was built on a machine running 9.1 with a full ish set of libs. So in the end I reloaded 9.1 on the machine I wanted that app on then immediately loaded 9.2 as an upgrade , using the ice maker window to download all the bug fixes before running gnome. Configure still complaining of missing libs, which were the same on both machines So in the end I copied over the complete directory from this machine were it was built to the other machine , luckily I had'nt done a make clean, and did a make install. It looks like I got away with it. I'm not happy with this solution ,its mucky and dos'nt solve why a prog would compile on a machine running 9.1 and be a pig on 9.2 BTW 9.2 dos'nt down load the upgrades on install
Richard On Fri, 2003-10-24 at 18:16, Bill Mullen wrote: > On Thu, 23 Oct 2003, Richard Bown wrote: > > > back again,sorted the libxml , but gnomeprint is giving me probs and I'm > > now hitting long lists on file conflicts These are the versions of > > gnomeprint installed > > > > libgnomeprint-2.3.1-4mdk > > libgnomeprintui2-2_0-2.3.1-2mdk > > libgnomeprint15-0.37-4mdk > > libgnomeprint2-2_0-devel-2.3.1-4mdk > > libgnomeprint2-2_0-2.3.1-4mdk > > > > and here the error message at the point configure fails. > > > > checking if iconv() handles UTF-8... yes > > checking preferred charset formats for system iconv... found > > checking for %l and %k support in strftime... yes > > checking for nl_langinfo (CODESET)... yes > > checking for GnomePrint libraries >= 0.25... > > > > I would have thought the above list was >= 0.25 > > You probably need: > > libgnomeprint15-devel-0.37-4mdk > > And possibly also: > > libgnomeprintui2-2_0-devel-2.3.1-2mdk > > Both of which should be on the CDs. > > The thing to always bear in mind is that whenever a compile is looking for > something and not finding it, it is almost always a "*-devel" package that > it is seeking. Having a certain library package alone is *not* enough to > be able to compile apps that will use that library - you will always need > to have the "*-devel" RPM for that library installed as well. As far as > gcc is concerned, it doesn't think that the library is installed, because > it cannot locate the -devel files for it. :( > > HTH! -- Richard Bown <[EMAIL PROTECTED]>
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
