linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Samuelson <peter@cadcamlab.org>
To: Richard Henderson <rth@twiddle.net>,
	Keith Owens <kaos@ocs.com.au>, Pavel Machek <pavel@suse.cz>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] kernel/module.c (plus gratuitous rant)
Date: Mon, 30 Oct 2000 05:05:43 -0600	[thread overview]
Message-ID: <20001030050543.A9175@wire.cadcamlab.org> (raw)
In-Reply-To: <20001027194513.A1060@bug.ucw.cz> <4309.972694843@ocs3.ocs-net> <20001028131558.A17429@uni-mainz.de> <20001028172700.A13608@twiddle.net> <20001029160916.B12250@uni-mainz.de>
In-Reply-To: <20001029160916.B12250@uni-mainz.de>; from dominik.kubla@uni-mainz.de on Sun, Oct 29, 2000 at 04:09:16PM +0100


  [rth]
> > Which was a nice idea, but it doesn't actually work.  Changes
> > in spec file format between versions makes this fall over.

[Dominik Kubla]
> Wow. So much for reading the manual... well, that's considered
> cheating anyway, isn't it?

I know this was true at one time -- egcs couldn't read 2.7 spec files,
or something like that.  (I remember at the time thinking "so much for
the great and glorious '-V' theory".)

But I think it's since been fixed:

  $ gcc -v
  Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.2/specs
  gcc version 2.95.2 20000220 (Debian GNU/Linux)
  $ gcc -V2.7.2.3 -v
  Reading specs from /usr/lib/gcc-lib/i386-linux/2.7.2.3/specs
  gcc driver version 2.95.2 20000220 (Debian GNU/Linux) executing gcc version 2.7.2.3

Is there more subtle breakage?

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-30 11:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <39F5830E.7963A935@uow.edu.au>
     [not found] ` <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>
2000-10-27 17:45   ` [patch] kernel/module.c (plus gratuitous rant) Pavel Machek
2000-10-27 20:40     ` Jeff Garzik
2000-10-27 21:12       ` Alan Cox
2000-10-27 20:46     ` Alan Cox
2000-10-28  1:00     ` Keith Owens
2000-10-28 11:15       ` Dominik Kubla
2000-10-29  0:27         ` Richard Henderson
2000-10-29 15:09           ` Dominik Kubla
2000-10-30 11:05             ` Peter Samuelson [this message]
2000-10-30 18:50               ` Richard Henderson
2000-10-29 23:23       ` Rusty Russell
2000-10-30 11:08         ` Peter Samuelson
2000-10-30 11:19           ` Recommended compiler? - " Linux Kernel Developer
2000-10-30 11:58             ` Peter Samuelson
2000-10-30 13:49               ` Martin Dalecki
2000-10-30 20:50                 ` Horst von Brand
2000-10-30 22:02                   ` Jakub Jelinek
2000-10-31 10:27                   ` Martin Dalecki

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=20001030050543.A9175@wire.cadcamlab.org \
    --to=peter@cadcamlab.org \
    --cc=kaos@ocs.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=rth@twiddle.net \
    /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).