public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "th.r.klein at web dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/47836] Some Cross Compiler can't build target-libiberty or target-zlib Date: Sun, 27 Feb 2011 09:34:00 -0000 [thread overview] Message-ID: <bug-47836-4-8aGuFx5k0p@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47836-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47836 --- Comment #8 from th.r.klein at web dot de 2011-02-27 09:23:44 UTC --- Exactly this is the current problem, there is neither a working switch like --disable-target-zlib nor a working --disable-target-libiberty. (sorry if confusing you by using of "without" instead of "disable", but this was only an example.)
next prev parent reply other threads:[~2011-02-27 9:24 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-21 15:03 [Bug regression/47836] New: " th.r.klein at web dot de 2011-02-21 19:22 ` [Bug regression/47836] " pinskia at gcc dot gnu.org 2011-02-22 19:53 ` th.r.klein at web dot de 2011-02-22 22:57 ` pinskia at gcc dot gnu.org 2011-02-23 18:10 ` th.r.klein at web dot de 2011-02-23 20:45 ` pinskia at gcc dot gnu.org 2011-02-24 20:15 ` th.r.klein at web dot de 2011-02-26 15:36 ` rwild at gcc dot gnu.org 2011-02-27 9:34 ` th.r.klein at web dot de [this message] 2011-02-27 22:48 ` pinskia at gcc dot gnu.org 2011-02-28 20:25 ` th.r.klein at web dot de 2011-03-02 5:57 ` rwild at gcc dot gnu.org 2011-03-02 16:50 ` joseph at codesourcery dot com 2011-06-22 20:18 ` hp at gcc dot gnu.org 2011-06-22 21:33 ` hp at gcc dot gnu.org 2011-06-24 11:11 ` th.r.klein at web dot de 2011-06-27 20:58 ` hp at gcc dot gnu.org 2011-06-27 21:04 ` hp at gcc dot gnu.org 2011-10-07 4:26 ` fzvqedi at v dot mintemail.com 2012-02-02 8:18 ` 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-47836-4-8aGuFx5k0p@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).