Hi,
A few comments from a new user yet oldtimer.
The check_prerequisites() in common/libs/func_check_version.sh fails on
FIND and GREP because "fancy" version numbers on Knoppix 5.1 contain
intermediate noise words which confuse the 'cut -d" " -f4'.
I had to pick the last string :
------------------------------------------------------
getlast() {
read ARG
expr "$ARG" : ".* \([^ ]*$\)"
}
...
check_version "4.1.20" "$(find --version | head -n1 | getlast)"
"FIND"
...
check_version "2.5" "$(grep --version | head -n1 | getlast)"
"GREP"
---------------------------------------
The default location of the makefile is such that it clobbers the
original jhalfs/Makefile
>From 'configuration'
-------------------------------------
SCRIPT_ROOT="jhalfs"
JHALFSDIR="$BUILDDIR/$SCRIPT_ROOT"
...
MKFILE="$JHALFSDIR/Makefile"
-------------------------------------
And this does come from Config.in
-------------------------------------------------------
config MKFILE
string "Makefile"
default "$JHALFSDIR/Makefile"
-------------------------------------------------------
Is there any purpose to this or is this a joke?
It seems that the scripts fail to initially create the '*-commands'
directories
and rely on their presence to assume that "something" has already been
created :
>Are you happy with these settings? yes/no (no): yes
>
>------------------------------------------------------------------------------
>
>Creating Makefile... START DIR /mnt/b0830/jhalfs PROG hlfs
>HLFS/master.sh: line 498: cd: /mnt/b0830/jhalfs/hlfs-commands: Aucun fichier
>ou répertoire de ce type
>From func_book_parser lines 28...
-------------------------------------------------------------------
# Grab a fresh book if it's missing, otherwise, update it from the
# repo. If we've already extracted the commands, move on to getting
the
# sources.
if [ -d ${PROGNAME}-$LFSVRS ] ; then
cd ${PROGNAME}-$LFSVRS
.../...
else
svn co $SVN/${svn_root}/${TREE} ${PROGNAME}-$LFSVRS >>$LOGDIR/$LOG 2>&1
echo -ne "done\n"
extract_commands
fi
--------------------------------------------------------------------
Too bad svn didn't run...
No wonder, this was done offline!
Same kind of problems with 'jhalfs/pkg_tarball_list' same cause I guess.
Overall, the whole thing tries to be exceedingly clever but falls short of the
most basic reliability requirements.
And BTW, thanks for trying to "educate" me :->
> To use this tool you MUST:
>
> - have experience building {c,h,b}LFS packages
NO! I don't want to, on the contrary I want to use ALFS to get this
experience even if the learning curve is steeper
> - know how to edit and write shell scripts
yes
> - know how a Makefile works
yes
> - be able to trace build failures and to find what is causing it
> (user error, package bug, {c,h,b}LFS command bug, or jhalfs code bug)
yes
>
> If you do not have the above skills, please don't use this tool.
If you do not have software engineering skills beyond "cleverness" I suggest
you read this:
http://catb.org/~esr/writings/cups-horror.html
JLD
P.S. I'll manage thru anyway, just been upset...
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
