From: Dirk Eddelbuettel <edd@debian.org>
To: Brian Gough <bjg@network-theory.co.uk>
Cc: gsl-discuss@sources.redhat.com
Subject: [forwarded message from Anders H. Abrahamsen]
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15378.24865.151675.344772@sonny.eddelbuettel.com> (raw)
Message-ID: <20011219132000.fvaiIM7rKAFhBBgaDE4omJx85TrZMIs4yVFVlmlA96w@z> (raw)
In-Reply-To: <15376.65449.53187.75608@debian>
"Brian" == Brian Gough <bjg@network-theory.co.uk> writes:
Brian> Any ideas?
Anders> I have tried both gcc 2.96 and gcc 3.1-0.10. For three days ago I
Anders> ran Rehat 7.1, now I've just upgraded to 7.2.
[...]
Anders> Anders H A writes: > When I run the tests (make check), it locks up
Anders> after this test: > > .. > PASS: gsl_sf_ellint_E_e(M_PI/3.0, 0.01,
Anders> mode, &r)m > > (All tests before PASSes.) >
You can assess success (or lack thereof) on various platform and compilers at
Debian's "Build Daemon Success/Failure" database. Goto
http://buildd.debian.org/build.php?arch=&pkg=gsl
to pull the logs for the gsl package. As the package build process calls
'make check', these logs are fairly long and detailed.
Among the platforms that compiled gsl-1.0 successfully (i.e. i386, ia64 [aka
"itanium"], alpha, arm, mips, mipsel, sparc), the ia64 port uses a gcc 2.96:
edd@caballero:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/ia64-linux/2.96/specs
gcc version 2.96 20000731 (Debian GNU/Linux IA64 experimental)
edd@caballero:~$ uname -a
Linux caballero 2.4.9-itanium-smp #1 SMP Wed Nov 21 13:44:54 MST 2001 ia64 unknown
Now, as everybody knows, what Red Hat calls "gcc 2.96" is probably not what
the rest of the world calls "gcc 2.96" so you might want to check for an
upgraded gcc toolchain there.
I can't think of a platform (other than hppa) that enforces
gcc-3.0. Unfortunately, hppa currently has toolchain issues so there is no
attempt beyond the failure of 0.9.4 back in October. I do have other packages
with issues on that platform.
Hope this helps,
Dirk (Debian maintainer for GSL)
--
Good judgment comes from experience; experience comes from bad judgment.
-- F. Brooks
next prev parent reply other threads:[~2001-12-19 13:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 forwarded message from Anders H. Abrahamsen Brian Gough
2001-12-04 13:11 ` Brian Gough
2001-12-19 13:20 ` Dirk Eddelbuettel [this message]
2001-12-04 13:11 ` [forwarded message from Anders H. Abrahamsen] Dirk Eddelbuettel
2001-12-19 13:20 ` Anders H A
2001-12-04 13:11 ` Anders H A
2001-12-19 13:20 ` Brian Gough
2001-12-04 13:36 ` Brian Gough
2001-12-19 13:20 ` Dirk Eddelbuettel
2001-12-19 13:20 ` forwarded message from Anders H. Abrahamsen Brian Gough
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=15378.24865.151675.344772@sonny.eddelbuettel.com \
--to=edd@debian.org \
--cc=bjg@network-theory.co.uk \
--cc=gsl-discuss@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).