Date: Sun, 28 Jun 2009 14:14:15 -0800 From: Mel Flynn <mel.flynn+fbsd.questions@mailing.thruhere.net> To: freebsd-questions@freebsd.org Subject: Re: libtool shared Message-ID: <200906281414.16019.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> In-Reply-To: <6ae50c2d0906281340p68b5f8ewa41095e694cf5ff8@mail.gmail.com> References: <6ae50c2d0906281009n24381ad3j59125e237739ca2c@mail.gmail.com> <h28a06$hmt$1@ger.gmane.org> <6ae50c2d0906281340p68b5f8ewa41095e694cf5ff8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sunday 28 June 2009 12:40:24 alexus wrote: > company policy not too use ports, any other suggestions? Understand GNU autotools in detail, the patches for it in the respective ports, how to read config.log and whether all this is worth compliance to company policy. Note: the above requires at least two weeks of non-productive self-education on the boss' clock, judging from the fact you post configure output, rather then config.log snippets (without being judgmental or condescending: it shows you are just starting with the GNU autotools experience). Recently Giorgos posted a nice summary of what you'd need to learn [1]. Of course, I'm presuming installing/maintaining software is something that belongs to your daily tasks. If you only need to fix this specific problem, we would need output from config.log around the lines where it says it can't build shared libs. [1] http://www.freebsd.org/cgi/mid.cgi?db=mid&id=87hbyk6h02.fsf@kobe.laptop -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200906281414.16019.mel.flynn%2Bfbsd.questions>