Il 16/09/2013 19:23, Tom Tromey ha scritto:
> Tom> I can try a test build using a setting for CC that rejects -c -o.
>
> I did this and the build died pretty early on:
>
> /home/tromey/Space/Trunk/Git/bin/my-cc -c -DHAVE_CONFIG_H -g -g -I.
> -I../../gcc/libiberty/../include -W -Wall -Wwrite-s
Tom> I can try a test build using a setting for CC that rejects -c -o.
I did this and the build died pretty early on:
/home/tromey/Space/Trunk/Git/bin/my-cc -c -DHAVE_CONFIG_H -g -g -I.
-I../../gcc/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat
-Wstrict-prototypes -pedantic -fpi
Paolo> You are listed as the author of the "compile" script in Automake, do you
Paolo> remember which compilers need it? I'm too young for that (that's
Paolo> something I can say less and less :))...
I have no idea any more.
I can try a test build using a setting for CC that rejects -c -o.
Tom
Il 26/08/2013 18:09, Tom Tromey ha scritto:
>> "Ian" == Ian Lance Taylor writes:
>
> Ian> I assume that dropping $(OUTPUT_OPTION) is correct--I haven't looked
> Ian> at the new definition of $(COMPILE).
>
> I believe the depcomp script takes care of this.
I think that would be the "compile"
> "Ian" == Ian Lance Taylor writes:
Ian> I assume that dropping $(OUTPUT_OPTION) is correct--I haven't looked
Ian> at the new definition of $(COMPILE).
I believe the depcomp script takes care of this.
Tom
2013/8/20 Tom Tromey :
> This converts Go.
>
> It renames gospec.o to go/gospec.o, for uniformity and so we can
> remove an explicit rule.
>
> It defines go_OBJS, to conform to the documented Make-lang.in
> conventions, and to ensure that Go objects are given the correct
> order-only dependencies o
This converts Go.
It renames gospec.o to go/gospec.o, for uniformity and so we can
remove an explicit rule.
It defines go_OBJS, to conform to the documented Make-lang.in
conventions, and to ensure that Go objects are given the correct
order-only dependencies on generated files.
* Make-la
