Date: Sat, 7 Jul 2012 09:20:53 +0100 From: David Chisnall <theraven@freebsd.org> To: Andriy Gapon <avg@freebsd.org> Cc: toolchain@freebsd.org Subject: Re: gcc46 header search path Message-ID: <7937CE7E-2583-4DAF-9782-37B82891D3FF@freebsd.org> In-Reply-To: <4FF766D6.5040909@FreeBSD.org> References: <4FF60A9E.5070503@FreeBSD.org> <4FF6DB51.40904@FreeBSD.org> <508B8B4E-DF5E-412B-BD2B-86F21EBF4C8C@bsdimp.com> <4FF700CF.2000206@FreeBSD.org> <1DED79CC-CACD-4D22-9F1F-E3EB17938EB6@bsdimp.com> <4FF7182A.9070803@FreeBSD.org> <714BF622-A1B3-4A4A-A8BC-DCA82B4434A2@FreeBSD.org> <4FF766D6.5040909@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Jul 2012, at 23:29, Andriy Gapon wrote: > I think that this is a dummy argument. One could easily want his = LOCALBASE to > be /opt and the real ports system should support that. So what ports = currently > do, they really have to do (assuming $LOCALBASE as opposed to = /usr/local). That's completely irrelevant. If a user installs things in a = non-standard location, then that user should expect to have to point = things that they build from source at that non-standard location. If, = however, a user installs things in the standard location, then this = should Just Work. =20 The workflow that I have seen where this fails: - User runs ./configure - Configure script says 'libpng is not installed!' - User installs libpng from ports / packages - User runs ./configure - Configure script says 'libpng is not installed!' - User sends me an email asking why they can't install on FreeBSD, = usually including a small whine that this works on their favourite Linux = distro. - I tell the user 'Oh, you need to say = --with-png-include=3D/usr/local/include --with-png-lib=3D/usr/local/lib' - User says 'Why doesn't the compiler that FreeBSD ships know where to = find headers and libraries that FreeBSD installs?' - I shrug. I assumed this was done for a sensible reason, but so far no one has = actually said what that reason is. In an ideal world, the system = compiler should be able to automatically find any headers and libraries = installed by any supported mechanism (ports, pkg_add, pkg add), but in = an almost-ideal world it should at least find them if they are in the = default locations. David=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7937CE7E-2583-4DAF-9782-37B82891D3FF>