Mail Archives: djgpp/2004/09/16/03:25:54
On Wednesday 15 September 2004 14:34, you wrote:
> With a new computer running Windows XP I installed the files from
> Andrew Cotrell's page on clio.
> <http://clio.rice.edu/djgpp/win2k/main_204.htm>
> Following his directions, I had no trouble bringing DJGPP up.
> (Great work, Andrew)
Some notes:
bash205b[bs].zip from clio.rice.edu has one critical bug, which prevents
running rather many configure scripts (when PATH_SEPARATOR=:). See
my recent post to djgpp-workers mailing list for more details:
http://www.delorie.com/djgpp/mail-archives/browse.cgi?p=djgpp-workers/2004/09/06/09:13:35
Also there is one problem in config.site which appears when environment
variable PATH_SEPARATOR is not set at all.
>
> m4-14s compiled and installed just fine. (Thanks! Eli)
>
> sed412s built, tested and installed. (No problems here, Juan Manuel)
>
> GNU autoconf 2.57, release 3 (v2gnu/acnf257b.zip).
> acn257s.zip built and installed with no problems. (Thanks! Richard)
>
> The build from amak176s.zip failed nine tests:
> conff.test pr9.test subcond2.test
> insthook.test pr87.test subcond3.test
> lex3.txt python3.test subpkg.test
I don't remember recent version of autoconf and automake which passes
all tests for DJGPP target. autoconf-2.59 and automake-1.9.1 has
even more failures, but seems to work for me otherwise.
> Should I use this failed automake, Richard?
>
> . GNU binutils 2.13 (v2gnu/bnu213b.zip);
> bnu215s.zip built and installed binaries.
> There were warnings. The one recurring one, and most easily
> corrected, was about the use of an old (2.13) version of
> autoconfig. I was running build.sh and mv politely informed
> me that when moving a string of files the last one must be
> a directory. I'll look into that, and how you got upx to
> work. Since I deleted -i386-pc-msdosdjgpp from djconfig.sh
I have practically not used UPX for some time.
upx-1.2.X had problems with DJGPP binaries generated by recent
versions of GCC and binutils. Really the failure is if one decompress UPX
compressed file (it does not work any more). Therefore last versions gives up
on DJGPP binaries. New beta versions of UPX (eg. upx-1.9.2 works, but it's
not tested so much, so be carefull)
> configure told me the processor was -i786-pc-msdosdjgpp.
> This was news to me since I thought I had a x86 Family 15
> Model 3 Stepping 3 GenuineIntel ~2532 Mhz.
>
> I'd like to rebuild configure, Andris, if you could walk me
> through the steps.
It may depend from package. In some cases aclocal, automake
mey need some command line options. Usually they should work
without
> Do I go down to maintainer-clean?
Normally not necessary
Andris
- Raw text -