On Thu, Mar 18, 2010 at 4:58 PM, Dan Nicholson <span dir="ltr"><<a href="mailto:dbn.lists@gmail.com">dbn.lists@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div><div></div><div class="h5">On Thu, Mar 18, 2010 at 12:41 PM, Joel Feiner <<a href="mailto:jafeiner@gmail.com">jafeiner@gmail.com</a>> wrote:<br> > On Thu, Mar 18, 2010 at 3:32 PM, Dan Nicholson <<a href="mailto:dbn.lists@gmail.com">dbn.lists@gmail.com</a>> wrote:<br> >><br> >> On Thu, Mar 18, 2010 at 10:54 AM, Joel Feiner <<a href="mailto:jafeiner@gmail.com">jafeiner@gmail.com</a>> wrote:<br> >> > The error that comes up is this:<br> >> > libtool: link: gcc -DHAVE_DMX_CONFIG_H -DHAVE_DIX_CONFIG_H -Wall<br> >> > -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes<br> >> > -Wmissing-declarations -Wnested-externs -fno-strict-aliasing<br> >> > -Wbad-function-cast -Wformat=2 -Wold-style-definition<br> >> > -Wdeclaration-after-statement -D_BSD_SOURCE -DHAS_FCHOWN<br> >> > -DHAS_STICKY_DIR_BIT -I/home/XXXX/xbuild/out/include/pixman-1<br> >> > -I/usr/include/freetype2 -I../../include -I../../include -I../../Xext<br> >> > -I../../composite -I../../damageext -I../../xfixes -I../../Xi -I../../mi<br> >> > -I../../miext/shadow -I../../miext/damage -I../../render -I../../randr<br> >> > -I../../fb -fvisibility=hidden -I../../hw/xfree86/dixmods/extmod<br> >> > -I/home/XXXX/xbuild/out/include/libdrm -I/usr/include/freetype2 -O2<br> >> > -mtune=native -march=native -pipe -fomit-frame-pointer -rdynamic -o Xdmx<br> >> > dmx.o dmxcb.o dmxcmap.o dmxcursor.o dmxdpms.o dmxextension.o dmxfont.o<br> >> > dmxgc.o dmxgcops.o dmxinit.o dmxinput.o dmxlog.o dmxpict.o dmxpixmap.o<br> >> > dmxprop.o dmxscrinit.o dmxshadow.o dmxstat.o dmxsync.o dmxvisual.o<br> >> > dmxwindow.o miinitext.o fbcmap_mi.o panoramiX.o dmx_glxvisuals.o<br> >> > -L/home/XXXX/xbuild/out/lib64 ../../fb/.libs/libfb.a<br> >> > ../../mi/.libs/libmi.a<br> >> > ../../render/.libs/librender.a ../../Xi/.libs/libXi.a<br> >> > ../../xkb/.libs/libxkb.a ../../xkb/.libs/libxkbstubs.a<br> >> > ../../miext/shadow/.libs/libshadow.a<br> >> > ../../miext/damage/.libs/libdamage.a<br> >> > ../../Xext/.libs/libXext.a ../../dix/.libs/libmain.a<br> >> > ../../dix/.libs/libdix.a ../../config/.libs/libconfig.a<br> >> > /usr/lib64/libhal.so<br> >> > /usr/lib64/libdbus-1.so ../../os/.libs/libos.a /usr/lib64/libgcrypt.so<br> >> > -L/usr/lib64 /usr/lib64/libgpg-error.so ../../xfixes/.libs/libxfixes.a<br> >> > glxProxy/libglxproxy.a input/libdmxinput.a config/libdmxconfig.a<br> >> > /home/XXXX/xbuild/out/lib64/libXmuu.so /usr/lib64/libXrender.so<br> >> > /usr/lib64/libX11.so /usr/lib64/libxcb.so /usr/lib64/libXau.so<br> >> > /home/XXXX/xbuild/out/lib64/libXfixes.so<br> >> > /home/XXXX/xbuild/out/lib64/libXi.so<br> >> > /home/XXXX/xbuild/out/lib64/libXext.so<br> >> > /home/XXXX/xbuild/out/lib64/libX11.so<br> >> > /home/XXXX/xbuild/out/lib64/libxcb.so<br> >> > /usr/lib64/libXdmcp.so -ldl /home/XXXX/xbuild/out/lib64/libXfont.so<br> >> > /usr/lib64/libfreetype.so /home/XXXX/xbuild/out/lib64/libfontenc.so -lz<br> >> > /home/XXXX/xbuild/out/lib64/libXau.so<br> >> > /home/XXXX/xbuild/out/lib64/libpixman-1.so<br> >> > /home/XXXX/xbuild/out/lib64/libXdmcp.so -lm -lrt -Wl,-rpath<br> >> > -Wl,/home/XXXX/xbuild/out/lib64 -Wl,-rpath<br> >> > -Wl,/home/XXXX/xbuild/out/lib64<br> >> ><br> >> > /home/XXXX/xbuild/out/lib64/libXi.so: undefined reference to<br> >> > `XESetWireToEventCookie'<br> >> ><br> >> > /home/XXXX/xbuild/out/lib64/libXi.so: undefined reference to<br> >> > `XESetCopyEventCookie'<br> >> > What appears to be happening, I think, is that it is getting libraries<br> >> > like<br> >> > libXrender and so on from /usr/lib64 instead of my build directory. I'm<br> >> > not<br> >> > sure why libtool is doing this. I have my PKG_CONFIG_PATH set to my<br> >> > local<br> >> > build package config path (/home/XXXX/xbuild/out/lib64/pkgconfig) and<br> >> > LD_LIBRARY_PATH is also set to that (modulo the pkgconfig part). I had<br> >> > also<br> >> > built the whole get up without using LD_LIBRARY_PATH. Same results.<br> >> > The<br> >> > only two modules that have this problem are pixman and xserver. Pixman<br> >> > I<br> >> > worked around by passing --disable-gtk to ./configure, since that was<br> >> > the<br> >> > part of the build that was failing. For xserver, it appears to be dmx<br> >> > that's failing.<br> >><br> >> If I had to guess, the /usr/lib64 is getting hardcoded into one of the<br> >> .la libtool archives installed in /home. Can you do "grep /usr/lib64<br> >> /home/XXXX/xbuild/out/lib64/*.la"? Maybe there's a problem with module<br> >> ordering in xorg.modules. Not sure if that's what's causing the<br> >> reference errors, though.<br> >><br> >> --<br> >> Dan<br> ><br> > I actually did grep for /usr/lib64 in my ~/xbuild (where the source and<br> > output trees live) and removed all references in the libtool archives (and<br> > even in libtool itself!). It didn't make a difference.<br> <br> </div></div>Next time can you record what those references were? That would help<br> solve this problem.<br></blockquote><div><br></div><div>They are now attached. I stripped out some obvious irrelevant lines (like /usr/lib64/dbus*). It's down to 254 lines, which hopefully shouldn't be too much to handle.</div> <div><br></div><div>I was not where I could go back to my Linux installation when I sent the 2nd email.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im"><br> > Somehow libtool<br> > found those libraries again. Note that it *has* found some of the libraries<br> > in the right place and that's the most confusing part. I'm not on Linux<br> > right now, so I can't try diddling with xorg.modules, but I'll try that<br> > again later this evening or tomorrow.<br> <br> </div>Well, you would need to clean up in the xserver tree too since now all<br> the .la files in the tree contain the references to the unwanted<br> libraries.<br></blockquote><div><br></div><div>I'll try a new build in a few minutes and see if deleting the entries in *.la files in the source tree as well as the build tree makes any difference.</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im"><br> > Does X.org require a specific version of libtool? Perhaps the one I have is<br> > incorrect or has some bug that interacts badly with X.org builds? Again, I<br> > can't check the version right now.<br> <br> </div>I don't think it's libtool that's causing the problem. It's doing what<br> it's always done (for better or worse). I suspect the problem is that<br> there is a module being built out of order that's picking up your<br> host's libraries because the new ones don't exist yet.<br> <br> Needs more info, though.<br> <br> --<br> <font color="#888888">Dan<br> </font></blockquote></div><br>