[jhalfs] branch trunk updated: Fix $(BUILDDIR)/jhalfs/Makefile

"Git Owner" ([email protected] via alfs-discuss Mailing List) <[email protected]>
Newsgroups gmane.linux.lfs.automated
Message-ID <164901523145.30731.8890942149593284170@rivendell.linuxfromscratch.org>
This is an automated email from the git hooks/post-receive script.

git pushed a commit to branch trunk
in repository jhalfs.

The following commit(s) were added to refs/heads/trunk by this push:
     new 924a237  Fix $(BUILDDIR)/jhalfs/Makefile
924a237 is described below

commit 924a2378434b4f256606d91398c12392f0951b46
Author: Pierre Labastie <[email protected]>
AuthorDate: Sun Apr 3 21:42:25 2022 +0200

    Fix $(BUILDDIR)/jhalfs/Makefile
    
    Now that we have only lfs, some lines in the Makefile have been
    removed, but still some shell continuation (&& \) were left. This
    leads to weird error message (@ non existing command, or so).
    Remove the continuation characters.
---
 common/libs/func_wrt_Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/common/libs/func_wrt_Makefile b/common/libs/func_wrt_Makefile
index 7c5f75a..78bb3e1 100644
--- a/common/libs/func_wrt_Makefile
+++ b/common/libs/func_wrt_Makefile
@@ -232,7 +232,7 @@ LUSER_wrt_RunAsUser() {            # Calculate time with perl, footer to log fil
 (
 cat << EOF
 	@source ~/.bashrc && \\
-	\$(CMDSDIR)/`dirname $file`/\$@ >> \$(LOGDIR)/\$@$version 2>&1 && \\
+	\$(CMDSDIR)/`dirname $file`/\$@ >> \$(LOGDIR)/\$@$version 2>&1
 EOF
 ) >> $MKFILE.tmp
 }
@@ -248,7 +248,7 @@ CHROOT_wrt_RunAsRoot() {           #
 (
 cat << EOF
 	@source envars && \\
-	\$(crCMDSDIR)/`dirname $file`/\$@ >>\$(crLOGDIR)/\$@$version 2>&1 && \\
+	\$(crCMDSDIR)/`dirname $file`/\$@ >>\$(crLOGDIR)/\$@$version 2>&1
 EOF
 ) >> $MKFILE.tmp
 

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.

-- 
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.