Re: gvim weird linkage - NOT ONLY
The stack trace below shows exactly the symptoms of the binutils DT_TEXTREL bug, which has been fixed by the latest vendor import. Rebuilding world IS NOT ENOUGH to solve the problem. You will need to rebuild all the incorrect libraries which have been built with broken binutils before. Libpng is the only such library I found so far. Programs, linked with imlib are crashing when trying to dynamically load libppng, most likely. > #0 0x280530be in reloc_non_plt () /usr/libexec/ld-elf.so.1 > #1 0x28050b00 in find_symdef () from /usr/libexec/ld-elf.so.1 > #2 0x28051097 in dlopen () from /usr/libexec/ld-elf.so.1 > #3 0x28252bbb in sys_dl_open () from /usr/local/lib/libltdl.so.1 > #4 0x2825313e in tryall_dlopen () from /usr/local/lib/libltdl.so.1 > #5 0x282540c0 in lt_dlopen () from /usr/local/lib/libltdl.so.1 > #6 0x28254395 in lt_dlopenext () from /usr/local/lib/libltdl.so.1 > #7 0x28076558 in __imlib_ProduceLoader () from > /usr/X11R6/lib/libImlib2.so.1#8 0x28076bf7 in __imlib_LoadAllLoaders > () from /usr/X11R6/lib/libImlib2.so.1#9 0x28076b69 in > __imlib_RescanLoaders () from /usr/X11R6/lib/libImlib2.so.1#10 > 0x28076f28 in __imlib_LoadImage () from > /usr/X11R6/lib/libImlib2.so.1#11 0x28084d64 in imlib_load_image () > from /usr/X11R6/lib/libImlib2.so.1#12 0x804b167 in > imlib_context_set_color ()#13 0x80496e6 in imlib_context_set_color () > #14 0x804963d in imlib_context_set_color () To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage - NOT ONLY
On Sat, 9 Mar 2002, Vallo Kallaste wrote: -> On Sat, Mar 09, 2002 at 09:42:07PM +0100, Olivier Houchard <[EMAIL PROTECTED]> wrote: -> Tried without XIM support only, then without multibyte, fontset and -> XIM support, no joy. Exactly same linkage happens. Perhaps I should -> also note that using Motif for GUI will not change anything. I have a very similar problem with windowmaker, xv and perhaps few other X11 applications. I also have a window manager compiled from x11-wM/phluid port. They all dump core attempting to dlopen(): (example from phluid) #0 0x280530be in reloc_non_plt () /usr/libexec/ld-elf.so.1 #1 0x28050b00 in find_symdef () from /usr/libexec/ld-elf.so.1 #2 0x28051097 in dlopen () from /usr/libexec/ld-elf.so.1 #3 0x28252bbb in sys_dl_open () from /usr/local/lib/libltdl.so.1 #4 0x2825313e in tryall_dlopen () from /usr/local/lib/libltdl.so.1 #5 0x282540c0 in lt_dlopen () from /usr/local/lib/libltdl.so.1 #6 0x28254395 in lt_dlopenext () from /usr/local/lib/libltdl.so.1 #7 0x28076558 in __imlib_ProduceLoader () from /usr/X11R6/lib/libImlib2.so.1 #8 0x28076bf7 in __imlib_LoadAllLoaders () from /usr/X11R6/lib/libImlib2.so.1 #9 0x28076b69 in __imlib_RescanLoaders () from /usr/X11R6/lib/libImlib2.so.1 #10 0x28076f28 in __imlib_LoadImage () from /usr/X11R6/lib/libImlib2.so.1 #11 0x28084d64 in imlib_load_image () from /usr/X11R6/lib/libImlib2.so.1 #12 0x804b167 in imlib_context_set_color () #13 0x80496e6 in imlib_context_set_color () #14 0x804963d in imlib_context_set_color () This is current installed from scratch from one of the late february snaphots, with world updated every so-often (2-3 days max). New make buildworld with -g in progress now. I even recompiled XFree86-4 (4.1.0 port) and it didn't help. -- << Marcin Cieślak // [EMAIL PROTECTED] >> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 09:42:07PM +0100, Olivier Houchard <[EMAIL PROTECTED]> wrote: > > I did cvsup, world and new kernel, just in case.. but it really > > doesn't matter. Same problem. > You may try to compile vim with ./configure --disable-xim too. > It worked for me. Tried without XIM support only, then without multibyte, fontset and XIM support, no joy. Exactly same linkage happens. Perhaps I should also note that using Motif for GUI will not change anything. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 10:41:32PM +0200, Vallo Kallaste wrote: > On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick <[EMAIL PROTECTED]> wrote: > > > > Any hints? Seems like some environment configuration problem or > > > latent bug somewhere.. > > > > I just rebuild my current today and gvim has started working for me > > again now > > I did cvsup, world and new kernel, just in case.. but it really > doesn't matter. Same problem. You may try to compile vim with ./configure --disable-xim too. It worked for me. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 02:19:40PM +, Simon Dick <[EMAIL PROTECTED]> wrote: > > Any hints? Seems like some environment configuration problem or > > latent bug somewhere.. > > I just rebuild my current today and gvim has started working for me > again now I did cvsup, world and new kernel, just in case.. but it really doesn't matter. Same problem. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 09:55:50AM -0800, David O'Brien <[EMAIL PROTECTED]> wrote: > On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: > > Gvim will link against nonexistent libraries, some of them seem to > > be derived from libXThrStub library name and some Xlib function > > What revision of port/editors/vim/Makefile do you have? /usr/ports/editors/vim/Makefile: $FreeBSD: ports/editors/vim/Makefile,v 1.185 2002/03/04 21:13:20 obrien Exp $ -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: > Gvim will link against nonexistent libraries, some of them seem to > be derived from libXThrStub library name and some Xlib function What revision of port/editors/vim/Makefile do you have? To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:55:13PM +0200, Vallo Kallaste wrote: > On Sat, Mar 09, 2002 at 07:39:00AM -0600, "Jacques A. Vidrine" <[EMAIL PROTECTED]> >wrote: > > > Update your -CURRENT. I noticed this problem a month or two ago, > > but with a recent build of -CURRENT, gvim finally works again. > > Hm, thanks for confirming, but I'm running the very latest -current > as I wrote. Actually I've switched back to -current some weeks ago > after using -stable for a while because -current was very unstable > after beginnings of SMPng. To be clear I did fresh install of the > -current snapshot which I found in ftp.ee.freebsd.org, not 4.5-> > -current upgrade. I've built several worlds and kernels from that > onward. > Any hints? Seems like some environment configuration problem or > latent bug somewhere.. I just rebuild my current today and gvim has started working for me again now -- Simon Dick [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 07:39:00AM -0600, "Jacques A. Vidrine" <[EMAIL PROTECTED]> wrote: > Update your -CURRENT. I noticed this problem a month or two ago, > but with a recent build of -CURRENT, gvim finally works again. Hm, thanks for confirming, but I'm running the very latest -current as I wrote. Actually I've switched back to -current some weeks ago after using -stable for a while because -current was very unstable after beginnings of SMPng. To be clear I did fresh install of the -current snapshot which I found in ftp.ee.freebsd.org, not 4.5-> -current upgrade. I've built several worlds and kernels from that onward. Any hints? Seems like some environment configuration problem or latent bug somewhere.. -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: gvim weird linkage
On Sat, Mar 09, 2002 at 03:36:20PM +0200, Vallo Kallaste wrote: > Hi > > Gvim will link against nonexistent libraries, some of them seem to > be derived from libXThrStub library name and some Xlib function > names, very weird. I'm unable to build working gvim either from > ports or by hand, also doesn't matter is it newest version or older > 6.0 release. Update your -CURRENT. I noticed this problem a month or two ago, but with a recent build of -CURRENT, gvim finally works again. Cheers, -- Jacques A. Vidrine <[EMAIL PROTECTED]> http://www.nectar.cc/ NTT/Verio SME . FreeBSD UNIX .Heimdal Kerberos [EMAIL PROTECTED] . [EMAIL PROTECTED] . [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
gvim weird linkage
Hi Gvim will link against nonexistent libraries, some of them seem to be derived from libXThrStub library name and some Xlib function names, very weird. I'm unable to build working gvim either from ports or by hand, also doesn't matter is it newest version or older 6.0 release. First thought something is wrong with my hand-compiled XFree 4.2.0, but it isn't, XFree-4 port gave same results. I've -current as of yesterday, certainly past of the latest md5-crypt.c bug.. In the light of past events it seems to be something with linker or perhaps binutils. Non-X vim will work fine. myhakas:root# pwd /opt/portbuild/usr/ports/editors/vim/work/vim61a/src myhakas:root# ls -la vim -rwxr-xr-x 1 root wheel 1202570 Mar 9 15:01 vim myhakas:root# ldd vim vim: libXaw.so.7 => /usr/X11R6/lib/libXaw.so.7 (0x28158000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x281ab000) libncurses.so.5 => /usr/lib/libncurses.so.5 (0x281b8000) libc.so.5 => /usr/lib/libc.so.5 (0x281fa000) libXThrStub.XDeleteProperty => not found (0x0) libXThrStubXtVaGetValues => not found (0x0) libXThrStub.XDefaultScreen => not found (0x0) libXThrStub.XpmFreeAttributes => not found (0x0) libXmu.so.6 => /usr/X11R6/lib/libXmu.so.6 (0x282b) libXt.so.6 => /usr/X11R6/lib/libXt.so.6 (0x282c5000) libSM.so.6 => /usr/X11R6/lib/libSM.so.6 (0x2830e000) libICE.so.6 => /usr/X11R6/lib/libICE.so.6 (0x28317000) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x2832d000) libXpm.so.4 => /usr/X11R6/lib/libXpm.so.4 (0x283e5000) libXThrStub.so.6 => /usr/X11R6/lib/libXThrStub.so.6 (0x283f3000) myhakas:root# exit -- Vallo Kallaste [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
