From: Giuseppe Pagnoni on 30 Apr 2010 13:39 Dear xmonad maintainers, I just noticed that with the latest port tree upgrade (as of today), even when force-rebuilding all the ports dependent on libgmp (after its recent update detailed in /usr/ports/UPDATING), xmonad crashes on startup with the following error message: /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required by xmonad -x86_64-freebsd which seems to indicate that the xmonad dependency on libgmp was not updated in the port's files to follow the recent libgmp bump. I was able to make it work anyway with: ln -s /usr/local/lib/libgmp.so.10 /usr/local/lib/libgmp.so.8 but I wanted to signal the issue. very best, giuseppe PS: I am running FreeBSD 8.0-RELEASE-p2 / amd64 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: freebsd-ports on 30 Apr 2010 14:29 On 2010-04-30 19:39:44, Giuseppe Pagnoni wrote: > xmonad crashes on startup with the following error message: > > /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required by > xmonad -x86_64-freebsd This might have something to do with the way that xmonad recompiles itself and saves a copy of the binary in your $HOME. Have a look in ~/.xmonad, I think... M _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Gabor PALI on 30 Apr 2010 16:13 On 04/30/10 19:39, Giuseppe Pagnoni wrote: > xmonad crashes on startup with the following error message: > > /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required > by xmonad -x86_64-freebsd [..] > the xmonad dependency on libgmp was not updated in the port's files > to follow the recent libgmp bump. It was updated, just check it out at the right place [1]. On 04/30/10 20:29, freebsd-ports(a)coreland.ath.cx wrote: > This might have something to do with the way that xmonad recompiles > itself and saves a copy of the binary in your $HOME. Have a look in > ~/.xmonad, I think... Yes, that makes sense I think. What happens if you simply remove the xmonad binary in ~/.xmonad? Cheers, :g [1] http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/xmonad/Makefile.diff?r1=1.14;r2=1.15 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Giuseppe Pagnoni on 3 May 2010 05:01 Yep, that was exactly the problem. Removing the executable in ~/.xmonad makes xmonad start up correctly now. Much thanks for helping out best, giuseppe 2010/4/30 Gabor PALI <pgj(a)freebsd.org>: > On 04/30/10 19:39, Giuseppe Pagnoni wrote: >> xmonad crashes on startup with the following error message: >> >> /libexec/ld-elf.so.1: Shared object libgmp.so.8 not found, required >> by xmonad -x86_64-freebsd > [..] >> the xmonad dependency on libgmp was not updated in the port's files >> to follow the recent libgmp bump. > > It was updated, just check it out at the right place [1]. > > > On 04/30/10 20:29, freebsd-ports(a)coreland.ath.cx wrote: >> This might have something to do with the way that xmonad recompiles >> itself and saves a copy of the binary in your $HOME. Have a look in >> ~/.xmonad, I think... > > Yes, that makes sense I think. What happens if you simply remove the xmonad > binary in ~/.xmonad? > > > Cheers, > :g > > > [1] > http://www.freebsd.org/cgi/cvsweb.cgi/ports/x11-wm/xmonad/Makefile.diff?r1=1.14;r2=1.15 > > -- Giuseppe Pagnoni Dip. Scienze Biomediche Sezione Fisiologia Univ. di Modena e Reggio Emilia Via Campi 287 I-41125 Modena, Italy Tel: +39-059-205-5742 Fax: +39-059-205-5336 _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Gabor PALI on 3 May 2010 05:48 On Mon, May 3, 2010 at 11:01 AM, Giuseppe Pagnoni <gpagnoni(a)gmail.com> wrote: > Yep, that was exactly the problem. Removing the executable in > ~/.xmonad makes xmonad start up correctly now. Meanwhile I found that the same effect can be achieved by issuing `xmonad --recompile`. I think it is always needed on each shared library bump. Cheers, :g _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
|
Next
|
Last
Pages: 1 2 Prev: FreeBSD Port: ja-lynx-2.8.7.dev9 Next: [HEADS UP] Xorg 7.5 merge comming tomorrow. |