Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
Cc: gdb-patches@sourceware.org
Subject: Re: breakage with "switch to gdb version script"
Date: Wed, 15 Apr 2015 04:35:00 -0000	[thread overview]
Message-ID: <20150415043543.GH872@vapier> (raw)
In-Reply-To: <201504150216.t3F2GroJ012806@ignucius.se.axis.com>

[-- 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 --]

      reply	other threads:[~2015-04-15  4:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 14:35 Hans-Peter Nilsson
2015-04-14  3:18 ` [PATCH] sim: ppc: fix up version script Mike Frysinger
2015-04-14 15:29 ` breakage with "switch to gdb version script" Mike Frysinger
2015-04-14 20:43   ` Hans-Peter Nilsson
2015-04-14 21:18     ` Mike Frysinger
2015-04-15  2:17       ` Hans-Peter Nilsson
2015-04-15  4:35         ` Mike Frysinger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150415043543.GH872@vapier \
    --to=vapier@gentoo.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hans-peter.nilsson@axis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox