All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: Russell King <rmk@arm.linux.org.uk>, mythos <papadako@csd.uoc.gr>,
	linux-kernel@vger.kernel.org
Subject: Re: Can't compile 2.4.3 with agcc
Date: Tue, 24 Apr 2001 14:30:09 +0100	[thread overview]
Message-ID: <26559.988119009@redhat.com> (raw)
In-Reply-To: <200104241328.f3ODSFrn011684@pincoya.inf.utfsm.cl>
In-Reply-To: <200104241328.f3ODSFrn011684@pincoya.inf.utfsm.cl>


vonbrand@inf.utfsm.cl said:
>  These "broken and cryptic" checks have been done several times now.
> You could certainly add a note to this effect to the documentation on
> building the kernel.

> Building a known broken kernel just for the sake of "better error
> reporting" is dead wrong, IMO.

The fact that the error is reported in a cryptic fashion is a minor issue. 
The important point is that the check itself is broken and not guaranteed 
to work even with good compilers. 

--
dwmw2



      reply	other threads:[~2001-04-24 13:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-23 13:13 Can't compile 2.4.3 with agcc mythos
2001-04-23 14:48 ` Russell King
2001-04-23 15:27 ` Alan Cox
2001-04-23 15:52 ` David Woodhouse
2001-04-23 17:57   ` Ingo Oeser
2001-04-23 19:43   ` Alan Cox
2001-04-23 20:46     ` David Woodhouse
2001-04-23 21:03   ` Matan Ziv-Av
2001-04-23 21:16     ` David Woodhouse
2001-04-23 22:32       ` Andrzej Krzysztofowicz
2001-04-23 22:54         ` David Woodhouse
2001-04-24  8:53           ` Russell King
2001-04-24 12:37           ` David Woodhouse
2001-04-23 22:25   ` Horst von Brand
2001-04-23 22:35     ` David Woodhouse
2001-04-24 13:28       ` Horst von Brand
2001-04-24 13:30         ` David Woodhouse [this message]

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=26559.988119009@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=papadako@csd.uoc.gr \
    --cc=rmk@arm.linux.org.uk \
    --cc=vonbrand@inf.utfsm.cl \
    /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.