linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J . A . Magallon" <jamagallon@able.es>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jakub@redhat.com, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	David <dllorens@lsi.uji.es>,
	linux-kernel@vger.kernel.org
Subject: Re: Posible bug in gcc
Date: Mon, 26 Feb 2001 22:03:06 +0100	[thread overview]
Message-ID: <20010226220306.A2403@werewolf.able.es> (raw)
In-Reply-To: <20010226123309.A16592@devserv.devel.redhat.com> <E14XRyY-0001gE-00@the-village.bc.nu>
In-Reply-To: <E14XRyY-0001gE-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Mon, Feb 26, 2001 at 19:02:19 +0100


On 02.26 Alan Cox wrote:
Also fails in gcc-2.96-0.38mdk (Mandrake Cooker):
rpm -q --changelog gcc
* Sat Feb 17 2001 Chmouel Boudjnah <chmouel@mandrakesoft.com> 2.96-0.38mdk

- exit 0 if [ $1 = 0 ] if we are in %postun (to don't screwd up the
  alternatives).

* Thu Feb 15 2001 David BAUDENS <baudens@mandrakesoft.com> 2.96-0.37mdk

- Fix build on PPC :)

* Thu Feb 15 2001 Chmouel Boudjnah <chmouel@mandrakesoft.com> 2.96-0.36mdk

- Break build on PPC ;).
- Red Hat patches, Jakub Jelinek (rel74) 5 new patches :

-- 
J.A. Magallon                                                      $> cd pub
mailto:jamagallon@able.es                                          $> more beer

Linux werewolf 2.4.2-ac4 #2 SMP Mon Feb 26 00:21:23 CET 2001 i686


  parent reply	other threads:[~2001-02-26 21:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 16:30 Posible bug in gcc David
2001-02-26 17:15 ` Alan Cox
2001-02-26 17:33   ` Jakub Jelinek
2001-02-26 18:02     ` Alan Cox
2001-02-26 18:02       ` Richard B. Johnson
2001-02-27 19:50         ` Ville Herva
2001-02-26 21:03       ` J . A . Magallon [this message]
2001-02-26 20:53     ` David Relson
2001-02-26 22:30 ` J . A . Magallon
2001-02-27 10:56   ` Erik Mouw

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=20010226220306.A2403@werewolf.able.es \
    --to=jamagallon@able.es \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dllorens@lsi.uji.es \
    --cc=jakub@redhat.com \
    --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 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 NNTP newsgroup(s).