public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tsukasa OI <research_trasio@irq.a4lg.com>
To: Tsukasa OI <research_trasio@irq.a4lg.com>,
	Anthony Green <green@moxielogic.com>
Cc: gdb-patches@sourceware.org
Subject: [PATCH 0/1] sim/moxie: add custom directory stamp rule
Date: Thu,  8 Sep 2022 11:45:46 +0000	[thread overview]
Message-ID: <cover.1662637359.git.research_trasio@irq.a4lg.com> (raw)

Hello,

While I'm testing maintainer mode with:

$srcdir/configure \
    --enable-targets=all \
    --enable-maintainer-mode \
    --enable-gold \
    --enable-ld \
    --enable-nls \
&& make

I encountered several issues.  Along with:

1.  <https://sourceware.org/pipermail/binutils/2022-September/122770.html>
    which is resolved by:
    <https://sourceware.org/pipermail/binutils/2022-September/122780.html>
2.  <https://sourceware.org/pipermail/gdb-patches/2022-September/191731.html>

this is the third (and the last) issue preventing all-arch build with
the maintainer mode enabled.



If maintainer mode is enabled and try to build moxie simulator, the build
fails because there's no rule to make sim/moxie/.dirstamp to build
sim/moxie/moxie-gdb.dtb.

Normally, Automake creates directory stamp file when an output is in a
subdirectory.  However, only if the output is either a program or a library.

Because sim/moxie/moxie-gdb.dtb is neither a program nor a library (but a
binary-format DeviceTree, a data file), Automake does not generate dirstamp
file ($builddir/sim/moxie/.dirstamp) for it and causes this error.

This commit adds its own rule for the directory stamp (modified copy of the
Automake output) and adds the directory stamp file to DISTCLEANFILES to
mimic Automake-generated behavior (although "make distclean" does not work
when maintainer mode is enabled).

Thanks,
Tsukasa




Tsukasa OI (1):
  sim/moxie: add custom directory stamp rule

 sim/Makefile.in    | 23 ++++++++++++++---------
 sim/moxie/local.mk |  5 +++++
 2 files changed, 19 insertions(+), 9 deletions(-)


base-commit: 39eedb20b7e95e469d11667c11233233e9d0226b
-- 
2.34.1


             reply	other threads:[~2022-09-08 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 11:45 Tsukasa OI [this message]
2022-09-08 11:45 ` [PATCH 1/1] " Tsukasa OI
2022-10-09  3:57 ` [PATCH v2 0/1] " Tsukasa OI
2022-10-09  3:57   ` [PATCH v2 1/1] " Tsukasa OI
2022-10-11 10:34     ` Andrew Burgess

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=cover.1662637359.git.research_trasio@irq.a4lg.com \
    --to=research_trasio@irq.a4lg.com \
    --cc=gdb-patches@sourceware.org \
    --cc=green@moxielogic.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).