From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] clapack libraries missing?: buildroot-2014.11
Date: Wed, 01 Apr 2015 23:07:42 +0200 [thread overview]
Message-ID: <551C5E1E.4090303@mind.be> (raw)
In-Reply-To: <8328b17ed1d642209ea7133d18709de1@exch13-mail05.win.slac.stanford.edu>
[Ernesto, any chance of configuring your mailer to do proper quoting?]
On 01/04/15 07:05, Williams Jr., Ernest L. wrote:
[snip]
> My code does not compile:
> clapack has types that are not defined :(
>
> What other header file defines, "integer, "complex", "doublereal", "logical" , etc ...?
>
> /* header file for clapack 3.2.1 */
>
> #ifndef __CLAPACK_H
> #define __CLAPACK_H
>
> /* Subroutine */ int caxpy_(integer *n, complex *ca, complex *cx, integer *
> incx, complex *cy, integer *incy);
>
>
>
> Looks like "f2c.h" is actually needed but was not installed.
Could you find out from upstream how to make sure that f2c gets installed as
well? Perhaps also ask them to include f2c.h from clapack.h.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2015-04-01 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 14:51 [Buildroot] clapack libraries missing?: buildroot-2014.11 Ernest Williams
2015-03-31 20:06 ` Arnout Vandecappelle
2015-04-01 0:13 ` Williams
2015-04-01 5:05 ` Williams
2015-04-01 21:07 ` Arnout Vandecappelle [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-30 5:47 Williams
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=551C5E1E.4090303@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.