Message-ID: <005001c299a9$073c24a0$39f3cfcf@oemcomputer>
From: "Ed Manlove" <emanlove AT ieee DOT org>
To: <djgpp AT delorie DOT com>
Subject: Re: Expansion of "$srcdir" and '${DJDIR}' in gnu\binutl-2.121\build.djg\djconfig.sh
X-Mailer: Microsoft Outlook Express 5.00.2615.200
Date: Sun, 1 Dec 2002 21:15:45 -0500
X-Priority: 3
X-MSMail-Priority: Normal
X-Mimeole: Produced By Microsoft MimeOLE V5.00.2615.200
Reply-To: djgpp AT delorie DOT com

> > I an trying to
> > understand how the above terms are expanded by configure and the
difference
> > between the single quotes '' and the double quotes"".
>
> '${DJDIR}' in single quotes is not expanded by the shell, while in double
> quotes it _is_ expanded immediatly.

Eli,

Thanks for the explanation. In trying to build gcc 2.95.2 for the h8300 I
get an error (the first one, which of course brought others I stupidly
wasted time with) in the course of fixing headers.  The error is shown here

Fixing headers into c:/djgpp/gnu/gcc-2.952/build.djg/gcc/include for
h8300-hitachi-hms target
./fixinc.sh: cd: c:/djgpp/h8300-hitachi-hms/sys-include: No such file or
directory (ENOENT)

As I dug into why this was occurring I realized that adding
the -with-headers parameter should solve this.  But I was having issue with
the proper formatting of the directory location, hence my question.  I have
tried several variations which yet to have successfully built.  The most
interesting results in a COPIED file generated by fixheader located in
c:\djgpp\gnu\gcc-2.952\build.djg\$DJGPP\/h8300-hitachi-hms/sys-include (or
something close to this).  Cute but not right.

If you noted the almost cross pollination of the two configure scripts for
binutls and gcc (i.e. the use of the --srcdir="$srcdir" --prefix='${DJDIR}'
in my gcc configure script) my first attempts to use the djconfig.sh script
to build gcc failed.  Since I was almost immediately successful with the
binutls script I copied and slightly modified it to the point of the above
error.  I will back track and retry the original script and see what I can
do to bring it to the point I am now at, fix this error, and successfully
build gcc for the h8300!

Ed