| Newsgroups |
gmane.linux.lfs.automated |
| Message-ID |
<[email protected]> |
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
--
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page