From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. d73709d8ee01b5e39f6f6ca85801c3c28c18414d
Date: Thu, 06 May 2021 09:48:52 +0000 [thread overview]
Message-ID: <4FbTLD4CGMz2xRH@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1500 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 d73709d8ee01b5e39f6f6ca85801c3c28c18414d (commit)
from be28aade968899ee907cc135e0158e23f7fe2908 (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 d73709d8ee01b5e39f6f6ca85801c3c28c18414d
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu May 6 09:48:31 2021 +0000
ffmpeg: Honour CFLAGS and LDFLAGS
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/ffmpeg | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/ffmpeg b/lfs/ffmpeg
index 976a4ab13..dbc2e933e 100644
--- a/lfs/ffmpeg
+++ b/lfs/ffmpeg
@@ -86,7 +86,10 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
@$(PREBUILD)
@rm -rf $(DIR_APP) && cd $(DIR_SRC) && tar axf $(DIR_DL)/$(DL_FILE)
- cd $(DIR_APP) && ./configure \
+ cd $(DIR_APP) && \
+ CFLAGS="$(CFLAGS)" \
+ LDFLAGS="$(LDFLAGS)" \
+ ./configure \
--prefix=/usr \
--enable-shared \
--enable-gpl \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2021-05-06 9:48 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=4FbTLD4CGMz2xRH@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