Date:	Thu, 4 Mar 1999 15:14:50 +0100
From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Message-Id:	<199903041414.PAA29375@acp3bf.physik.rwth-aachen.de>
To:	apc AT transtech-design DOT com (Adrian Cox)
Cc:	djgpp AT delorie DOT com
Subject:	Re: linux to msdos cross compiler
Newsgroups:	comp.os.msdos.djgpp
Organization:	RWTH Aachen, III. physikalisches Institut B
X-Newsreader:	TIN [version 1.2 PL2]
Reply-To:	djgpp AT delorie DOT com

In article <36DD73A4 DOT 9A094239 AT transtech-design DOT com> you wrote:

> I'm working on SuSe Linux 6.0, and the first problem occurs in building
> binutils: everything appears to build correctly, but when I run the new
> ld command, I get the following error:

> $ ld/ld-new -V
> GNU ld version 2.9.1 (with BFD 2.9.1)
>   Supported emulations:
>    i386go32
> ld/ld-new:built in linker script:24: parse error

This may not be what's bugging you, but I remember having had problems
with the linker script building procedure as well, when I tried something
like that. 

It turned out that it was due to a change in behaviour of BASH version
2 versus version 1. There's a place in one of the configuration
scripts or makefiles (don't remember details) that only ever worked as
it currently is because of what appeared to be a bug in bash 1. The
bug is in handling of '{}' characters inside some advanced ${} string
replacement.

Using bash1 as /bin/sh solved that problem for me, IIRC.

--
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -