public inbox for gsl-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: "Adam Kleczkowski" <ak133@cus.cam.ac.uk>
Cc: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>, adam@kleczkowski.net
Subject: Re: Problem with Cygwin installation: FAQ?
Date: Wed, 19 Dec 2001 13:20:00 -0000	[thread overview]
Message-ID: <130270578311.20011128005136@familiehaase.de> (raw)
In-Reply-To: <NCBBIJNHCKHEPHMAPMMIAEHODCAA.ak133@cus.cam.ac.uk>

Hallo Adam,

Am 2001-11-27 um 13:33 schriebst du:

> 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

As Kees wrote, you cannot mix cygwin and mingw, if you compile *with*
cygwin1.dll then you do correct like above, if you have a dsl lib compiled
*with* mingw you need to add -mno-cygwin to your link line to get a native
windows binary.

gcc -mno-cygwin -o random.exe -c random.c -lgsl -l...

and you need to add the correct libs (I don't know them, Kees wrote about
dependencies msvcrt and so), libm, libg, libc are all the same as libcygwin.

Ciao,

Gerrit P. Haase                            mailto:gp@familiehaase.de
-- 
=^..^=

WARNING: multiple messages have this Message-ID
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: "Adam Kleczkowski" <ak133@cus.cam.ac.uk>
Cc: "Gsl-Discuss" <gsl-discuss@sources.redhat.com>, adam@kleczkowski.net
Subject: Re: Problem with Cygwin installation: FAQ?
Date: Tue, 20 Nov 2001 03:02:00 -0000	[thread overview]
Message-ID: <130270578311.20011128005136@familiehaase.de> (raw)
Message-ID: <20011120030200.K5-DjERIAB-PDawtMV8D-qPh3LMUbxi7E89q2e7faQQ@z> (raw)
In-Reply-To: <NCBBIJNHCKHEPHMAPMMIAEHODCAA.ak133@cus.cam.ac.uk>

Hallo Adam,

Am 2001-11-27 um 13:33 schriebst du:

> 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

As Kees wrote, you cannot mix cygwin and mingw, if you compile *with*
cygwin1.dll then you do correct like above, if you have a dsl lib compiled
*with* mingw you need to add -mno-cygwin to your link line to get a native
windows binary.

gcc -mno-cygwin -o random.exe -c random.c -lgsl -l...

and you need to add the correct libs (I don't know them, Kees wrote about
dependencies msvcrt and so), libm, libg, libc are all the same as libcygwin.

Ciao,

Gerrit P. Haase                            mailto:gp@familiehaase.de
-- 
=^..^=

  parent reply	other threads:[~2001-12-19 13:20 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 ` Brian Gough
2001-11-19  9:00   ` Brian Gough
2001-12-19 13:20   ` Brian Gough
2001-12-19 13:20   ` [Gnuwin32-users] " GnuWin32
2001-11-20  0:58     ` GnuWin32
2001-12-19 13:20     ` Adam Kleczkowski
2001-11-20 10:13       ` Adam Kleczkowski
2001-12-19 13:20 ` Adam Kleczkowski
2001-12-19 13:20 ` Gerrit P. Haase [this message]
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=130270578311.20011128005136@familiehaase.de \
    --to=gp@familiehaase.de \
    --cc=adam@kleczkowski.net \
    --cc=ak133@cus.cam.ac.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).