Date: Tue, 22 Aug 2023 09:50:46 +0200 From: Felix Palmen <zirias@freebsd.org> To: ports@freebsd.org, emulation@freebsd.org Subject: Re: Building a Linuxulator userland from source Message-ID: <nvl3etkac6d6miv4axj2mjbdtkkzc7rqrcqbco4f5uzljz5ryk@vlp2l4mirabf> In-Reply-To: <67ea2b0e1f9ed5c695fb50c3d9a1d378@Leidinger.net> References: <xcztahm3vu3bjghjqqxuoy2xabyjmyfq22jw6mkaaaqo7wa36s@fdq7dlvpuhlk> <d1fdffa65d8d83018448ea2565bee397@Leidinger.net> <pusevat67254zxani3p26zpktfozyeopw6nm2gxbkjvq7o4d5h@573vplxfsmsq> <67ea2b0e1f9ed5c695fb50c3d9a1d378@Leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--pr6a2ixrlujzdhyn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable * Alexander Leidinger <Alexander@Leidinger.net> [20230822 01:25]: > Am 2023-08-18 11:26, schrieb Felix Palmen: > > 1.) Of course, Uses/linux.mk would need quite some switching to handle > > c7 as well as something new that works completely differently (maybe > > call it src). All still open issues. >=20 > I suggest to write a new Uses/xxx.mk for this. Much more easy for you to = do > what you want, and less error prone and less QA to do for the existing > linux_base stuff. Thanks! Actually, I had this thought already but was unsure about it. So, someone else suggesting exactly the same is quite convincing. My goal is to replace -c7 with my project, but of course, even if that succeeds, it means both userlands will need to coexist for quite some time, and that's probably indeed easier with completely separate Uses. > > 2.) Could you please elaborate how e.g. some config file "visible" to > > the Linux processes could "pollute" a Linux build? Besides, this could > > only affect files from base /etc I think... >=20 > Well... the config part was more to highlight what the linux_base ports u= se > the fallthrough for. In case of building I worry more that some includes > from /usr/local are used than anything else. Also some other stuff > configure-runs might pick-up from the installed FreeBSD ports. I assume/hope that's a minor risk. /usr/local is not in the standard search paths of the toolchain, so, must be added explicitly. A build system doing that without being requested to do so would be pretty much broken. Furthermore, the toolchain is built --with-sysroot=3D/compat/linux so prepends that to all the system search paths. Configure scripts finding *tools* in FreeBSD's /usr/local *might* be a risk. Not an issue building with poudriere (the build jail will only have what we want), but maybe an issue when someone builds the ports in a live system. Well, we will see :) At least, I already have the first ports building fine using shell and make from the Linux userland, e.g. here: https://github.com/Zirias/zfbsd-ports/blob/linux/sysutils/linux-man-db/Make= file Cheers, Felix --=20 Felix Palmen <zirias@FreeBSD.org> {private} felix@palmen-it.de -- ports committer -- {web} http://palmen-it.de {pgp public key} http://palmen-it.de/pub.txt {pgp fingerprint} 6936 13D5 5BBF 4837 B212 3ACC 54AD E006 9879 F231 --pr6a2ixrlujzdhyn Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iNUEABYKAH0WIQRpNhPVW79IN7ISOsxUreAGmHnyMQUCZORoxV8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0Njkz NjEzRDU1QkJGNDgzN0IyMTIzQUNDNTRBREUwMDY5ODc5RjIzMQAKCRBUreAGmHny MbsqAQCA+cGpGpXlMbtYtMwS2gGaCYDrjEyDp+0J+iyKnyZOugD/VEbrJ0ztd9ib IPWJ1XYLEkuNQBQFiGA/6ZJzfqExfg4= =I6iy -----END PGP SIGNATURE----- --pr6a2ixrlujzdhyn--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?nvl3etkac6d6miv4axj2mjbdtkkzc7rqrcqbco4f5uzljz5ryk>