public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/47733] psignal (int, const? char*) in libiberty/strsignal.h Date: Wed, 22 Jun 2011 20:20:00 -0000 [thread overview] Message-ID: <bug-47733-4-JxjzrH7c0V@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47733-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47733 --- Comment #2 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-06-22 20:18:00 UTC --- Author: hp Date: Wed Jun 22 20:17:47 2011 New Revision: 175307 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=175307 Log: PR regression/47836 PR bootstrap/23656 PR other/47733 PR bootstrap/49247 * configure.ac (target_libraries): Remove target-libiberty. Remove case-statement setting skipdirs=target-libiberty for multiple targets. Remove checking target_configdirs and removing target-libiberty but keeping target-libgcc if otherwise empty. * Makefile.def (target_modules): Don't add libiberty. (dependencies): Remove all traces of target-libiberty. * configure, Makefile.in: Regenerate. (fixing PR annotations in the ChangeLog entry) Modified: trunk/ChangeLog
next prev parent reply other threads:[~2011-06-22 20:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-14 14:56 [Bug other/47733] New: " dilyan.palauzov at aegee dot org 2011-06-01 15:06 ` [Bug other/47733] " jan.smets@alcatel-lucent.com 2011-06-22 20:20 ` hp at gcc dot gnu.org [this message] 2011-06-22 21:31 ` hp at gcc dot gnu.org 2011-06-27 20:57 ` hp at gcc dot gnu.org 2011-06-27 21:06 ` hp at gcc dot gnu.org 2011-12-15 1:44 ` pinskia at gcc dot gnu.org 2011-12-15 1:46 ` pinskia at gcc dot gnu.org 2011-12-15 1:52 ` pinskia at gcc dot gnu.org 2012-01-15 19:24 ` pinskia at gcc dot gnu.org
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=bug-47733-4-JxjzrH7c0V@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).