From: Mike Frysinger <vapier@gentoo.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb@sourceware.org, Joel Sherrill <joel.sherrill@oarcorp.com>,
Anthony Green <green@moxielogic.com>
Subject: Re: integrating dtc into the sim/ tree
Date: Wed, 20 Aug 2014 09:33:00 -0000 [thread overview]
Message-ID: <1732783.0nBxt22mln@vapier> (raw)
In-Reply-To: <20140819062557.GE4828@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 883 bytes --]
On Tue 19 Aug 2014 08:25:57 Joel Brobecker wrote:
> > so i guess that leaves us with linking against a system copy. i'm fine
> > with that too. thoughts ?
>
> Do I understand correctly that this is the status quo?
gdb links against system libs which the FSF has no control over:
- python
- xz-utils (lzma)
- expat
- zlib
this last one is also included directly in the gcc tree (also the sourceware
tree in the past iirc)
gcc links to non-FSF 3rd party libs, albeit doesn't bundle them
so after talking to myself, i guess the issue isn't so much with using the
system copy of dtc as it is with making it a hard requirement (which is
different from how the other packages use 3rd party libs -- they're all
optional). might be able to reduce the requirement so only the hw layers hard
depend on it, but i'm not sure if even that is possible.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-20 9:33 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 [this message]
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
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=1732783.0nBxt22mln@vapier \
--to=vapier@gentoo.org \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=green@moxielogic.com \
--cc=joel.sherrill@oarcorp.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