From: "Luke A. Guest" <laguest@abyss2.demon.co.uk>
To: Laurent GUERBY <laurent@guerby.net>
Cc: GCC ML <gcc@gcc.gnu.org>
Subject: Re: Status of the GNAT Ada compiler
Date: Sat, 27 Nov 2004 01:15:00 -0000 [thread overview]
Message-ID: <1101517308.26196.58.camel@rogue.abyss2.demon.co.uk> (raw)
In-Reply-To: <1101516972.5935.73.camel@pc.site>
On Sat, 2004-11-27 at 00:56, Laurent GUERBY wrote:
> Hi Luke, in order to be able to help you web need
> some information:
>
> - what is your OS
> - what is your OS installed Ada compiler
> - what are you typing in exactly
> - how does it fail exactly
>
> I personaly use SuSE 9.1 on both x86 and x86_64 cpus,
> the distribution comes with packages gnat and gnat-runtime, if you
> install them from YaST then you can compile
> without any problem GCC 3.4.x and GCC from current CVS
> by following the GCC website instructions.
Linux rogue 2.6.8-gentoo-r7 #2 Mon Oct 11 00:13:25 BST 2004 i686 AMD
Athlon(TM) XP 2000+ AuthenticAMD GNU/Linux
I have an optional install of GNAT-3.15p which I use to build FSF GNAT.
../gcc-3.4.1/configure --prefix=/opt/gcc-3.4.1 --enable-languages=ada
--program-suffix=341 2>&1|tee log.config.txt
make BOOT_CFLAGS='-mtune=athlon-xp -O3 -pipe' CFLAGS='-O'
LIBCXXFLAGS='-g -O2 -fno-implicit-templates' bootstrap 2>&1|tee
log.make.txt
The last version I have that installed without any problems in 3.4.0.
I'm about to try the -rgcc-ss-3_4-20041126 branch.
Luke.
next prev parent reply other threads:[~2004-11-27 1:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 0:44 Luke A. Guest
2004-11-27 0:56 ` Andrew Pinski
2004-11-27 1:01 ` Luke A. Guest
2004-11-27 1:13 ` Laurent GUERBY
2004-11-27 1:15 ` Luke A. Guest [this message]
2004-11-27 1:41 ` Laurent GUERBY
2004-11-27 1:48 ` Luke A. Guest
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=1101517308.26196.58.camel@rogue.abyss2.demon.co.uk \
--to=laguest@abyss2.demon.co.uk \
--cc=gcc@gcc.gnu.org \
--cc=laurent@guerby.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 read-only IMAP folder(s) and NNTP newsgroup(s).