From: Nizar ROMDHANE <nizar.romdhane@st.com>
To: law@redhat.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc v2.96
Date: Mon, 12 Apr 2004 11:24:00 -0000 [thread overview]
Message-ID: <407A7D1F.5050909@st.com> (raw)
In-Reply-To: <200404081921.i38JLQdi015334@speedy.slc.redhat.com>
law@redhat.com wrote:
> In message <407547AB.6000306@st.com>, Nizar ROMDHANE writes:
> >Hi all,
> >
> >I'm trying to get the source code for gcc v2.96 (the one shipped with several
> > linux distributions)
> >but I can not find it on the website of gnu. Can anyone help me. I heard alco
> > about the existence of
> >a v2.95.4, is it true? I f yes where to download it?
> You will need to get it from your OS vendor. 2.96 in particular is not an
> FSF release -- it was a pre GCC 3.0 snapshot used by Red Hat for RHL 7.x
> and the sources can be found on your SRPM disks and/or Red Hat's FTP
> sites.
>
> jeff
>
>
>
>
Hi,
Thanks a lot for your help, but I can not find the source code under Redhat ftp site. Can you give
the complete path please?
Thanks a lot
Best regards
--
-----------------------------------------
Nizar ROMDHANE
System Level Design Engineer
SLD Team Leader - OCCS - CMG Design - CMG
STMicroelectronics Tunis
Cite Technologique des communications -
Elghazala - 2088 - Ariana - TUNISIA
phone:
+216 71 857 750 (office 131)
mobile: +216 97 431 708
fax:
+216 71 857 525
e-mail:
nizar.romdhane@st.com
nizar_romdane@yahoo.fr
web:
http://www.st.com
-----------------------------------------
next prev parent reply other threads:[~2004-04-12 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 4:57 Getting List of Static Libraries used in Executable Lalit Seth
2004-04-08 11:55 ` Eljay Love-Jensen
2004-04-08 13:12 ` gcc v2.96 Nizar ROMDHANE
2004-04-08 13:45 ` Eljay Love-Jensen
2004-04-08 17:37 ` llewelly
2004-04-08 19:21 ` law
2004-04-12 11:24 ` Nizar ROMDHANE [this message]
2004-04-12 11:56 ` Eljay Love-Jensen
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=407A7D1F.5050909@st.com \
--to=nizar.romdhane@st.com \
--cc=gcc-help@gcc.gnu.org \
--cc=law@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).