From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1edc79f4ba32df639f0df140d3f9b9f690cd2861
Date: Sat, 19 Aug 2023 14:30:49 +0000 [thread overview]
Message-ID: <4RSh495R9Tz2xTh@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1487 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 1edc79f4ba32df639f0df140d3f9b9f690cd2861 (commit)
from 0b0d4363cf53132d6871501027164dbf9e3a5423 (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1edc79f4ba32df639f0df140d3f9b9f690cd2861
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Aug 19 14:30:31 2023 +0000
qrencode: Fix build on riscv64
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/qrencode | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/lfs/qrencode b/lfs/qrencode
index aaf004b4d..2deb8b4cf 100644
--- a/lfs/qrencode
+++ b/lfs/qrencode
@@ -73,6 +73,7 @@ $(subst %,%_MD5,$(objects)) :
$(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar zxf $(DIR_DL)/$(DL_FILE)
+ $(UPDATE_AUTOMAKE)
cd $(DIR_APP) && ./configure --prefix=/usr
cd $(DIR_APP) && make $(MAKETUNING) $(EXTRA_MAKE)
cd $(DIR_APP) && make install
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2023-08-19 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4RSh495R9Tz2xTh@people01.haj.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox