Hi Michael, Michael Tautschnig <[email protected]> writes: > error: conflicting function declarations "lookup" > old definition in module data file > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/src/cmd/6l/l.h > line 405 > struct Sym * (char *name, signed int v) > new definition in module 8db file > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/include/mach.h > line 377 > signed int (char *, char *, struct Symbol *) > go tool dist: FAILED: gcc -Wall -Wstrict-prototypes -Wextra -Wunused > -Wuninitialized -Wno-sign-compare -Wno-missing-braces -Wno-parentheses > -Wno-unknown-pragmas -Wno-switch -Wno-comment -Wno-missing-field-initializers > -Werror -fno-common -ggdb -pipe -O2 -o > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/pkg/tool/linux_amd64/6l > -m64 $WORK/data.o $WORK/decodesym.o $WORK/dwarf.o $WORK/elf.o $WORK/go.o > $WORK/ldelf.o $WORK/ldmacho.o $WORK/ldpe.o $WORK/lib.o $WORK/macho.o > $WORK/pe.o $WORK/symtab.o $WORK/asm.o $WORK/enam.o $WORK/list.o $WORK/obj.o > $WORK/optab.o $WORK/pass.o $WORK/prof.o $WORK/span.o > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/pkg/obj/linux_amd64/libmach.a > > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/pkg/obj/linux_amd64/libbio.a > > /srv/jenkins-slave/workspace/sid-goto-cc-golang/golang-1.2.1/pkg/obj/linux_amd64/lib9.a > -lm > debian/rules:106: recipe for target 'debian/build.stamp' failed > make[1]: *** [debian/build.stamp] Error 1 > > Given that the signatures differ both in the number of parameters and the > return > type, quite likely this conflict is not at all intended. Is there a "static" > missing? I don’t know the compiler code well enough to judge that. From a quick look, it isn’t obvious to me either.
Can you take this issue upstream directly please? I don’t think it’s effective for me to play messenger here. You can find the Go bugtracker at http://code.google.com/p/go/issues/list If you insist, please provide some steps to reproduce. -- Best regards, Michael -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
