X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f X-Received: by 10.182.24.9 with SMTP id q9mr15597211obf.13.1443373845134; Sun, 27 Sep 2015 10:10:45 -0700 (PDT) X-Received: by 10.182.116.165 with SMTP id jx5mr65546obb.27.1443373845076; Sun, 27 Sep 2015 10:10:45 -0700 (PDT) Newsgroups: comp.os.msdos.djgpp Date: Sun, 27 Sep 2015 10:10:44 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse AT google DOT com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=46.5.89.169; posting-account=OsAajgoAAADdKJnkJkmhzqP0jo6I_P_0 NNTP-Posting-Host: 46.5.89.169 References: <5607D4C3 DOT 4040800 AT gmx DOT de> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <46687d69-e0fb-4bfb-8125-a2c5380e85cb@googlegroups.com> Subject: Re: djgpp to Linux ARM cross binutils From: "Juan Manuel Guerrero (juan DOT guerrero AT gmx DOT de) [via djgpp AT delorie DOT com]" Injection-Date: Sun, 27 Sep 2015 17:10:45 +0000 Content-Type: text/plain; charset=ISO-8859-1 Bytes: 3114 Lines: 40 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t8RHU2mJ005754 Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sunday, September 27, 2015 at 3:21:26 PM UTC+2, Wiktor S. wrote: > c:/dj/gnu/binutils-2.25.1/binutils/configure: line 9052: unexpected EOF > while lo > oking for matching `'' > c:/dj/gnu/binutils-2.25.1/binutils/configure: line 9053: syntax error: > unexpecte > d end of file > Makefile:3447: recipe for target 'configure-binutils' failed > make.exe[1]: *** [configure-binutils] Error 1 > make.exe[1]: Leaving directory 'c:/dj/gnu/binutils-2.25.1/djgpp' > Makefile:845: recipe for target 'all' failed > make.exe: *** [all] Error 2 > > Why is that? > Is it normal that make tries to configure something, when build.sh had > already been run? Yes, because binutils uses the cygnus build system. It is not DJGPP specific. In this system almost every directory has its own configure script that must be run to create the required makefile. In the Autoconf/Automake build system usually there is only a configure script in the top source directory that configures and creates all makefiles in the source tree. The DJGPP specific build.sh makes DJGPP specific changes to all configure scripts, then it runs the configure script in the top source directory creating the makefile. If this is successful, build.sh starts makefile and this makefile goes recursively through the source tree running first the configure script to create the makefile for that directory and then running the produced makefile. This is all cygnus specific and is not related to the DJGPP port. The top source directory configure scripts creates the top source directory makefile, then this makefile is executed and goes recursively through the tree executing first the configure script that creates the makefile and then executing the makefile. Regards, Juan M. Guerrero