From: Brian Gough <bjg@network-theory.co.uk>
To: "Santiago Calderon" <sacate@jazzfutboleros.com>
Cc: <gsl-discuss@sources.redhat.com>
Subject: Re: BORLAND C++ and GSL
Date: Wed, 19 Dec 2001 13:20:00 -0000 [thread overview]
Message-ID: <15362.52284.487515.682511@debian> (raw)
In-Reply-To: <000a01c176a2$870955c0$0be6a8c0@SACATE>
Santiago Calderon writes:
> 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
Hi,
That package is maintained by the GnuWin32 group, so I don't know much
about it, but I believe the DLL you want is in their file gsl-1.0-bin.zip.
regards
Brian Gough
WARNING: multiple messages have this Message-ID
From: Brian Gough <bjg@network-theory.co.uk>
To: "Santiago Calderon" <sacate@jazzfutboleros.com>
Cc: <gsl-discuss@sources.redhat.com>
Subject: Re: BORLAND C++ and GSL
Date: Sat, 17 Nov 2001 23:34:00 -0000 [thread overview]
Message-ID: <15362.52284.487515.682511@debian> (raw)
Message-ID: <20011117233400.BFtJn14bzVF6KWf2L6IzUIi51inP_Ho0iwSeu3Co2cM@z> (raw)
In-Reply-To: <000a01c176a2$870955c0$0be6a8c0@SACATE>
Santiago Calderon writes:
> 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
Hi,
That package is maintained by the GnuWin32 group, so I don't know much
about it, but I believe the DLL you want is in their file gsl-1.0-bin.zip.
regards
Brian Gough
next prev parent 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
2001-11-17 13:31 ` Santiago Calderon
2001-12-19 13:20 ` Santiago Calderon
2001-12-19 13:20 ` Brian Gough [this message]
2001-11-17 23:34 ` Brian Gough
2001-12-19 13:20 ` Santiago Calderon
2001-11-18 6:54 ` Santiago Calderon
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=15362.52284.487515.682511@debian \
--to=bjg@network-theory.co.uk \
--cc=gsl-discuss@sources.redhat.com \
--cc=sacate@jazzfutboleros.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).