From: Bernard Dautrevaux <Dautrevaux@microprocess.com>
To: "'Frank Ch. Eigler'" <fche@redhat.com>,
Bernard Dautrevaux <Dautrevaux@microprocess.com>
Cc: norbert.c.esser@philips.com, sid@sources.redhat.com
Subject: RE: Segmentation Fault sid&gdb
Date: Wed, 17 Jan 2001 00:37:00 -0000 [thread overview]
Message-ID: <17B78BDF120BD411B70100500422FC6309E1C9@IIS000> (raw)
> -----Original Message-----
> From: Frank Ch. Eigler [ mailto:fche@redhat.com ]
> Sent: Tuesday, January 16, 2001 10:08 PM
> To: Bernard Dautrevaux
> Cc: norbert.c.esser@philips.com; sid@sources.redhat.com
> Subject: Re: Segmentation Fault sid&gdb
>
>
<snipped>
>
> : (and is still the one delivered as latest release by a lot
> of people,
> : even at cygnus, er... redhat)
>
> Nah - AFAIK neither Cygnus nor Red Hat has released gcc 2.95.2.
>
I don't know on RedHat Linux, but cygnus deliver gcc-2.95.2-6 (that's the
sixth port of 2.95.2) on cygwin, and that's usually there that I get the
source code, as I need for a lot of tools to have them running under Win32
(using mingw32, not cygwin, but usually a lot of the port effort is already
done for cygwin).
Regards,
Bernard
--------------------------------------------
Bernard Dautrevaux
Microprocess Ingenierie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: dautrevaux@microprocess.com
b.dautrevaux@usa.net
--------------------------------------------
next reply other threads:[~2001-01-17 0:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-17 0:37 Bernard Dautrevaux [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-01-16 11:04 Bernard Dautrevaux
2001-01-16 13:09 ` Frank Ch. Eigler
2001-01-16 14:46 ` Ben Elliston
2001-01-16 6:38 norbert.c.esser
2001-01-16 9:55 ` Frank Ch. Eigler
2001-01-16 14:26 ` matthew green
2001-01-16 1:23 norbert.c.esser
2001-01-16 4:39 ` Frank Ch. Eigler
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=17B78BDF120BD411B70100500422FC6309E1C9@IIS000 \
--to=dautrevaux@microprocess.com \
--cc=fche@redhat.com \
--cc=norbert.c.esser@philips.com \
--cc=sid@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).