Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hans-peter.nilsson@axis.com>
To: vapier@gentoo.org
Cc: gdb-patches@sourceware.org
Subject: breakage with "switch to gdb version script"
Date: Mon, 13 Apr 2015 14:35:00 -0000	[thread overview]
Message-ID: <201504131435.t3DEZTAS012532@ignucius.se.axis.com> (raw)

This commit:

commit 8c32ba22334b8be1c2cf412a789deeded786e1f5
Author: Mike Frysinger <vapier@gentoo.org>
Date:   Fri Apr 10 19:40:54 2015 -0400

    sim: switch to gdb version script
    
    Since the local create-version.sh already points directly into the gdb
    source tree, we might as well use the gdb script directly too.

 sim/common/ChangeLog         |    5 +++++
 sim/common/Make-common.in    |    5 +++--
 sim/common/create-version.sh |   38 --------------------------------------
 3 files changed, 8 insertions(+), 40 deletions(-)

seems to have caused breakage building a sim for
powerpc-unknown-eabisim:

...
make[3]: *** No rule to make target `/tmp/hpautotest-sim/src/sim/ppc/../common/create-version.sh', needed by `version.c'.  Stop.
make[3]: Leaving directory `/tmp/hpautotest-sim/powerpc-eabisim/sim/ppc'
make[2]: *** [all] Error 1make[2]: Leaving directory `/tmp/hpautotest-sim/powerpc-eabisim/sim'

While that seems pretty trivial, you also need to adjust
src-release.sh to make sure "./src-release.sh -b sim" works,
in which a tool-specific create-version.sh is searched.

brgds, H-P


             reply	other threads:[~2015-04-13 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-13 14:35 Hans-Peter Nilsson [this message]
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

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=201504131435.t3DEZTAS012532@ignucius.se.axis.com \
    --to=hans-peter.nilsson@axis.com \
    --cc=gdb-patches@sourceware.org \
    --cc=vapier@gentoo.org \
    /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