From: Josh McKinney <forming@home.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.4.10-pre5
Date: Sat, 8 Sep 2001 23:05:39 -0500 [thread overview]
Message-ID: <20010908230539.A4927@home.com> (raw)
In-Reply-To: <E15fhnT-0003np-00@the-village.bc.nu> <3B9A95C7.DDF81890@oracle.com>
In-Reply-To: <3B9A95C7.DDF81890@oracle.com>
Since I have gotten a decent amount of flame mail from my one-liner posted
yesterday, I am just curious. Has anyone really been able to successfully
compile their kernel with gcc-3*. I did once or twice long before it was
released, but it dies on the same error everytime. I posted it to the
GCC mailing list because it was an internal compiler error, but it went
unanswered, along with other reports of the same bug. Anyway, I just want
to see if someone really is able to use it as a reliable compiler.
Josh
On approximately Sun, Sep 09, 2001 at 12:03:51AM +0200, Alessandro Suardi wrote:
> Alan Cox wrote:
> >
> > > ferred-stack-boundary=2 -march=i586 -DMODULE -c -o rd.o rd.c
> > > > rd.c: In function `rd_ioctl':
> > > > rd.c:262: invalid type argument of `->'
> > > > rd.c: In function `rd_cleanup':
> > > > rd.c:375: too few arguments to function `blkdev_put'
> >
> > 2.4.10pre5 doesnt compile for rd. It looks like the same error I got when
> > I applied Al's patch to -ac (and thus took it back out)
>
> Just in case anybody wondered it doesn't compile with gcc-3.0.1 either.
>
> --alessandro
>
> "this is no time to get cute, it's a mad dog's promenade
> so walk tall, or baby don't walk at all"
> (Bruce Springsteen, 'New York City Serenade')
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Linux, the choice | Magic is always the best solution --
of a GNU generation -o) | especially reliable magic.
Kernel 2.4.9-ac1 /\ |
on a i586 _\_v |
|
next prev parent reply other threads:[~2001-09-09 4:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 5:12 2.4.10-pre5 Garst R. Reese
2001-09-08 6:14 ` 2.4.10-pre5 Kingsley Foreman
2001-09-08 6:46 ` 2.4.10-pre5 Josh McKinney
2001-09-08 8:19 ` 2.4.10-pre5 Nicholas Knight
2001-09-08 9:32 ` 2.4.10-pre5 Eyal Lebedinsky
2001-09-08 13:05 ` 2.4.10-pre5 Alan Cox
2001-09-08 22:03 ` 2.4.10-pre5 Alessandro Suardi
2001-09-09 4:05 ` Josh McKinney [this message]
2001-09-09 4:14 ` 2.4.10-pre5 Steven Walter
2001-09-09 11:48 ` 2.4.10-pre5 (and gcc-3) Ken Moffat
2001-09-09 21:22 ` compiling kernel with gcc-3 (was: 2.4.10-pre5) Alessandro Suardi
2001-09-08 10:36 ` 2.4.10-pre5 Peter Osterlund
2001-09-08 12:57 ` 2.4.10-pre5 Garst R. Reese
2001-09-09 5:30 ` 2.4.10-pre5/pre6 Garst R. Reese
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=20010908230539.A4927@home.com \
--to=forming@home.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