From: "Tim Van Holder" To: Subject: RE: Fileutils 4.0 port and ginstall Date: Sun, 4 Mar 2001 17:36:50 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 In-reply-to: <3AA25FC5.699C6BCA@phekda.freeserve.co.uk> Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > I expect the fix is mainly needed for automake and friends, so when they > build 'program' as main target, they can install 'program' and ginstall > will make sure this arrives as 'program.exe' if applicable. Then again, > AC_EXEEXT should really be added to configure.in when porting to DOS > (but then you hit the 'DJGPP maintainers shouldn't need > autoconf/automake' axiom again). > You might want the program to be executable from command.com too, once > installed. Unless it's program.(exe|com|bat), command.com won't find it. ??? Don't know what you mean here - that's what I said. Instead of having ginstall try to add an extension if appropriate, we should really just add AC_EXEEXT to configure.in and rerun autoconf & automake. That will cause the Makefile to have 'program$(exeext)' targets, which should be installed correctly. Then again, I believe gcc 3.0 will no longer append .exe, which breaks the exeext detection in autoconf :-( > I think 'depcomp' works OK with bash 2.04 though. Yup, it does. > is 95% done, I want to finish it, before I look at 4.1. I hope to look at > 4.1 before it's released, so I can get DJGPP changes into the actual > sources, rather than as a patch supplied with the DJGPP port, but time > will tell. Okidoki.