From: Andris Pavenis <pavenis@latnet.lv>
To: gsl-discuss@sources.redhat.com
Subject: Re: [PATCH] Add missing $(EXEEXT)
Date: Tue, 27 Jul 2004 12:17:00 -0000 [thread overview]
Message-ID: <200407271517.51531.pavenis@latnet.lv> (raw)
In-Reply-To: <16646.13280.949064.263942@network-theory.co.uk>
On Tuesday 27 July 2004 13:52, Brian Gough wrote:
> Andris Pavenis writes:
> > There are missing $(EXEEXT) in Makefile.am files in subdirectories of
> > directory test. Attached patch fixes this problem.
> >
> > After that GSL-1.5 builds OK for i586-pc-msdosdjgpp. I didn't get any
> > testsuite failures.
>
> Thanks for the patch. What about other programs like gsl-histogram and
> gsl-randist that are in the build -- do they need $(EXEEXT) also?
Both gsl-histogram and gsl-randist were built and I didn't noticed problems
for i586-pc-msdoddjgpp (where EXEEXT=.exe)
So perhaps the patch is enough.
Andris
next prev parent reply other threads:[~2004-07-27 12:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-26 16:43 Andris Pavenis
2004-07-27 11:00 ` Brian Gough
2004-07-27 12:17 ` Andris Pavenis [this message]
2004-07-28 10:30 ` Brian Gough
2004-07-29 7:41 ` Andris Pavenis
2004-07-29 11:00 ` 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=200407271517.51531.pavenis@latnet.lv \
--to=pavenis@latnet.lv \
--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).