From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: plotutils in djgpp
Date: 27 Jun 2001 09:50:31 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 26
Message-ID: <9hca97$2td$1@nets3.rz.RWTH-Aachen.DE>
References: <9hbok6$6k1$1 AT gemini DOT ntu DOT edu DOT tw>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 993635431 2989 137.226.32.75 (27 Jun 2001 09:50:31 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 27 Jun 2001 09:50:31 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

ywshei <ywshei AT tao DOT iam DOT ntu DOT edu DOT tw> wrote:

> The numbers of error occured if using the "sh configure".

Please try to be more specific. What were the precise error message
you got? Did you read the FAQ's tips about porting Unix packages?
The most important bits to remember:

* Always run configure scripts in DJGPP Bash, with the
  "TEST_FINDS_EXE" option active. You'll know that you didn't when 
  the configure script complains it can't find gcc or cc, or some other
  programs.

* After finding and fixing any problem, be sure to start from a clean
  situation: delete config.cache before re-running configure.

* In case of any error messages, capture the output to a file, and
  mail it.

* Don't assume that just because the programs compile and seem to run,
  you've dont a successful port of them to DOS --- there's a couple of
  traps and pitfalls to be aware of, which may go unnoticed even by the
  "make check" run, if one exists.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.