On 2019-06-25 12:52 -0500, Bruce Dubbs via lfs-dev wrote:
> On 6/25/19 11:57 AM, Ryan Marsaw via lfs-dev wrote:
> > On Sun, 23 Jun 2019, Brendan L via lfs-dev wrote:
> > 
> > > Blog about the change in maintainership:
> > > https://people.gnome.org/~federico/blog/maintaining-bzip2.html
> > > 
> > > Here is another blog entry about the coming release:
> > > https://people.gnome.org/~federico/blog/preparing-the-bzip2-107-release.html
> > >  
> > > 
> > > 
> > > There is a fix for a new security issue.  Also the build system is now
> > > meson and cmake.
> > > -- 
> > > http://lists.linuxfromscratch.org/listinfo/lfs-dev
> > > FAQ: http://www.linuxfromscratch.org/faq/
> > > Unsubscribe: See the above information page
> > 
> > I was able to complete a LFS build using the latest git snapshot of
> > bzip2 (still no release tarball yet).
> > 
> > Here are my findings:
> > 
> > Chapter 5 (Constructing a Temporary System)
> > 
> > 1) Ninja and Meson will now need to be installed in Chapter 5, just
> > after the Python 3 package.
> > 
> > For ninja:
> > python3 configure.py --bootstrap
> > install -v -m 0755 ninja /tools/bin
> > 
> > For meson:
> > python3 setup.py build
> > python3 setup.py install --root=dest
> > cp -v -R dest/tools/* /tools
> > 
> > 2) Python 3 will need to be built with the switch "--with-ensurepip=yes" to
> > satisfy the installation of meson, which means that zlib and libffi will
> > need to be installed prior to Python 3, with "--with-system-ffi"
> > switch added to Python 3 configuration.

I think we can skip setuptools/pip things and use meson without installing it. 
There is a meson.py in meson source tarball.  We should be able to run meson
with "python3 /source/meson-xxxx/meson.py".

I'll try this approach tomorrow.
-- 
Xi Ruoyao <[email protected]>
School of Aerospace Science and Technology, Xidian University

-- 
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page

Reply via email to