Message-ID: <000f01c07c11$f7a8d8a0$70a5403e@gw>
From: "Les Newell" <les AT lnewell DOT screaming DOT net>
To: <djgpp AT delorie DOT com>
Subject: Re: DJGPP cross compiler
Date: Thu, 11 Jan 2001 21:02:30 -0000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Reply-To: djgpp AT delorie DOT com

I eventually found the problem so I thought I might as well let you know.
There are two versions of cpp. The one in $prefix/bin that gets called by
gcc and one in $prefix/lib/gcc-lib/h8300-hms/2.95.2 that gets called by the
one in $prefix/bin (why use the same filename??). When I tried compiling,
cpp couldn't find the other copy, ended up calling itself and self
destructed.
For some reason the first version of cpp is configured to look in
$prefix/lib/gcc-lib/h8300-hms/295.2 (note only one dot).
Unfortunately the second copy of cpp expects to find the libraries in
$prefix/lib/gcc-lib/h8300-hms/2.95.2/include!

Is this a bug in the make process, with an 8.3 filename conversion problem?
If so where should I report it?

At the moment I have kludged things by having two direcories, one called
295.2 and the other 2.95.2 It works but is not ideal

Thanks for your help,
Les


> Hi,
> I am trying to build a djgpp-x-h8300-hms compiler.
> I first built a Linux-x-djgpp compiler using the build-djgpp script and
> tested it with a simple hello world program. The program seemed to work
fine
> even if DJGPP and go32-v2 were not on the path.
> I then used the build-3way script to build the djgpp-x-h8300-hms compiler
> and ended up with the appropriate libraries and a set of binaries, though
> only the following were .exes
> Cpp.exe
> h8300-hms-c++.exe
> h8300-hms-c++filt.exe
> h8300-hms-g++.exe
> h8300-hms-gcc.exe
>
>
> If I try to run h8300-hms-gcc on a simple program containing a for loop I
> get the following:
> Load error: no DOS memory
> cpp.exe: Internal compiler error: program cpp got fatal signal 105
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> cpp.exe: Internal compiler error: program cpp got fatal signal 1
> h8300-~4.exe: Internal compiler error: program cpp got fatal signal 1
>
> Attached is the output of using gcc with the -v option
>
> This seems to happen if I have DJGPP on the path or not. Does anyone know
> what I have done wrong?
>
> Thanks,
> Les
>
>
>
>