Sender: tim AT riker DOT skynet DOT be Message-ID: <3B5D8290.59ABA137@falconsoft.be> Date: Tue, 24 Jul 2001 16:13:36 +0200 From: Tim Van Holder Organization: Anubex N.V. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.16-3 i686) X-Accept-Language: en, nl-BE, nl MIME-Version: 1.0 To: "Peter J. Farley III" , djgpp AT delorie DOT com Subject: Re: Which config.site should be used, bash or autoconf 2.50? References: <3b5b44b8 DOT 11468978 AT news DOT escape DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Reply-To: djgpp AT delorie DOT com "Peter J. Farley III" wrote: > > Hi all, > > I just got back to updating my djgpp installation for a new source > build (awka-0.7.5, to be precise), and dl'ed the latest bash (bsh204b) > and autoconf (acnf250b), and these two both have a file called > share/config.site. There is some overlap between the two, but which > one should be used? I will be needing autoconf to update the source > package to build under djgpp, but obviously bash has to work, too. Bash does not require config.site for proper operation; it just packages that file because it was mainly used to enable some special features of our bash that helped run configure scripts. You need autoconf 2.50's config.site in order to run configure scripts generated by _our_ autoconf 2.50 (the path-searching using execuatble extensions isn't in mainline autoconf yet). So basically, you will probably want autoconf 2.50's config.site in $DJDIR/share, but you will either need to regenerate all configure scripts you want to run using autoconf 2.50 (not always easy to do, as many 2.13 configure.in scripts rely on undocumented internal variables and/or macros that ceased to work in 2.50), or set TEST_FINDS_EXE=y first (otherwise, no programs will be found). Or you can rename either one (say, have config.site and confsite.213), and set CONFIG_SITE to point to the one you want to use. -- Tim Van Holder - Anubex N.V. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message was posted using plain text. I do not endorse any products or services that may be hyperlinked to this message.