Re: breakage with "switch to gdb version script"

Mike Frysinger
2015-04-15T04:35:47Z

[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]

On 15 Apr 2015 04:16, Hans-Peter Nilsson wrote:
> I saw no such problem at 69cb14a0d7, neither for sim nor gdb,
> using an x86_64 Debian 7.1. Info-files *are* being generated
> with src-release.sh, as for a release, so your development tools
> have to be complete. You probably expected this kind of
> reponse, but still: unless it was a temporary bug fixed between
> your test and the commit above, I'd guess your makeinfo tools
> are out of date or something similar, which would not be
> something you can allow yourself to "give up" on, and just skip
> testing. Pretty please investigate.

i run Gentoo and then some. tooling versions are almost never an issue (unless
they're too new). in this case i had a GNUmakefile in a subdir lying around
that confused things. not that the error maked sense:
...
make[1]: Entering directory '/usr/local/src/gnu/gdb/libiberty/testsuite'
make[1]: Nothing to be done for 'info'.
make[1]: Leaving directory '/usr/local/src/gnu/gdb/libiberty/testsuite'
make: Nothing to be done for 'info'.
make: *** No rule to make target 'info'. Stop.
$

> Regarding using the gdb create-version.sh for sim, I'd rather we
> increase separation between sim and gdb sources than making them
> more intertwined like that.

the source repos aren't going to split, so i don't think we should spend time on
the git side. there's no reason though we couldn't bundle version.c in the sim/
tree and drop gdb/ entirely.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]