Bug#619792: gcc-4.6: FTBFS on kfreebsd: gengtype: Internal error: abort in get_output_file_with_visibility, at gengtype.c:1998
Cyril Brulebois
Version: 4.6.0-1
Severity: serious
Justification: FTBFS
User: debia...@lists.debian.org
Usertags: kfreebsd
Hi,
your package FTBFS on kfreebsd-amd64 (at least):
| /bin/bash ../../src/gcc/../move-if-change tmp-constants.h insn-constants.h
| echo timestamp > s-constants
| gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../src/gcc -I../../src/gcc/build -I../../src/gcc/../include -I../../src/gcc/../libcpp/include -I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd -I../libdecnumber \
| -o build/min-insn-modes.o min-insn-modes.c
| gcc -c -g -fkeep-inline-functions -DIN_GCC -W -Wall -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -Wold-style-definition -Wc++-compat -DHAVE_CONFIG_H -DGENERATOR_FILE -I. -Ibuild -I../../src/gcc -I../../src/gcc/build -I../../src/gcc/../include -I../../src/gcc/../libcpp/include -I../../src/gcc/../libdecnumber -I../../src/gcc/../libdecnumber/dpd -I../libdecnumber \
| -o build/genflags.o ../../src/gcc/genflags.c
| build/gengtype \
| -r gtype.state
| gengtype: Internal error: abort in get_output_file_with_visibility, at gengtype.c:1998
| make[5]: *** [s-gtype] Error 1
Full build logs:
https://buildd.debian.org/status/package.php?p=gcc-4.6&suite=sid
Filing as serious since it's just an essential part of the toolchain.
Please get in touch with debian-bsd@ if you need help.
KiBi.
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Cyril Brulebois
> On 27.03.2011 04:22, Cyril Brulebois wrote:
> > Please get in touch with debian-bsd@ if you need help.
>
please just contact the appropriate people, pretty please?
Cyril Brulebois
> please just contact the appropriate people, pretty please?
And since apparently IRC is the way to answer people and not to mail
the appropriate ones…
05:40:14 [doko__] ping?
05:44:11 [KiBi] pong.
05:44:58 [doko__] I don't care about kfreebsd. debian is upstream for that arch, so they should handle it
05:45:14 [KiBi] That's why you should talk to debian porters, at debian-bsd@.
05:45:22 [doko__] no
05:45:37 [KiBi] Why?
05:45:52 [doko__] debian-bsd should talk to upstreams and debian maintainers
05:46:15 [doko__] and debian-bsd should take care about keeping the port alive
05:46:25 [KiBi] That's why you should talk to them.
05:46:39 [KiBi] “Fix my bug” would be a start, even if you don't like communicating that much.
05:47:02 [doko__] again, no. if you feel like this, please reassign the bug to some debian-bsd package
05:47:05 [KiBi] You're wasting my time instead of sending them a mail, that's absurd.
05:47:37 [doko__] no, you are wasting your own time.
05:48:18 [KiBi] Anything against my telling debian-bsd that?
05:48:29 [doko__] not at all
KiBi.
Petr Salinger
--
The failure is on kfreebsd-amd64 with 4.6.0-1,
but the 4.6.0~rc1-2, 4.6.0~rc1-3 have been fine.
All tried on fash. The difference is used gcc-4.5.
Failed builds used gcc-4.5_4.5.2-7,
the previous used gcc-4.5_4.5.2-6.
Petr