Date: Tue, 28 Jun 2016 17:43:43 -0700 From: Alfred Perlstein <alfred@freebsd.org> To: Julian Elischer <julian@freebsd.org>, "ports@FreeBSD.org" <ports@freebsd.org> Subject: Re: best way to tune ports to add a CLFAGS entry Message-ID: <577319BF.5040403@freebsd.org> In-Reply-To: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org> References: <7d454696-f910-7533-5757-74eb624f9315@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/28/16 9:52 AM, Julian Elischer wrote: > At work I am doing various cross compiles in order to make a product > under freebsd that actually will run under a modified FreeBSD that > runs on an appliance. We want to get away from hand rolling everything > to leverage all teh work in getting ports working well on FreeBSD. > > We have some extra syscalls and some structures have different sizes, > so we need to compile/link agains an alternate set of > includes/libraries and not those in /usr/include or /usr/lib. > > Ideally I want to use the "--sysroot" and "-isystem" options to the > compiler/linker or failing that, add a -I or -L entries to make it > look at the correct includes and libraries, not those in the base system. > > > In many ports CFLAGS etc. are sent in via the arguments to ./configure > or environment vars, but there are many other ports that have other > ways to specify these. > > Does the ports framework have any standard way to do this? > LDEXTRA_ARGS or EXTRA_CFLAGS or similar? > > I've looked around and can't really see anything. Best would be a > single file to which I could add these things but adding them to the > environment would also work. > > yours in ports ignorance.. Sounds like a decent idea to override includedirs, but I wouldn't trust it. :) Why not do what NANOBSD/FreeNAS do and compile inside a chroot (or even VM) with the proper includes and such installed? It sounds like a big sledgehammer to use a chroot or a VM, but in reality it's MUCH safer than some port accidentally pulling something from the wrong /usr/include and then you spending hours, days, etc tracking it down. Trust me, I've seen the fallout and it's NOT FUN!!! For FreeNAS we made it so that you could run the FreeNAS OS (trueos) as the actual build server and that saved us a huge number of headaches. If you're very, very against the idea of VM or chroot then you could just make /usr/include actually contain YOUR includes as you probably shouldn't need them otherwise on a build server. -Alfred -Alfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?577319BF.5040403>