Date: Tue, 4 Jan 2000 11:25:02 +0200 (IST) From: Eli Zaretskii X-Sender: eliz AT is To: michael green cc: djgpp AT delorie DOT com Subject: Re: Installing binaries In-Reply-To: <84roml$bqo$1@nntp9.atl.mindspring.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk [Please don't change the Subject of your messages, it makes it hard to track the thread as it evolves. Your original message had a different Subject line.] On Mon, 3 Jan 2000, michael green wrote: > Then I installed djpp 2.02 through zip picker and install.exe utility. > Where and how do I install all these files ? It doesn't matter where to install them, and it seems like you already succeeded in doing so. So this is not a problem anymore. > Installing the patch > gzip -d binutils-2.9.1-m68hc1x-19991128.diffs.gz > tar xvzf binutils-2.9.1.tar.gz > mv binutils-2.9.1 binutils-2.9.1-m68hc1x > patch -p1 < ../binutils-2.9.1-m68hc1x-19991128.diffs These instructions assume a Unix system. You are trying to do this on Windows, which introduces an additional level of complexity into the equation. So you should take the instructions with a grain of salt. Like I said: I strongly suggest to begin by building Binutils 2.9.1 for DJGPP without any changes. Only *after* you succeed in doing this, I recommend to apply binutils-2.9.1-m68hc1x-19991128.diffs with the Patch utility and reconfigure and rebuild Binutils for m86k. > sh ./configure --target=m6811-elf -program-prefix=m6811-elf- > So thats what I did. The error I got was something like configure: bin/sh: > [noent] and then something about a host. So I gave the commands sh > ./configure --host=i586 --target=m6811-elf --program=prefix=m6811-elf- > Then it looked good for a socond or so until I got message back that said > ****can not find config.sub . These are problems typical of running GNU configure scripts on DOS/Windows unaltered. They will not work without some minor tweaking. In my previous message, I suggested to look in the DJGPP archives where you can find scripts and instructions which will allow you to avoid all these problems. Did you look there, and did you try to use those scripts/instructions? > I had a copy of bash.exe in djgpp\bin so I > copied it to the binutils-2.9.1-m68hc1x directory as sh.exe because I > remembered reading something about this. I am not sure if this was correct. You are randomly poking around instead of following my advice. It won't work for you that way, believe me. I'm leaving the rest of the message below because it includes the URL where I recommended to look for scripts and instructions to build Binutils 2.9.1 with DJGPP. > Eli Zaretskii wrote in message ... > > > >On Sat, 1 Jan 2000, mg wrote: > > > >> I am trying to install files binutils-2_9_1-m68hc1x-19991128_diffs > and > >> binutils-2_9_1-tar. I am running a pentium processor with windows 98.Can > any > >> body give me any help installing? In the readme.djg > >> located in d:\djgpp\gnu\binutl-2.81 directory of the djgpp installation > it > >> references > >> under ---How to enable other object formats?--- section a copy of > >> config.bat and diffs.djg. Where do these files come from? > > > >Don't try to build Binutils 2.9.1 with instructions from Binutils > >2.8.1. Most of those instructions are not valid for the newer release > >of Binutils, because almost all the problems that those instructions > >are meant to handle are already taken care of in v2.9.1 by patches > >sent to the maintainer since v2.8.1 was released. > > > >You need a set of scripts and instructions to build Binutils 2.9.1. I > >think you can find these in the DJGPP mail archives at > >http://www.delorie.com/djgpp/mail-archives/. If you cannot find > >anything in the archives of the djgpp list, look in the archives of > >the djgpp-workers list. > > > >In any case, do NOT apply the m68hc patches before you succeed in > >building the unaltered distribution. Otherwise you will not know > >where did the problems come from. > > >