From: Alan Jackson <ajackson@shell.com>
To: Brian Gough <bjg@network-theory.co.uk>
Cc: gsl-discuss@sources.redhat.com
Subject: Re: 1.2 release candidate
Date: Tue, 02 Jul 2002 09:56:00 -0000 [thread overview]
Message-ID: <20020702115301.0b152c87.ajackson@shell.com> (raw)
Message-ID: <20020702095600.oIOQZzZZmXRRblZbC3hSn4gkb-RKVZ99qLOQXWOtAfI@z> (raw)
In-Reply-To: <15646.11784.301352.760739@debian>
On Sat, 29 Jun 2002 23:00:40 +0100 (BST)
Brian Gough <bjg@network-theory.co.uk> wrote:
> I've put a gsl-1.2 release candidate at
>
> http://www.network-theory.co.uk/gsl/gsl-1.1.1+.tar.gz
>
> Please try it out and let me know if it works. I have tested it on
> GNU/Linux with gcc-2.95.4.
>
Solaris 2.8, gcc version 2.95.2 19991024
make finished error free.
make check gave the following errors :
test_rotg.o: In function `test_rotg':
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:889: undefined reference to `LLC5'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:908: undefined reference to `LLC27'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1015: undefined reference to `LLC109'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1024: undefined reference to `LLC110'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1026: undefined reference to `LLC115'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1026: undefined reference to `LLC116'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1093: undefined reference to `LLC5'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1161: undefined reference to `LLC5'
/tmp/untar/gsl-1.1.1+/cblas/test_rotg.c:1194: undefined reference to `LLC115'
test_rotmg.o: In function `test_rotmg':
/tmp/untar/gsl-1.1.1+/cblas/test_rotmg.c:167: undefined reference to `LLC12'
collect2: ld returned 1 exit status
*** Error code 1
make: Fatal error: Command failed for target `test'
Current working directory /tmp/untar/gsl-1.1.1+/cblas
*** Error code 1
make: Fatal error: Command failed for target `check-am'
Current working directory /tmp/untar/gsl-1.1.1+/cblas
*** Error code 1
make: Fatal error: Command failed for target `check-recursive'
--
Alan K. Jackson - BTC - Quantitative AVO Team
Shell E&P Technology and Research
voice :(713)245-7355 fax :(713)245-7492 snail :Box 481,Houston,Tx 77001
UUCP: ...!{uupsi}!shell!ajackson INTERNET: ajackson@shell.com
next prev parent reply other threads:[~2002-07-02 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-31 9:55 Brian Gough
2002-12-31 9:55 ` Charles Yee
2002-07-02 10:03 ` Charles Yee
2002-12-31 9:55 ` Sergei Morozov
2002-07-02 10:47 ` Sergei Morozov
2002-12-31 9:55 ` Alan Jackson [this message]
2002-07-02 9:56 ` Alan Jackson
2002-12-31 9:55 ` Brian Gough
2002-07-02 15:01 ` Brian Gough
[not found] ` <20020630185808.GA345@voyager.perassi.home>
2002-12-31 9:55 ` Brian Gough
2002-07-01 15:24 ` Brian Gough
2002-12-31 9:55 ` Carlo Perassi
2002-07-02 3:02 ` Carlo Perassi
2002-12-31 9:55 ` Olivier Andrieu
2002-07-02 16:06 ` Olivier Andrieu
2002-12-31 9:55 ` Andrea Riciputi
2002-07-04 16:11 ` Andrea Riciputi
2002-12-31 9:55 ` Brian Gough
2002-07-07 15:27 ` Brian Gough
2002-12-31 9:55 ` Slaven Peles
2002-07-01 11:14 ` Slaven Peles
2002-12-31 9:55 ` Brian Gough
2002-07-01 15:24 ` Brian Gough
2002-12-31 9:55 ` Failed 1.2 release candidate - check Daniel Konkle
2002-07-01 15:14 ` Daniel Konkle
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=20020702115301.0b152c87.ajackson@shell.com \
--to=ajackson@shell.com \
--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).