Jim Meyering <[EMAIL PROTECTED]> writes:
> I use the gcc snapshot of the day (checked out 2001-01-11.04h59 UTC)
> and tried putting your latest depcomp into fileutils. It worked fine
> for builds in a directory that was already configured (stale depmode?),
Either that or 'config.cache' -- the dependency mode is determined at
'configure' time and cached.
> but when I ran `make distcheck', it ended up running in gcc3 mode and
> failed because it put preprocessor output in the .o file.
>
> The symptom was that linking failed because the .o file wasn't valid.
>
> Here's s tiny test case that tries to demonstrate what happened:
>
> $ cat k.c
> int foo () {}
> $ DEPENDENCIES_OUTPUT=1 gcc -c -o k.o k.c -M -MT k.o -MF k.Po
> $ cat k.o
> # 1 "k.c"
> int foo () {}
>
> I'm using automake-1.4b.
>
> | 2001-01-10 Tom Tromey <[EMAIL PROTECTED]>
> |
> | * depcomp: Handle gcc 3.
I think this is a GCC bug, not a problem with 'automake'. For some
reason, it is treating the -c as a -E.
- Hari
--
Raja R Harinath ------------------------------ [EMAIL PROTECTED]
"When all else fails, read the instructions." -- Cahn's Axiom
"Our policy is, when in doubt, do the right thing." -- Roy L Ash
