All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: gcc-3.3.1 breaks kernel
Date: Fri, 11 Jul 2003 21:02:32 -0400	[thread overview]
Message-ID: <20030712010232.GA7107@nevyn.them.org> (raw)
In-Reply-To: <20030712004301.GE2791@werewolf.able.es>

On Sat, Jul 12, 2003 at 02:43:01AM +0200, J.A. Magallon wrote:
> 
> On 07.12, Christian Kujau wrote:
> > J.A. Magallon wrote:
> > > Hi all...
> > > 
> > > Any brave soul there is using a prerelease of gcc-3.3.1 to build kernels ?
> > > (don't know if RawHide or SuSE beta or any other have that, apart from
> > > MandrakeCooker).
> > 
> > yes, 2.4.2x and 2.5.7x build properly with Debians gcc-3.3.1 here (x86).
> > 
> 
> Plz, can you tell me the exact version of gcc (date of snapshot or the
> like). My cooker gcc is:
> 
> - Update to 3.3-hammer branch as of 2003/07/03
> 
> Perhaps I can dig the gcc changelogs to look for something.
> 
> This is really strange...

Then ask your vendor about that, it's not the 3.3 branch.  Hammer is
maintained by (I think) SuSE people.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

  reply	other threads:[~2003-07-12  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8avk.6lp.3@gated-at.bofh.it>
2003-07-11 23:45 ` gcc-3.3.1 breaks kernel Christian Kujau
2003-07-12  0:43   ` J.A. Magallon
2003-07-12  1:02     ` Daniel Jacobowitz [this message]
2003-07-12  8:46     ` Wade
2003-07-14 13:14     ` Martin Schlemmer
2003-07-11 17:59 J.A. Magallon
2003-07-11 18:51 ` Jeff Garzik

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=20030712010232.GA7107@nevyn.them.org \
    --to=dan@debian.org \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.