public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Santiago Calderon" <sacate@jazzfutboleros.com>
To: <gsl-discuss@sources.redhat.com>
Subject: BORLAND C++ and GSL
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <000a01c176a2$870955c0$0be6a8c0@SACATE> (raw)
Message-ID: <20011219132000.c3ZcSjpwpMJkzb77Hr_sY_qdQLo_0jtNQSNlRt5TpGc@z> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Hello everobody
 
I have tried to use the new gsl1.0 version with c++ Borland 
under windows'98 using the static libraries libgsl-bcc.lib and 
libgslcblas-bcc.lib. Anything seems to work fine during the compilation, 
but when I trie to run the program it gives me an error 
because it do not find the libgsl.dll library. In the zip file I downloaded it 
is a file called libgsl.dll.a, I have try to rename it to 
libgsl.dll as it is used in windows but the program now says that the libgsl.dll 
is corrupted.
 
 It seems as if the *-bcc.lib for Borland were import 
libraries and not static libraries because they need the dll 
libraries to work. The *.dll of the download have the 
*.dll.a termination and I am not able of using them under windows even changing 
the name to *.dll
 
 Please help
Santiago Calderon

             reply	other threads:[~2001-12-19 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Santiago Calderon [this message]
2001-11-17 13:31 ` Santiago Calderon
2001-12-19 13:20 ` Santiago Calderon
2001-12-19 13:20 ` Brian Gough
2001-11-17 23:34   ` Brian Gough
2001-12-19 13:20   ` Santiago Calderon
2001-11-18  6:54     ` Santiago Calderon
  -- strict thread matches above, loose matches on Subject: below --
2001-12-19 13:20 GnuWin32
2001-11-21 21:06 ` GnuWin32

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='000a01c176a2$870955c0$0be6a8c0@SACATE' \
    --to=sacate@jazzfutboleros.com \
    --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).