From: Jon Grimm <jgrimm2@us.ibm.com>
To: gcc@gcc.gnu.org
Subject: stale pooma src for testing gcc in 'POOMA build and test guide'?
Date: Fri, 01 Oct 2004 17:01:00 -0000 [thread overview]
Message-ID: <415D892D.5000901@us.ibm.com> (raw)
Hello,
This question may be a little lite for this list.. but it seems relevant to the docs/testing of gcc. If there's a better list to ask on, I'll move any discussion there.
Here goes anyway...
In the testing webpages, "POOMA build and test guide" at:
http://gcc.gnu.org/testing/testing-pooma.html
,there is a version of pooma provided:
ftp://gcc.gnu.org/pub/gcc/infrastructure/pooma-gcc.tar.gz
This version of pooma appears to be pooma-2.3.0.
However... is this version still relevant?? I ask, as the compile is (minimally) choking on gcc-3.4 and I see in the pooma code:
#if (defined(__MWERKS__) && __MWERKS__ >= 0x2301) || __GLIBCPP__ >= 20001129
typedef std::ios_base::fmtflags FmtFlags_t;
#else
typedef long FmtFlags_t;
#endif
BUT... __GLIBCPP__ was renamed __GLIBCXX__ in 3.4.0 timeframe, so that version check won't work as expected.
The current downloadable pooma source (2.4.0) has similar code too, but ... CVS sources look to have moved to actually do a 'configure' check, so may work.
Does anyway do any testing of their own with pooma + gcc-3.4 to verify it doesn't compile (may be better to ask on pooma-dev)?
If validated, maybe the docs should stop referencing pooma, or have updated sources, or at least mention that the bundled source may only work for testing older (pre-3.4 gccs)?
--
Jon Grimm <jgrimm2@us.ibm.com>
Lotus Notes: Jon Grimm/Austin/IBM@IBMUS
next reply other threads:[~2004-10-01 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 17:01 Jon Grimm [this message]
2004-10-03 6:59 ` Richard Guenther
2004-10-04 13:50 ` Jon Grimm
2004-10-05 11:52 ` Ben Elliston
2004-10-27 14:03 ` Gerald Pfeifer
2004-10-27 14:06 ` Richard Guenther
2004-10-27 15:22 ` Gerald Pfeifer
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=415D892D.5000901@us.ibm.com \
--to=jgrimm2@us.ibm.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).