Date: Mon, 3 May 2010 11:48:36 +0200 From: Gabor PALI <pgj@FreeBSD.org> To: Giuseppe Pagnoni <gpagnoni@gmail.com> Cc: Haskell@freebsd.org, freebsd-ports@freebsd.org Subject: Re: FreeBSD Port: xmonad-0.9.1_1 Message-ID: <g2h685a6ef81005030248h7d14a45cpeff95ec99bb61267@mail.gmail.com> In-Reply-To: <l2l92056ebc1005030201hc3c91df7yaa32f88c6665761a@mail.gmail.com> References: <w2r92056ebc1004301039n6b6ebfc2j4689a10386c7be4a@mail.gmail.com> <4BDB39F5.7080500@FreeBSD.org> <l2l92056ebc1005030201hc3c91df7yaa32f88c6665761a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 3, 2010 at 11:01 AM, Giuseppe Pagnoni <gpagnoni@gmail.com> wrot= e: > Yep, that was exactly the problem. =A0Removing 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?g2h685a6ef81005030248h7d14a45cpeff95ec99bb61267>