public inbox for src-cvs@sourceware.org help / color / mirror / Atom feed
From: amodra@sourceware.org To: binutils-cvs@sourceware.org, src-cvs@sourceware.org Subject: gdb and binutils branch master updated. b879806f2fdd2eca7092d7b854d6cbbbbbd0493b Date: Thu, 14 Aug 2014 04:23:00 -0000 [thread overview] Message-ID: <20140814042326.19890.qmail@sourceware.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 "gdb and binutils". The branch, master has been updated via b879806f2fdd2eca7092d7b854d6cbbbbbd0493b (commit) from 23ebe1a0bd86fdae83ca738cf75be67b58703756 (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 ----------------------------------------------------------------- https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=b879806f2fdd2eca7092d7b854d6cbbbbbd0493b commit b879806f2fdd2eca7092d7b854d6cbbbbbd0493b Author: Alan Modra <amodra@gmail.com> Date: Thu Aug 14 13:46:09 2014 +0930 configury changes to make ld plugin support controlled by --enable-plugins This also makes --enable-plugins default to on for hosts that can support plugins, so we have consistent lto toolchain support. The ACX_LARGEFILE moves aren't strictly necessary, but are harmless and will be necessary if plugin support is extended to more hosts via libtool's dlopen support. I started down that path then decided it was more work than I was interested in doing. (ACX_LARGEFILE invokes AC_PLUGINS.) config/ * plugins.m4: Test for dlfcn.h or windows.h here to set default for --enable-plugins. Report error if someone tries to enable plugins on a host we don't support. bfd/ * configure.ac: Delete redundant plugin related checks. * configure: Regenerate. binutils/ * configure.ac: Move ACX_LARGEFILE after LT_INIT. * config.in: Regenerate. * configure: Regenerate. gas/ * configure.ac: Move ACX_LARGEFILE after LT_INIT. * config.in: Regenerate. * configure: Regenerate. gprof/ * configure.ac: Move ACX_LARGEFILE after LT_INIT. * configure: Regenerate. * gconfig.in: Regenerate. ld/ * configure.ac: Move AC_PROG_CC and other macros earlier. Delete plugin checks now done in config/plugins.m4. * config.in: Regenerate. * configure: Regenerate. ----------------------------------------------------------------------- Summary of changes: bfd/ChangeLog | 5 + bfd/configure | 64 ++- bfd/configure.ac | 6 - binutils/ChangeLog | 6 + binutils/config.in | 3 + binutils/configure | 513 ++++++++------- binutils/configure.ac | 2 +- config/ChangeLog | 6 + config/plugins.m4 | 23 +- gas/ChangeLog | 6 + gas/config.in | 3 + gas/configure | 513 ++++++++------- gas/configure.ac | 2 +- gprof/ChangeLog | 6 + gprof/configure | 513 ++++++++------- gprof/configure.ac | 2 +- gprof/gconfig.in | 3 + ld/ChangeLog | 7 + ld/config.in | 9 - ld/configure | 1693 ++++++++++++++++++++++++------------------------- ld/configure.ac | 30 +- 21 files changed, 1768 insertions(+), 1647 deletions(-) hooks/post-receive -- gdb and binutils
reply other threads:[~2014-08-14 4:23 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=20140814042326.19890.qmail@sourceware.org \ --to=amodra@sourceware.org \ --cc=binutils-cvs@sourceware.org \ --cc=src-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).