Re: [lfs-dev] [RFC] remove obsolete clfs code in jhalfs

"William Harrington" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated,gmane.linux.lfs.devel,gmane.linux.lfs.devel
Message-ID <4406240.LvFx2qVVIh@nuclear>
On Wednesday, February 23, 2022 10:50:32 AM CST William Harrington wrote:
> On Wednesday, February 23, 2022 9:35:32 AM CST James B wrote:
> 
> Greetings,
> 
> As a previous dev of CLFS, it wouldn't hurt to keep it in jHALFS, but also
> wouldn't gain much of anything keeping it in there. I built a clfs sysroot
> with current versions of packages for an M68K KISS 68030 system recently.
> The historical value is great. Keep it or remove it, fine either way.
> 
> My focus is on ARM in LFS. A future focus may be a Power9 system from Talos.
> 
> 007 brings up a good point. Valid.
> 
> Sincerely,
> 
> William Harrington

Greetings,

More info I left out:

The lfs-arm book is in synch with the LFS book, but there are a few edits 
regarding arm in the glibc and gcc sections.

ISL is also included ( matter of preference, also the gcc contrib script will 
download isl, may be required in the future)

Readline disables bracketed paste by default

GRUB can be removed (Boot section still needs updating)

If we did incorporate that into the LFS book, we'd need a way for the xml to 
render a book for arm kinda like we do for systemd and sysvinit. I kept it 
separate now as it is the best way. If someone chimes in with a way to manage 
it, sure. For now, it is separate.

Sincerely,

William Harrington

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.