Re: [Mingw-msys] Strangeness in diffutils build (gcc generating dependencies)

[Luke D. <cod...@ho...>]

Hi,

Since the dependency file generation uses 'sed' a lot, your problem is
probably the same as one already reported:

http://www.geocrawler.com/archives/3/18160/2002/3/0/8258345/

Luke Dunstan


----- Original Message -----
From: "Paul Moore" <gu...@mo...>
To: <min...@li...>
Sent: Tuesday, April 16, 2002 4:20 AM
Subject: [Mingw-msys] Strangeness in diffutils build (gcc generating
dependencies)


I'm getting some very annoying errors when trying to port/build
diffutils-2.8.1 with msys 1.06 (and mingw with the new mingw-runtime 2.0
beta) on Win2000 Pro.

To reproduce the problem, simply unpack the diffutils tarball somewhere.
Then do ./configure, then make, and then make a second time. The
*second* make fails, with an error

    .deps/mkstemp.Po:1: *** multiple target patterns.  Stop.

(The first make also fails - but this is a porting issue, which I'm
addressing...)

I believe that the cause of this is the way gcc is called by the
makefile. A sample of the call is

source='strftime.c' object='strftime.o' libtool=no \
depfile='.deps/strftime.Po' tmpdepfile='.deps/strftime.TPo' \
depmode=gcc /bin/sh ../config/depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c \
`test -f strftime.c || echo './'`strftime.c

It looks like the config/depcomp file is causing the problem. The
dependency file .deps/xxx.Po ends up with spurious CR lines, which cause
the second make to fail. Unfortunately, it's not as simple as just
removing the CRs, as far as I can see, as doing that leaves the error.

I don't know if this is something that can be solved within MSys, or
whether it's gcc that is causing the problem. However, the problem is
*very* annoying. At the moment, my build and test cycle goes

   unpack
   apply current patchfile
   configure
   make
   diagnose and fix error
   generate new patchfile
   delete the whole distribution
   back to the top to unpack again...

This is tedious, to say the least :-(

Any assistance would be most gratefully appreciated!

Paul Moore.

PS I'm using mingw-runtime 2.0 beta to get round a particular porting
issue. You get the same problem with earlier runtimes - I was using 1.2
and had the same problem.