Re: problems with current jhalfs

"Pierre Labastie" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
On Mon, 2023-03-13 at 16:02 +0100, Thomas Seeling wrote:
> Hallo,
> 
> I checked out current git branch of jhalfs and I noticed a few problems:
> 
> 1.
> jhalfs script: the variable XSL is used empty resulting in the error message
> 
> 
> cp: cannot stat 'LFS/.xsl': No such file or directory
> 
> I patched it by adding "XSL=lfs.xsl" directly before the cp command.
> 
> The configuration file contains a line
> XSL=$PROGNAME.xsl
> so I assume PROGNAME should be defined somewhere but it isn't.

Actually, PROGNAME has been removed a while ago from "Config.in", but if you use
a "configuration" file made using the previous Config.in, the variable is still
there. The workaround (if you do not want to restart configuration from scratch,
that is, remove the "configuration" and "configuration.old" files before
configuring) is to edit "configuration" and replace "$PROGNAME" with "lfs".

> 
> 2.
> When downloading unzip60, there's an ambiguity with the filename. ftp download
> results in a ".tgz" file extension which then fails the check.
> 
> The wget command should use "-O unzip60.tar.gz" when downloading.

Hmm, I'm not sure exactly what you have done. Is it in the script generated for
blfs tools?

Pierre

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.