public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibolton at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/45174] Make fails in zlib
Date: Tue, 07 Sep 2010 14:49:00 -0000	[thread overview]
Message-ID: <20100907144411.24828.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45174-19456@http.gcc.gnu.org/bugzilla/>



------- Comment #22 from ibolton at gcc dot gnu dot org  2010-09-07 14:44 -------
(In reply to comment #21)
> Subject: Re:  Make fails in zlib
> 
> Hello;
>         Well I solved my problem, however the issue still remains. I installed
> the latest native binutils and gcc-4.5.1 on my linux installation. The
> script now works without any errors.
> 
>         However it appears that using the supplied binutils and compilers from
> Ubuntu 10.04 there is a problem creating the cross compilers. I do not
> know how or if I should proceed from here. It maybe there there is some
> subtle error in the bins supplied with Ubuntu.
> 
> Thank You,
> Donald Schlicht
> 

I've just read this thread and am now unsure as to whether there is a bug with
GCC or not.  It sounds like your initial troubles have gone away and now there
is a new problem.  Would it make sense to close this bug and raise a new bug to
cover the new issue?


-- 

ibolton at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45174


  parent reply	other threads:[~2010-09-07 14:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 22:20 [Bug bootstrap/45174] New: " dschlic1 at gmail dot com
2010-08-03 22:23 ` [Bug bootstrap/45174] " dschlic1 at gmail dot com
2010-08-03 22:25 ` pinskia at gcc dot gnu dot org
2010-08-03 22:28 ` pinskia at gcc dot gnu dot org
2010-08-03 23:00 ` dschlic1 at gmail dot com
2010-08-03 23:14 ` pinskia at gcc dot gnu dot org
2010-08-03 23:22 ` dschlic1 at gmail dot com
2010-08-04  0:42 ` pinskia at gcc dot gnu dot org
2010-08-04  0:43 ` pinskia at gcc dot gnu dot org
2010-08-05  0:27 ` dschlic1 at gmail dot com
2010-08-05 17:01 ` rwild at gcc dot gnu dot org
2010-08-06 14:35 ` dschlic1 at gmail dot com
2010-08-06 17:22 ` rwild at gcc dot gnu dot org
2010-08-07  0:18 ` dschlic1 at gmail dot com
2010-08-07 14:29 ` rwild at gcc dot gnu dot org
2010-08-08 19:19 ` dschlic1 at gmail dot com
2010-08-08 20:44 ` rwild at gcc dot gnu dot org
2010-08-09  0:42 ` dschlic1 at gmail dot com
2010-09-07 14:49 ` ibolton at gcc dot gnu dot org [this message]
2010-09-08 10:06 ` ibolton at gcc dot gnu dot org
2010-09-08 16:27 ` rwild at gcc dot gnu dot org
     [not found] <bug-45174-4@http.gcc.gnu.org/bugzilla/>
2010-10-02 14:52 ` rwild at gcc dot gnu.org
2011-01-18  1:46 ` John.Tytgat at aaug dot net
2011-01-18  6:29 ` John.Tytgat at aaug dot net
2011-01-18  8:30 ` rwild at gcc dot gnu.org
2011-04-12 19:36 ` dschlic1 at gmail dot com

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=20100907144411.24828.qmail@sourceware.org \
    --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: 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).