This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Advice ? autoconf-related bootstrap failure
- To: gcc-patches at gcc dot gnu dot org (gcc-patches at gcc dot gnu dot org)
- Subject: Advice ? autoconf-related bootstrap failure
- From: "Philippe De Muyter" <phdm at macqel dot be>
- Date: Thu, 4 May 2000 18:37:45 +0200 (CEST)
Bootstrapping gcc on m68k-motorola-sysv fails currently also with :
creating ./config.status
creating Makefile
sed: command garbled: s%@language_hooks@%%g
creating intl/Makefile
sed: command garbled: s%@language_hooks@%%g
creating po/Makefile.in
sed: command garbled: s%@language_hooks@%%g
creating fixinc/Makefile
sed: command garbled: s%@language_hooks@%%g
creating gccbug
sed: command garbled: s%@language_hooks@%%g
creating cp/Makefile
sed: command garbled: s%@language_hooks@%%g
creating f/Makefile
sed: command garbled: s%@language_hooks@%%g
creating java/Makefile
sed: command garbled: s%@language_hooks@%%g
The reason is that the native `sed' does not accept a command file bigger
than 4096 bytes. The protection given by autoconf fixing a limit of
90 lines is not enough here because of numerous long lines in the sed commands.
I could probably design an autoconf fix and submit it to the autoconf people,
but how can I be sure it will be used to generate the configure files in
gcc in a timely manner ?
Another way would be to patch directly the autoconf used for the gcc source
tree if there is one.
What's the best way to solve that problem ?
Thanks in advance
Philippe