From: Michael Tremer <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 3.x development tree branch, master, updated. 074d1301531b005c7463b797df6c6bbb2ac91979
Date: Sun, 08 Oct 2023 16:14:22 +0000 [thread overview]
Message-ID: <4S2Dvg07lJz2xg8@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3257 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 3.x development tree".
The branch, master has been updated
via 074d1301531b005c7463b797df6c6bbb2ac91979 (commit)
via f9e570fc05b081503415ef22e79d7c434908f682 (commit)
from 1426e4823bb862dd38da56091fc882a58495b10a (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 074d1301531b005c7463b797df6c6bbb2ac91979
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Oct 6 16:50:25 2023 +0000
elfutils: Correctly configure debuginfod
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit f9e570fc05b081503415ef22e79d7c434908f682
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Fri Oct 6 16:30:59 2023 +0000
gdb: Update to 13.2
This patch also enables support for debuginfod.
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
elfutils/elfutils.nm | 16 +++++++++++++---
gdb/gdb.nm | 4 +++-
2 files changed, 16 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/elfutils/elfutils.nm b/elfutils/elfutils.nm
index 4fdb6d955..61220a3d0 100644
--- a/elfutils/elfutils.nm
+++ b/elfutils/elfutils.nm
@@ -5,7 +5,7 @@
name = elfutils
version = 0.189
-release = 1
+release = 2
groups = Development/Libraries
url = https://sourceware.org/elfutils/
@@ -24,6 +24,8 @@ source_dl = https://sourceware.org/elfutils/ftp/%{version}/
sources = %{thisapp}.tar.bz2
build
+ DEBUGINFOD_URLS = "https://pakfire.ipfire.org/"
+
requires
bzip2-devel
curl-devel
@@ -39,6 +41,11 @@ build
test
make check
end
+
+ install_cmds
+ # Export DEBUGINFOD_URLS
+ echo "%{DEBUGINFOD_URLS}" > %{BUILDROOT}%{sysconfdir}/debuginfod/%{DISTRO_SNAME}.urls
+ end
end
packages
@@ -56,8 +63,11 @@ packages
package %{name}-libs
template LIBS
- files += %{libdir}/lib*%{version}.so
- files += %{libdir}/elfutils
+ files
+ %{sysconfdir}/debuginfod
+ %{sysconfdir}/profile.d/debuginfod*
+ %{libdir}/lib*%{version}.so
+ end
end
package %{name}-debuginfo
diff --git a/gdb/gdb.nm b/gdb/gdb.nm
index adea165f8..06c49499f 100644
--- a/gdb/gdb.nm
+++ b/gdb/gdb.nm
@@ -4,7 +4,7 @@
###############################################################################
name = gdb
-version = 13.1
+version = 13.2
release = 1
groups = Development/Debuggers
@@ -24,6 +24,7 @@ sources = %{thisapp}.tar.xz
build
requires
bison
+ elfutils-devel
expat-devel
gmp-devel
mpfr-devel
@@ -58,6 +59,7 @@ build
--with-expat \
--with-python=%{python3} \
--with-lzma \
+ --with-debuginfod \
--without-libexpat-prefix \
%{DISTRO_MACHINE}
hooks/post-receive
--
IPFire 3.x development tree
reply other threads:[~2023-10-08 16:14 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=4S2Dvg07lJz2xg8@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