| Newsgroups |
gmane.linux.lfs.automated |
| Message-ID |
<[email protected]> |
On Thu, 2022-06-16 at 13:28 +0300, Yasin YILMAZ wrote:
> 16.06.2022 12:34 tarihinde Yasin YILMAZ ([email protected] via
> alfs-discuss Mailing List) yazdı:
> >
> > 16.06.2022 08:13 tarihinde Pierre Labastie ([email protected]
> > via alfs-discuss Mailing List) yazdı:
> > > On Wed, 2022-06-15 at 23:29 -0500, Bruce Dubbs wrote:
> > > > On 6/15/22 22:05, Yasin YILMAZ ([email protected] via
> > > > alfs-discuss
> > > > Mailing
> > > > List) wrote:
> > > >
> > > > > > It is unclear that you disabled the checks. You can check by
> > > > > > looking at
> > > > > >
> > > > > > /mnt/lfs/jhalfs/lfs-commands/chapter08/803-glibc
> > > > > >
> > > > > > If the checks are really disabled there should be a line:
> > > > > > # make -k check >> $TEST_LOG 2>&1 || true
> > > > > >
> > > > > > The # is important.
> > > > > >
> > > > > > What I would suggest is starting over. First, make sure all the
> > > > > > virtual
> > > > > > files
> > > > > > systems are unmounted. Use the findmnt command to check, Then as
> > > > > > the
> > > > > > root user
> > > > > >
> > > > > > rm -rf /mnt/lfs/{bin,dev,home,lib,mnt,proc,run,sys,usr}
> > > > > > rm -rf
> > > > > > /mnt/lfs/{boot,etc,jhalfs,lib64,media,opt,root,sbin,srv,tmp,var}
> > > > > >
> > > > > > Be VERY careful with the above. You do not want to remove these
> > > > > > directories on the
> > > > > > host.
> > > > > >
> > > > > > When you have finished, you should only have
> > > > > > /mnt/lfs/{sources,lost+found}
> > > > > > Now remove any sub-directories in /mnt/lfs/sources.
> > > > > >
> > > > > > Then remove your jhalfs git directory and
> > > > > >
> > > > > > git clone git clone git://git.linuxfromscratch.org/jhalfs.git
> > > > > >
> > > > > > Then 'cd jhalfs.git' and run 'make' paying careful attention to
> > > > > > all the
> > > > > > options.
> > > > > >
> > > > > > That should get you back to a clean start.
> > > > > I implemented what you said. I am encountering the same error
> > > > > again. Is
> > > > > there an
> > > > > alternative solution?
> > > > The only think I can think of is to manually mount the virtual file
> > > > systems,
> > > > enter
> > > > chroot, and continue manually.
> > > I am not sure, but if it is the same error again, it means you have
> > > again
> > > selected "Abort on first testsuite failure". Do not do that (or use
> > > commit
> > > 594ff3d87 or later of jhalfs).
> > >
> > > Pierre
> > >
> >
> > After removing the part about the latest testsuite, after the update
> > you gave, I pulled the jhalfs again and tried again. Strangely enough,
> > it keeps giving the same error. Now I will try and update the language
> > structure from tr_TR.UTF-8 to en_US.UTF-8 and A4 page structure to
> > Letter.
> >
> > If it doesn't happen this time, I will go into the chroot environment
> > as Bruce said and continue, but in this case, there is no reason to
> > configure LFS + Pacman with jhalfs :(
> >
> > --
> > Yasin YILMAZ
> >
>
> I want to add all my settings so you can see if there is something wrong
> somewhere.
>
>
> [lfs@lab jhalfs]$ make
> Loaded configuration 'configuration'
> No changes to save (for 'configuration')
> Do you want to run jhalfs? yes/no (yes): yes
> Loading config params from <configuration>...OK
> Loading file common/common-functions...OK
> Loading file common/libs/func_book_parser...OK
> Loading file common/libs/func_download_pkgs...OK
> Loading file common/libs/func_wrt_Makefile...OK
> Loading file LFS/master.sh...OK
> ------------------------------------------------------------------------------
> Loading file common/libs/func_check_version.sh...OK
> Loading file common/libs/func_validate_configs.sh...OK
> Loading file common/libs/func_custom_pkgs...OK
> ------------------------------------------------------------------------------
> Checking tools required for jhalfs
> SUDO <1.9.11p1> OK (Min version: 1.7.0)
> WGET <1.21.3> OK (Min version: 1.0.0)
> LIBXML2 <2.09.14> OK (Min version: 2.06.20)
> LIBXSLT <1.01.35> OK (Min version: 1.01.14)
> DocBook XML DTD <4.5> OK (Min version: 4.5)
> DocBook XSL stylesheets <current> OK (Min version: current)
> ------------------------------------------------------------------------------
> COMMIT <11.1>
> BOOK </mnt/lfs/jhalfs/book-source>
> CUSTOM_TOOLS <n>
> INITSYS <systemd>
> BLFS_TOOL <n>
> LUSER <lfs>
> LGROUP <lfs>
> LHOME </home>
> BUILDDIR </mnt/lfs>
> CLEAN <y>
> GETPKG <y>
> SRC_ARCHIVE <> <-- NO directory name given
> SERVER <http://ftp.osuosl.org>
> RETRYSRCDOWNLOAD <y>
> RETRYDOWNLOADCNT <20>
> DOWNLOADTIMEOUT <30>
> RUNMAKE <y>
> TEST <1>
> STRIP <y>
> NCURSES5 <y>
> DEL_LA_FILES <y>
> FSTAB <>
> CONFIG <>
> TIMEZONE <Europe/Istanbul>
> PAGE <letter>
> LANG <en_US.UTF-8>
> INSTALL_LOG <y>
> PKGMNGT <y>
> FULL_LOCALE <y>
> WRAP_INSTALL <n>
> HOSTNAME <localhost>
> INTERFACE <eth0>
> IP_ADDR <10.0.2.9>
> GATEWAY <10.0.2.2>
> PREFIX <24>
> BROADCAST <10.0.2.255>
> DOMAIN <localdomain>
> DNS1 <10.0.2.3>
> DNS2 <8.8.8.8>
> FONT <lat0-16>
> KEYMAP <us>
> LOCAL <y>
> LOG_LEVEL <>
> COMPARE <n>
> OPTIMIZE <1>
> N_PARALLEL <4>
> SAVE_CH5 <y>
> REPORT <y>
> REBUILD_MAKEFILE <y>
The last one should be "n" when you restart.
Do not tick:
[ ] Rebuild the Makefile (see help)
The help says:
#-- Rebuild the Makefile
#
# This option allows to rebuild the Makefile after
# customizing the base system build scripts.
#
# See README.CUSTOM for more info about this feature.
# Note that you should do that after configuring a jhalfs
# build, and only if you need changing the build scripts order
# or add a new one.
You should only tick this if you need to change the order or customize the
scripts respective to the book. It is almost never needed in practice.
Pierre
--
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page