Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb@sourceware.org, Joel Sherrill <joel.sherrill@oarcorp.com>,
	Anthony Green <green@moxielogic.com>
Subject: Re: integrating dtc into the sim/ tree
Date: Thu, 21 Aug 2014 07:32:00 -0000	[thread overview]
Message-ID: <20140821073234.GM4828@adacore.com> (raw)
In-Reply-To: <2642309.RSytPSsbtK@vapier>

> it's pretty mature imo.  lemme phrase it this way: it's a hard
> requirement nowadays for ARM on Linux, so it's def viable.  i think a
> lot of the docs you're referring to is because the library aims to be
> used literally everywhere -- vendor BIOS, vendor kernels, etc...  the
> license readme explains this a bit more:
> https://git.kernel.org/cgit/utils/dtc/dtc.git/tree/README.license
[...]
> i'd be willing to make sure it builds everywhere.  the external
> dependencies in libfdt are extremely light (by design -- it wants to
> work in your typical BIOS).  basically it needs str/mem funcs and not
> ancient stdint.h.

You may actually have some issues with ancient stdint.h, but that
should be reasonably easy to take care of (eg. via gnulib) and
it seems to me like you have the answers to all my concerns, so
I no longer have any reservation towards that move. I would perhaps
poll the other GDB GMs to make sure they also have no objection
to it. So, to summarize:

  - Require dtc compiler in maintainer mode or when modifying
    some of the description files. Already required today for
    the moxie simulator.

    In non-maintainer mode, the generated files are already
    checked in.

  - Next step: Require and link against libdtc for all simulators
    instead of just moxie.

-- 
Joel


  reply	other threads:[~2014-08-21  7:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-18 22:14 gdb moxie build failure Joel Sherrill
2014-08-19  5:38 ` integrating dtc into the sim/ tree Mike Frysinger
2014-08-19  6:26   ` Joel Brobecker
2014-08-20  9:33     ` Mike Frysinger
2014-08-20  9:53       ` Joel Brobecker
2014-08-20 15:30         ` Mike Frysinger
2014-08-20 16:06           ` Joel Brobecker
2014-08-20 16:11             ` Joel Sherrill
2014-08-20 16:19               ` Joel Brobecker
2014-08-20 16:37                 ` Joel Sherrill
2014-08-21  1:31                 ` Mike Frysinger
2014-08-21  1:25             ` Mike Frysinger
2014-08-21  7:32               ` Joel Brobecker [this message]
2014-08-21  9:05                 ` Pedro Alves
2014-08-21 13:58                   ` Joel Sherrill
2014-08-21 16:25             ` Richard Henderson

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=20140821073234.GM4828@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=green@moxielogic.com \
    --cc=joel.sherrill@oarcorp.com \
    --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