I've seen this when trying to build on my iBook - there's a problem with
the script using an unexpanded macro on a file using sed.
I hacked configure.in to work around it:
Note the use of the word 'hacked'. The problem seems to be due to
differences between gGNU sed and BSD sed.
On Sun, 9 Feb 2003, Bernhard Held wrote:
> > Well I'm trying to solve some problems that appear to happen when
> > compiling sdcc using Mac OSX version (10).2. The compile farm at sf
> > still uses 10.1 and the new system appears to have broken something.
> > So far I've concluded that when doing ./configure the Makefile in
> > /sdcc/support/cpp2/ is empty. Using 10.1 at the cf this appears not to
> > be the case.
> > So what I would like to know what is the difference between
> > /support/cpp and /support/cpp2? Does it have a special task?
> In support/cpp was version 2.95.x. Then we migrated to cpp 3.1, and a new
> directory in parallel to the old one was needed: support/cpp2 was created.
> After the migration the old cpp was deleted in CVS.
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> sdcc-devel mailing list