From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: News Admin <news@nimloth.ics.muni.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: No Subject
Date: 21 Feb 2003 15:01:46 +0000 [thread overview]
Message-ID: <1045839704.5275.41.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <200302211343.h1LDhTM13523@nimloth.ics.muni.cz>
On Fri, 2003-02-21 at 13:43, News Admin wrote:
> $ gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-linux/3.2.3/specs
> Configured with: ../src/configure -v
> --enable-languages=c,c++,java,f77,proto,pascal,objc,ada --prefix=/usr
> --mandir=/usr/share/man --infodir=/usr/share/info
> --with-gxx-include-dir=/usr/include/c++/3.2 --enable-shared
> --with-system-zlib --enable-nls --without-included-gettext
> --enable-__cxa_atexit --enable-clocale=gnu --enable-java-gc=boehm
> --enable-objc-gc i386-linux
> Thread model: posix
> gcc version 3.2.3 20030210 (Debian prerelease)
How about using a released gcc compiler not a snapshot. gcc 3.2.1
and 3.2.2 appear to work fine. According to the FSF there is no
gcc 3.2.3 yet, so it isn't suprising a snapshot would have bugs
next prev parent reply other threads:[~2003-02-21 13:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-21 13:43 News Admin
2003-02-21 15:01 ` Alan Cox [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-08-30 5:02 No subject auto595907
2010-08-23 14:32 auto595907
2004-12-14 16:49 Andi Kleen
2004-12-15 23:50 ` No Subject Alan Cox
2004-07-16 16:54 Hermann Gottschalk
2004-07-16 16:59 ` No Subject Jesse Stockall
2004-02-22 17:51 redzic fadil
2004-02-22 20:54 ` No Subject Ludootje
2002-08-05 13:08 Christos Kartsaklis
2002-08-05 14:53 ` No Subject Alan Cox
2002-08-03 19:26 Pawel Kot
2002-08-03 21:45 ` No Subject Alan Cox
2002-08-03 21:58 ` Bartlomiej Zolnierkiewicz
2002-08-03 22:16 ` Bartlomiej Zolnierkiewicz
2002-08-03 23:38 ` Alan Cox
2002-08-03 22:53 ` Bartlomiej Zolnierkiewicz
2002-08-04 13:28 ` Henning P. Schmiedehausen
2002-08-04 15:40 ` Daniela Engert
2002-08-03 23:27 ` Petr Vandrovec
2001-08-24 22:16 abraxas2
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=1045839704.5275.41.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=news@nimloth.ics.muni.cz \
/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
all inboxes | Powered by JetHome®