Building BLFS packages in LFS chroot
Hans Malissa <[email protected]> Sat, 28 Mar 2020 20:23:19 -0000
| Newsgroups | gmane.linux.lfs.general |
|---|---|
| Message-ID | <[email protected]> |
--===============6508350075087565024==
Content-Type: multipart/alternative; boundary=Apple-Webmail-42--f13a8f89-622d-45a3-b8f9-e5187109d159
--Apple-Webmail-42--f13a8f89-622d-45a3-b8f9-e5187109d159
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=utf-8;
format=flowed
Hi all,=0A=0AI'm going to build=C2=A0a few packages from BLFS while still =
in the LFS chroot. Most importantly, those are gpm, lynx, wget, wpa_suppli=
cant, pciutils, usbutils, and their dependencies; some of these are nice t=
o have at hand. (There is a nice list of BLFS packages to be built in LFS =
chroot at=C2=A0http://www.linuxfromscratch.org/~ken/tuning/tuning-1-packag=
es-and-notes.txt=C2=A0although no rationale is given why these packages ar=
e chosen.)=0ANow, there are definitely differences between a full LFS envi=
ronment and the chroot environment. From what I'm noticing, the most obvio=
us ones would be that (a) in BLFS it is assumed that the packages is confi=
gured and built as a non-root user an only installed as a root user and (b=
) several bash variables are missing, like LANG or similar. Are there any =
generic instructions of how the instructions from BLFS for building any pa=
rticular package need to be modified for LFS? Does it make sense to set up=
a non-root user at the end of LFS for building the BLFS packages? Or to s=
et up some important bash variables?=0AGreetings,=0A=0AHans
--Apple-Webmail-42--f13a8f89-622d-45a3-b8f9-e5187109d159
Content-Type: multipart/related;
type="text/html";
boundary=Apple-Webmail-86--f13a8f89-622d-45a3-b8f9-e5187109d159
--Apple-Webmail-86--f13a8f89-622d-45a3-b8f9-e5187109d159
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8;
<html><body><div>Hi all,</div><div><br data-mce-bogus=3D"1"></div><div>I'm going to bu=
ild a few packages from BLFS while still in the LFS chroot. Most impo=
rtantly, those are gpm, lynx, wget, wpa_supplicant, pciutils, usbutils, an=
d their dependencies; some of these are nice to have at hand. (There is a =
nice list of BLFS packages to be built in LFS chroot at <a href=3D"ht=
tp://www.linuxfromscratch.org/~ken/tuning/tuning-1-packages-and-notes.txt"=
>http://www.linuxfromscratch.org/~ken/tuning/tuning-1-packages-and-notes.t=
xt</a> although no rationale is given why these packages are chosen.)=
</div><div>Now, there are definitely differences between a full LFS enviro=
nment and the chroot environment. From what I'm noticing, the most obvious=
ones would be that (a) in BLFS it is assumed that the packages is configu=
red and built as a non-root user an only installed as a root user and (b) =
several bash variables are missing, like LANG or similar. Are there any ge=
neric instructions of how the instructions from BLFS for building any part=
icular package need to be modified for LFS? Does it make sense to set up a=
non-root user at the end of LFS for building the BLFS packages? Or to set=
up some important bash variables?</div><div>Greetings,</div><div><br data=
-mce-bogus=3D"1"></div><div>Hans</div></body></html>
--Apple-Webmail-86--f13a8f89-622d-45a3-b8f9-e5187109d159--
--Apple-Webmail-42--f13a8f89-622d-45a3-b8f9-e5187109d159--
--===============6508350075087565024==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline
LS0gCmh0dHA6Ly9saXN0cy5saW51eGZyb21zY3JhdGNoLm9yZy9saXN0aW5mby9sZnMtY2hhdApG
QVE6IGh0dHA6Ly93d3cubGludXhmcm9tc2NyYXRjaC5vcmcvYmxmcy9mYXEuaHRtbApVbnN1YnNj
cmliZTogU2VlIHRoZSBhYm92ZSBpbmZvcm1hdGlvbiBwYWdlCg==
--===============6508350075087565024==--