Message-Id: <199907201632.QAA43352@out4.ibm.net> From: "Mark E." To: djgpp-workers AT delorie DOT com Date: Tue, 20 Jul 1999 12:32:48 -0400 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: configuring CVS binutils In-Reply-To: X-mailer: Pegasus Mail for Win32 (v3.11) Reply-To: djgpp-workers AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > > echo "Changing y.tab to y_tab ... " > > Isn't it better to patch the configure script itself so that it would > perform these transformations? The solution isn't meant to be permanent. A better solution I'm working on is to get the macro I came up with that detects the yacc output root into either Autoconf and Automake. The Autoconf maintainer won't accept it, despite the fact that Autoconf has AC_DECL_YYTEXT which has code to detect the lex output root which my macro would complement nicely. The Automake maintainer is willing to accept the macro, and since Binutils uses Automake, there is a good chance the problem will be permanently fixed. Thanks for the other suggestions. However, some of the files are not in Binutils from CVS (aka Binutils 2.9.5): > You can patch the configure script with a simple Sed script, like > this: Two files of these aren't present in Binutils 2.9.5, probably because of the switch to Automake: > s,Makefile\\.in\\.in,Makefile.in-in,g\ > s,y\\.tab\\.in,y_tab.in,g > And while at that, I have two comments about Binutils 2.9.1: > > - The top-level configure script searches for the shell, but only > for the win32 environment. Won't it be a good diea to make it do > that for DJGPP as well? I think it's a good idea, especially for those sticking with Bash 1.147. The default is /bin/sh if CONFIG_SHELL isn't set, which means those with Bash 1.147 lose if they don't have a /bin directory. Bash 2.03 has the /bin magic, so it doesn't really need the help. > > - What do people think about enabling more targets in the DJGPP > build? It seems that having support for ELF and PE cannot > possibly hurt anything, and might be useful for using/analyzing > object files created by Linux/Cygwin/Mingw32. Binutils 2.9.5 has a 'readelf' for reading ELF files, but not an equivalent 'readpe' for reading PE files. Which means we'll be able to read ELF files in the next release without having to enable it as target. As for including PE as a target, I would want to know how much bigger the binutils binaries would be before I can offer a comment. Mark --- Mark Elbrecht, snowball3 AT bigfoot DOT com http://snowball.frogspace.net/