From: "GnuWin32" <gnuwin32@users.sourceforge.net>
To: "Gsl Discuss" <gsl-discuss@sources.redhat.com>, <rvc@ku.edu>
Subject: Re: How to compile GSL using DJGPP ?
Date: Wed, 21 Nov 2001 13:48:00 -0000 [thread overview]
Message-ID: <003601c17848$f43cfaa0$382dfb3e@alpha> (raw)
Message-ID: <20011121134800.aRtSh4zjm0eBbcH6gPJ1zF0fS6pveB46ILAo1JH6jg8@z> (raw)
Gsl should compile in the standard way using Djgpp-2 if Djgpp is installed
on an MS-Windows system; Djgpp can then handle long file names. Just run
configure and make. I'm not absolutely certain there will be no errors, but
they will probably be minor ones.
Under plain DOS, you might indeed run into trouble with the 8+3
filename-restriction; see the Djgpp FAQ on how to work around this.
Kees Zeelenberg
Vijay:
The reason that it doesn't appear on the supported platforms list is because
DOS
only supports 8.3 file names. But, GSL has some file names that are longer
than
31 characters. There are probably ways that you can get around this, but
nobody
has done it yet.
>Date: Wed, 07 Nov 2001 22:07:58 -0600
>From: "Vijaya C Ramasami (Vijay)" <rvc@ku.edu>
>MIME-Version: 1.0
>To: GSL Discuss <gsl-discuss@sources.redhat.com>
>Subject: How to compile GSL using DJGPP ?
>Content-Transfer-Encoding: 7bit
>
>Hi,
>
> I just downloaded GSL from sources.redhat.com. I am using a MS-DOS
>version of the GNU C++ compiler (called DJGPP). I don't know how to
>compile the source code using this version of gcc. MS-DOS does not
>appear on the list of compiled platforms.
>
>Please help..
>
>-Vijay.
Rodney Sparapani Medical College of Wisconsin
Sr. Biostatistician Patient Care & Outcomes Research (PCOR)
rsparapa@mcw.edu http://www.mcw.edu/pcor
Was 'Name That Tune' rigged? WWLD -- What Would Lombardi Do
next reply other threads:[~2001-11-28 20:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-19 13:20 GnuWin32 [this message]
2001-11-21 13:48 ` GnuWin32
2001-12-19 13:20 Rodney Sparapani
2001-12-19 13:20 Vijaya C Ramasami (Vijay)
2001-12-19 13:20 ` Brian Gough
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='003601c17848$f43cfaa0$382dfb3e@alpha' \
--to=gnuwin32@users.sourceforge.net \
--cc=gsl-discuss@sources.redhat.com \
--cc=rvc@ku.edu \
/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).