From: Hans-Peter Nilsson <hp@sourceware.org>
To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org
Subject: [binutils-gdb] src-release.sh (SIM_SUPPORT_DIRS): Add libsframe, libctf/swap.h and gnulib
Date: Wed, 6 Sep 2023 02:15:57 +0000 (GMT) [thread overview]
Message-ID: <20230906021557.814F63858D28@sourceware.org> (raw)
https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=83066cb9c7dc2d16adf22649251392d04a7c8d83
commit 83066cb9c7dc2d16adf22649251392d04a7c8d83
Author: Hans-Peter Nilsson <hp@axis.com>
Date: Tue Sep 5 16:56:51 2023 +0200
src-release.sh (SIM_SUPPORT_DIRS): Add libsframe, libctf/swap.h and gnulib
Without this, a simulator build breaks when building from a tarball
made by "./src-release.sh -b sim", when building e.g. bfd and
libsframe. See also previous similar commits for GDB_SUPPORT_DIRS.
The libctf library does not needed to be built, but building
libsframe requires libctf/swap.h, with no dependencies on built or
configured contents. Do as for the single gdb files and include
explicitly only that file.
Diff:
---
src-release.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src-release.sh b/src-release.sh
index c974ea05473..465aee4ed2b 100755
--- a/src-release.sh
+++ b/src-release.sh
@@ -332,7 +332,7 @@ gdb_release()
}
# Corresponding to the CVS "sim" module.
-SIM_SUPPORT_DIRS="bfd opcodes libiberty include intl gdb/version.in gdb/common/create-version.sh makefile.vms zlib"
+SIM_SUPPORT_DIRS="libsframe bfd opcodes libiberty libctf/swap.h include intl gdb/version.in gdb/common/create-version.sh makefile.vms zlib gnulib"
sim_release()
{
compressors=$1
reply other threads:[~2023-09-06 2:15 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=20230906021557.814F63858D28@sourceware.org \
--to=hp@sourceware.org \
--cc=bfd-cvs@sourceware.org \
--cc=gdb-cvs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).