On Thu, 2020-12-03 at 19:18 +0000, Ken Moffat wrote:
> On Sat, Nov 28, 2020 at 08:15:45PM +0000, Ken Moffat wrote:
>
> > [...]
>
> Still floundering, trying to work out how to generate the Makefile
> for BLFS.
>
> I've used my own scripts for LFS, followed by libtasn1, p11-kit,
> make-ca,
> wget, ca-certs, sgml-common, OpenSP, openjade, unzip, docbook31,
> docbook45, dsssl, SGMLSpm, docbook-utils, libxml2, docbook-xml,
> libxslt, sudo, creation of /etc/sudoers, sqlite, apr, apr-util,
> scons, serf, subversion.
>
> Tnen I entered chroot via an xfce-term and ran (ignoring the many
> false steps):
>
> su - lfs
> svn co svn://svn.linuxfromscratch.org/ALFS/jhalfs/trunk jhalfs-svn
> (I figured that having jhalfs/jhalfs as the directory would confuse
> me, my user for this is called jhalfs)
> cd jhalfs-svn
> sudo mkdir /var/lib/jhalfs
> sudo chown -R jhalfs:jhalfs /var/lib/jhalfs
> ./install-blfs-tools.sh
This is the old method. It's better to use the menu: run make from the
jhalfs-svn dir then choose "Use Book --> Beyond Linux From Scratch" in
the menu. Some Other menu entries allow to customize the installation
paths, the init system, etc.
>
>
> That successfully downloaded BLFS r23951
>
> I then adjusted BLFS/envars.conf to do what I thought was needed.
Ah, that's the problem: the tools are installed in a different
directory ($HOME/blfs_root by default), so you should cd to that
directory, and work from there (edit envars.conf in that directory, and
run make there)
>
> Looking at the BLFS Makefile, I had the impression that just running
> 'make' should be enough to create something I could look at to see
> what could be run, and what might need adjustment before I tried to
> build something simple ('which' seems a pretty simple first package)
> and see what happened. But that appears to be the wrong command, or
> else run from the wrong place.
Yes, that should be ok provided you start from the installed directory,
not the jhalfs subversion tree.
>
> First, it appeared to again download BLFS r23951, but then it failed
> with lots of messages all saying:
>
> warning: failed to load external entity "/home/jhalfs/jhalfs-
> svn/BLFS/xsl/tracking-dir/instpkg.xml"
>
> and then at the end:
>
> python3: can't open file '/home/jhalfs/jhalfs-
> svn/BLFS/menu/menuconfig.py': [Errno 2] No such file or directory
>
> The menuconfig.py file is in ...jhalfs-svn/menu/menuconfig.py so I
> assume that I should NOT be running 'make' in BLFS/.
True, see above...
>
> Is there an idiot's guide to using jhalfs for BLFS, pretty please ?
Well, "README.BLFS" "3.1 INSTALLATION ON A RUNNING SYSTEM" is all I can
propose.
But I guess what is misleading is:
-------
4. USAGE::
From now on, all the work must be done from inside the installation
root directory.
-------
I need to reword that to tell it is the directory chosen as "Root of
the tools directory" in the menu.
(or "$HOME$BLFS_ROOT" when running install-blfs-tools.sh directly)
Note that it may be interesting to run "update-lfs.sh" so that lfs
packages appear in the menu only if they are newer than the installed
one (next time Bruce updates lfs).
HTH
Pierre
--
http://lists.linuxfromscratch.org/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
