Message-ID: From: "Andris Pavenis" To: "Laurynas Biveinis" Date: Sat, 10 Apr 1999 14:29:33 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: Help - failed building egcs libraries CC: djgpp-workers AT delorie DOT com In-reply-to: <001401be8342$91fcda20$59003bd4@default> X-mailer: Pegasus Mail for Win32 (v3.02b14) 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 On 10 Apr 99, at 13:08, Laurynas Biveinis wrote: > >gcc-2.8.1 is no more used to build egcs-1.1.2 libraries (direcory > >gnu/egcs-1.12/libs). You should build compiler at first (./djmake.sh in > >gnu/egcs-1.12/gcc/build.djg) and NOT remove it as the result of this build > >is used to build libraries. The fragment You sent includes path to > > Yes, I built and installed compiler before. BTW, about what "manual changes" > after "installing into temporary directory" is talking readme.DJGPP? > It's simply renaming or moving some files after './djmake.sh install'. I had some additional scripts for that I unfortunatelly didn't put into source archive. When I built egcs-1.1.2 I simply run one .BAT file (DOS batch file as I cannot run bash for too long time due to M$ bugs in Win9X) and as result I'm getting binary zip archives where there is no more need to edit anything. > >compiler that should be used to build libraries. If the problem is > >different browse file config.log to see more details (simply I cannot > >guess all possible problems) > > It seems I have found the problem - bug, actually. Somewhere in that > configuration - building files (I don't know where, because I don't > understand > anything about *.sh files) is hardcoded DJGPP directory /djgpp instead of > %DJDIR%: library build failed when I tried to do it in c:\programming\djgpp > and succeeded in c:\djgpp. In both cases compiler is looked in /djgpp/gnu/ > egcs-1.12/gcc/build.djg/ I would provide you with patches - if I understand > about that files. Unfortunately, I do not. > Did You run ./djconfig.sh in libs/build.djg? It sets absolute path to previously built compiler. Perhaps we should no more upload configured sources in such conditions and force to run ./djconfig.sh. Andris