close Warning: Failed to sync with repository "(default)": [Errno 12] Cannot allocate memory; repository information may be out of date. Look in the Trac log for more information including mitigation strategies.

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#166 closed defect (invalid)

jhalfs install stopped in chroot/e2fsprogs

Reported by: Brunno Owned by: clfs-commits@…
Priority: major Milestone: CLFS Standard 1.2.0
Component: BOOK Version: CLFS Standard 1.2.0
Keywords: Cc:

Description

I'm trying install development version of CLFS and its stops in this point:

make[2]: Entrando no diretório `/mnt/sis/jhalfs'


Building target 082-e2fsprogs [++++++++++++++++++++++\ls: impossível acessar /sources/e2fsprogs-1.40.4.tar.gz: Arquivo ou diretório não encontrado

+tar: a opção exige um argumento -- f

|Try tar --help' or tar --usage' for more information.

make[2]: [082-e2fsprogs] Erro 1 make[2]: Saindo do diretório `/mnt/sis/jhalfs' make[1]: [mk_SUDO] Erro 2 make[1]: Saindo do diretório `/mnt/sis/jhalfs'

<jhalfs 2.3.1> exit

This means that its failed to find the package and was not past his name for tar program, but the file is in the directory, but the symbolic link /sources -> /mnt/sis/sources, isn't created. I make the link but it's stops against:

jhalfs [ /mnt/sis/jhalfs ]$ make make[1]: Entrando no diretório `/mnt/sis/jhalfs'


Building target 082-e2fsprogs [+-make[1]: [082-e2fsprogs] Erro 127 ] 0 min. 1 sec

make[1]: Saindo do diretório `/mnt/sis/jhalfs' make: [mk_SUDO] Erro 2 jhalfs [ /mnt/sis/jhalfs ]$

Note: sis is the BUILD_DIR

Change History (3)

comment:1 Changed 14 years ago by Joe Ciccone

Please report non-clfs errors when using jhalfs to jhalfs, not clfs, reporting it here will not get it fixed.

comment:2 Changed 14 years ago by Joe Ciccone

Resolution: invalid
Status: newclosed

also, for the record, clfs standard 1.2.0 doesn't exist yet, it's a future milestone.

comment:3 Changed 14 years ago by Brunno

But the program retrieves the commands from the xml code of the book, if a failure occurs can be either the program as the xml code book.

About the milestone, which identify the relationship between milestones and version registered in CLFS trac?

Sorry about my persistence in this subjects, but the last time I installed a gnu/linux from the scratch was the LFS 6.1.

I had an interest in installing the CLFS recently seemed interesting the use of a tool like jhalfs to save time in the process.

I believe that even though perhaps boring, notes like mines, may help in the identification of problems that you and other developers of CLFS may not be aware that occur.

If the team of CLFS has no interest in this type of note, please let me know. I have no interest to be hampering the work of anyone.

Note: See TracTickets for help on using tickets.