Date: Fri, 6 Oct 2017 21:31:38 +0200 (CEST) From: Marco Beishuizen <mbeis@xs4all.nl> To: James Geering <j.geering@btinternet.com> Cc: freebsd-questions@freebsd.org Subject: Re: Cannot .configure WindowMaker 0.95.8 - Xmu lib issues Message-ID: <alpine.BSF.2.21.1710062125160.2053@yokozuna> In-Reply-To: <1507317531.4831.74.camel@btinternet.com> References: <1507310201.4831.52.camel@btinternet.com> <alpine.BSF.2.21.1710062004010.2053@yokozuna> <1507317531.4831.74.camel@btinternet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 6 Oct 2017, the wise James Geering wrote: > Oh I see; yes of course because following this concept one knows the > software from a third party has been 'ported' to the freeBSD platform > using the various libraries that are synchronised to that port version > -- right?? Correct. Dependent libraries are build and installed too, see below. > I still have the side-question though, which is why do I not have the > libXmu.so.* library in my file-system. When I install it using ports: > > % pkg install libXmu > > it installs but the libXmu is nowhere to be found? I really feel like > I'm missing a conceptual understanding here? I could be wrong but shouldn't this be done as root? Regarding libXmu: this library is a dependency of windowmaker so when windowmaker is build and installed via ports, libXmu will be build and installed also (if it doesn't exist on your system yet). Nice site to check on things like this is www.freshports.org. Regards, Marco -- Eagleson's Law: Any code of your own that you haven't looked at for six or more months, might as well have been written by someone else. (Eagleson is an optimist, the real number is more like three weeks.)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.21.1710062125160.2053>