public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Indu Bhagat <ibhagat@sourceware.org> To: bfd-cvs@sourceware.org, gdb-cvs@sourceware.org Subject: [binutils-gdb] src-release.sh: Add libsframe Date: Tue, 15 Nov 2022 23:57:57 +0000 (GMT) [thread overview] Message-ID: <20221115235757.5EA513948805@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=e619dddb3a45780ae66d762756882a3b896b617d commit e619dddb3a45780ae66d762756882a3b896b617d Author: Indu Bhagat <indu.bhagat@oracle.com> Date: Tue Nov 15 15:07:13 2022 -0800 src-release.sh: Add libsframe Add libsframe to the list of top level directories that will be included in a release. ChangeLog: * src-release.sh: Add libsframe Diff: --- src-release.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src-release.sh b/src-release.sh index 76c355a583c..050a8eb958d 100755 --- a/src-release.sh +++ b/src-release.sh @@ -94,7 +94,7 @@ do_proto_toplev() # built in the gold dir. The disables speed the build a little. enables= disables= - for dir in binutils gas gdb gold gprof gprofng ld libctf libdecnumber readline sim; do + for dir in binutils gas gdb gold gprof gprofng libsframe ld libctf libdecnumber readline sim; do case " $tool $support_files " in *" $dir "*) enables="$enables --enable-$dir" ;; *) disables="$disables --disable-$dir" ;; @@ -304,7 +304,7 @@ gdb_tar_compress() } # The FSF "binutils" release includes gprof and ld. -BINUTILS_SUPPORT_DIRS="bfd gas include libiberty libctf opcodes ld elfcpp gold gprof gprofng intl setup.com makefile.vms cpu zlib" +BINUTILS_SUPPORT_DIRS="libsframe bfd gas include libiberty libctf opcodes ld elfcpp gold gprof gprofng intl setup.com makefile.vms cpu zlib" binutils_release() { compressors=$1
reply other threads:[~2022-11-15 23:57 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=20221115235757.5EA513948805@sourceware.org \ --to=ibhagat@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: linkBe 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).