From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 7cc5c8a2b79c58bca5a06887ffeda0159c50a3a6
Date: Wed, 14 May 2025 16:47:23 +0000 (UTC) [thread overview]
Message-ID: <4ZyK5773f7z2xT4@people01.haj.ipfire.org> (raw)
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 7cc5c8a2b79c58bca5a06887ffeda0159c50a3a6 (commit)
from 5904802e7bc16b201e7887761b3f8a1fc133bb28 (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 7cc5c8a2b79c58bca5a06887ffeda0159c50a3a6
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Wed May 14 16:44:54 2025 +0000
udev: Don't fail if the linker emits any warnings
This only appears on aarch64.
[436/452] Linking target src/udev/v4l_id
FAILED: src/udev/v4l_id
cc -o src/udev/v4l_id src/udev/v4l_id.p/v4l_id_v4l_id.c.o -Wl,--as-needed -Wl,--no-undefined -Wl,-O1 -fstack-protector -O2 -g0 -pipe -Wall -fexceptions -fPIC -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -fstack-protector-strong -fstack-clash-protection -mbranch-protection=standard -Wl,--start-group src/shared/libsystemd-shared-254.a src/libsystemd/libsystemd_static.a src/basic/libbasic.a src/basic/libbasic-compress.a -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common -Wl,--gc-sections -pthread /usr/lib/libacl.so /usr/lib/libblkid.so /usr/lib/libcap.so /usr/lib/libcrypt.so -ldl /lib/libip4tc.so /lib/libip6tc.so /usr/lib/libkmod.so /usr/lib/libmount.so /usr/lib/libssl.so /usr/lib/libcrypto.so /usr/lib/libpam.so -lrt /usr/lib/liblzma.so /usr/lib/libzstd.so -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common -Wl,--gc-sections -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common -Wl,--gc-sections -lm -Wl,--end-group -Wl,--fa
tal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common -Wl,--gc-sections -Wl,--fatal-warnings -Wl,-z,now -Wl,-z,relro -Wl,--warn-common -Wl,--gc-sections
/usr/lib/libcrypto.so: warning: GCS is required by -z gcs, but this shared library lacks the necessary property note. The dynamic loader might not enable GCS or refuse to load the program unless all the shared library dependencies have the GCS marking.
/usr/lib/libzstd.so: warning: GCS is required by -z gcs, but this shared library lacks the necessary property note. The dynamic loader might not enable GCS or refuse to load the program unless all the shared library dependencies have the GCS marking.
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
Reported-by: Adolf Belka <adolf.belka@ipfire.org>
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/udev | 3 +++
1 file changed, 3 insertions(+)
Difference in files:
diff --git a/lfs/udev b/lfs/udev
index f182f1289..19e0557a3 100644
--- a/lfs/udev
+++ b/lfs/udev
@@ -76,6 +76,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && patch -Np1 < $(DIR_SRC)/src/patches/systemd-254-linux-6.12-fs.patch
cd $(DIR_APP) && tar axf $(DIR_DL)/udev-lfs-$(RULES_VER).tar.xz
+ # Don't fail if the linker shows a warning
+ cd $(DIR_APP) && sed -e "/fatal-warnings/d" -i meson.build
+
# Remove two unneeded groups (render and sgx) from the default udev rules
cd $(DIR_APP) && sed -i -e 's/GROUP="render"/GROUP="video"/' \
-e 's/GROUP="sgx", //' rules.d/50-udev-default.rules.in
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2025-05-14 16:47 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=4ZyK5773f7z2xT4@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