Date: Sat, 15 Nov 2014 10:16:18 +0100 From: Gary Jennejohn <gljennjohn@gmail.com> To: Beeblebrox <zaphod@berentweb.com> Cc: FreeBSD X11 mailing list <freebsd-x11@freebsd.org> Subject: Re: x11-wm/enlightenment (e17) XComposite support Message-ID: <20141115101618.72719706@ernst.home> In-Reply-To: <20141114152650.0641309a@ernst.home> References: <5465BD81.1070700@berentweb.com> <20141114103827.2ff76411@ernst.home> <5465D059.60703@berentweb.com> <20141114130618.4d0c4ac5@ernst.home> <5466030E.4000604@berentweb.com> <CAPS9%2BSsA_pLpdgbp4BSJ1qjvniWSFcwmiyqWyJYzv936dNZPsw@mail.gmail.com> <546604D4.8050300@berentweb.com> <20141114152650.0641309a@ernst.home>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 14 Nov 2014 15:26:50 +0100 Gary Jennejohn <gljennjohn@gmail.com> wrote: [ldd output snipped] > There you go. Your e17 was apparently generated prior to the > installation of Xcomposite. > > Reinstall e17 and maybe its dependencies. It should automatically > pick up Xcomposite. > I deleted the reply from Beeblebrox about using poudrierre (or however it's spelled) to generate his ports. None of the stuff used by the enlightenment port seems to have an explicit dependency on xcomposite. In contrast, e16 _does_ have a dependency and therefore pulls it in as required. This could mean that libXcomposite gets compiled later than e17 so that e17 doesn't know it's available. A possible work around would be to simply reinstall enlightenment directly from the ports tree after libXcomposite is installed. -- Gary Jennejohn
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141115101618.72719706>