public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "GnuWin32" <gnuwin32@users.sourceforge.net>
To: "Brian Gough" <bjg@network-theory.co.uk>, <adam@kleczkowski.net>
Cc: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>,
	<gnuwin32-users@lists.sourceforge.net>
Subject: Re: [Gnuwin32-users] Re: Problem with Cygwin installation: FAQ?
Date: Tue, 20 Nov 2001 00:58:00 -0000	[thread overview]
Message-ID: <000801c17785$1035c6c0$2f2dfb3e@alpha> (raw)
Message-ID: <20011120005800.avkm3Vh_SFgmmMf_384SjTzvwBIFwjLsg9u0RPrKnYg@z> (raw)
In-Reply-To: <15363.60888.510919.626756@debian>

The Gnuwin32 port at http://gnuwin32.sourceforge.net/ is not a Cygwin port,
but a native MS-Windows port (it only depends on msvcrt.dll, which is
supplied on all MS-Windows systems). When running 'make check', all went
well, and there were no errors (see check.log in gsl-1.0-src.zip). The
Gnuwin32 port comes with import libraries for Mingw (GCC for MS-Windows),
MSVC and Borland C.
I'm not sure what you have been trying to do. Do you use Cygwin to compile
Gsl? Usually libraries or programs that compile well under Linux, also
compile without any change under Cygwin (configure, make, make check, make
install), and in this case I'm not sure how your problem can be solved. I
could try a compilation under Cygwin, but this will have to wait until next
weekend.
Or did you compile a program under Cygwin (i.e. with the Cygwin GCC
compiler), while linking to the Gnuwin32 dll (by means of the Gnuwin32
import library gsl.dll.a)? In that case, some things will certainly go
wrong, e.g. because Cygwin dll's use an entry point that is different from
MS-Windows dll's, and because Cygwin dll's depend on cygwin1.dll and so you
end up with a program that depends on both cygwin1.dll (because you compiled
it under Cygwin) and msvcrt.dll (because gsl.dll depends on msvcrt.dll). And
since cygwin1.dll and msvcrt.dll export the same functions, the program will
crash. If you quikview an executable, you will see on which dll's it depends
directly; so if your executable depends on cygwin1.dll, this probably is the
cause of your problem. To solve this, make sure that  Mingw-GCC comes first
in your path, before cygwin\bin, and that the GCC compiler won't look after
libraries in cygwin\lib.
If you still have problems after this, then send me some sample programs,
and I will try whether they compile and execute well on my own system
(Windows 98).

Kees Zeelenberg

----- Oorspronkelijk bericht -----
Van: "Brian Gough" <bjg@network-theory.co.uk>
Aan: <adam@kleczkowski.net>
CC: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>;
<gnuwin32-users@lists.sourceforge.net>
Verzonden: dinsdag 27 november 2001 20:47
Onderwerp: [Gnuwin32-users] Re: Problem with Cygwin installation: FAQ?


> Hi,
>
> The Cygwin version of GSL is a third-party package made the GnuWin32
> group. I don't know much about it I'm afraid -- I get the same error
> as you, and I can't figure it out either.  Sorry I can't offer any
> more help than that. I'm cc'ing this message to their mailing list to
> see if they can offer any suggestions.
>
> Their distribution does include the similar program "gsl-randist"
> which generates random numbers correctly, so it must be possible to
> get this to work -- perhaps it just requires some special Windows
> compiler option that I'm not familiar with.
>
> regards
> Brian Gough
>
>
>
> Adam Kleczkowski writes:
>  > I am trying to install/compile/run GSL v. 1.0 in the Cygwin environment
>  > (most up-to-date version), gcc 2.95.3-5. This has created a series of
>  > various problems and I have not been successful so far.
>  >
>  > Cygwin is installed in c:\cygwin
>  >
>  > GSL libraries, include files etc in c:\cygwin\usr\bin etc, binaries in
>  > c:\cygwin\bin
>  >
>  > Testing by using example programs from the manual (pages referring to
PDF
>  > format):
>  >
>  > Page 40:        poly.c (finding roots of the polynomial)
>  > Page 162:       random.c (testing a random number generator)
>  > Page 266:       vanderpol.c (Vanderpol oscilator)
>  >
>  > Using the mingw installation.
>  > All programs compile well, but:
>  > a. poly.c executes with no problem
>  > b. random.c and vanderpol.c crash giving the message:
>  >
>  >       0 [main] A 86798653 handle_exceptions: Exception:
>  > STATUS_ACCESS_VIOLATION
>  >    1647 [main] A 86798653 open_stackdumpfile: Dumping stack trace to
>  > RANDOM.EXE.stack
>  > dump
>  >
>  > I compile using simply
>  > gcc -o random.exe -c random.c -lgsl -lm
>  >
>  > I attach the programs. Any clues? In fact, I want to use random number
>  > generators and ODE solver in my project, and these two have not
compiled
>  > well...
>  > Thanks for a response in advance. If there is a reasonable FAQ that
covers
>  > the Cygwin installation, I would love to know where to find it. I tried
to
>  > compile GSL from the source under Cygwin (./configure, make, make
install)
>  > but run into horrific problems.
>  > --
>  > Adam Kleczkowski
>  > Dept. Plant Sciences, University of Cambridge
>  > e-mail: adam@kleczkowski.net
>  > http://mathbio.com/ (work) http://kleczkowski.net/ (private)
>
> _______________________________________________
> Gnuwin32-users mailing list
> Gnuwin32-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/gnuwin32-users
>

  parent reply	other threads:[~2001-11-27 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-19 13:20 Adam Kleczkowski
2001-11-19  0:05 ` Adam Kleczkowski
2001-12-19 13:20 ` Adam Kleczkowski
2001-12-19 13:20 ` Brian Gough
2001-11-19  9:00   ` Brian Gough
2001-12-19 13:20   ` Brian Gough
2001-12-19 13:20   ` GnuWin32 [this message]
2001-11-20  0:58     ` [Gnuwin32-users] " GnuWin32
2001-12-19 13:20     ` Adam Kleczkowski
2001-11-20 10:13       ` Adam Kleczkowski
2001-12-19 13:20 ` Gerrit P. Haase
2001-11-20  3:02   ` Gerrit P. Haase

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='000801c17785$1035c6c0$2f2dfb3e@alpha' \
    --to=gnuwin32@users.sourceforge.net \
    --cc=adam@kleczkowski.net \
    --cc=bjg@network-theory.co.uk \
    --cc=gnuwin32-users@lists.sourceforge.net \
    --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).