From: tma <ay...@gm...> - 2001-03-25 17:00:01
|
On Sun, 25 Mar 2001 23:33:57 +1000 Gordon Heydon <gjh...@bi...> wrote: > * tma (ay...@gm...) wrote: > > > Hello, > > > > > > I had this problem. It turned out to be that my build environment was > > > stuff by a couple of old capatiblity libs, that were getting linked in > > > and causing the build to fail. use ldd to determine this, and go from > > > there. > > > > > > > I see what you mean but I don't know which binary to check for my case as. > > BTW, ecore's autoconf tells me the same, so as of now only that of evas > > works. > > Yes it does work, but if you delete the config.cache it wont work > anymore, You can check the XShm lib and that will tell you. another > thing to try is to run your configure with the -x option eg > > sh -c ./configure > I can't find an option to call "./configure -x", any clue? BTW, it still works fin with evas, damn that's too irritating. Is X now X11R6.5.1 or 6.4.x my CVS-version tells it is 6.5.1, maybe this is too new? PS: some libs in /usr/X11R6/lib like Xrender or Xfont were only built in .a form now and the .so.* are from Nov 25, that seems a bit odd, doesn't it. The way I build X is exact the way how it's describes in the INSTALL-X.org file plus my own host.def with pentium-opts and MgaHalLib-stuff. > This will show the output and help decipher it. > > > I'm sure that those libs are all there and the ld.so-cache is alright too. > > Could it be that my self-built X from CVS is incompatible because it's too > > new, I don't hope so. Actually it's the latest and finally my G400 doesn't > > crash in evas-hardware now as it did for two months or so. They finally > > updated the DRI-stuff so that works again with evas, it was broken for some > > months. > > It is most likely that you have an old library hanging around. > I rebuilt X and before installing it deleted it's directory. |