Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Mathieu Desnoyers <compudj@krystal.dyndns.org>
Cc: "Cui\, Dexuan" <dexuan.cui@intel.com>,
	       "'ltt-dev\@lists.casi.polymtl.ca'"
	<ltt-dev@lists.casi.polymtl.ca>,
	       "'gdb\@sourceware.org'" <gdb@sourceware.org>,
	       systemtap@sources.redhat.com,
	Josh Stone <jistone@redhat.com>
Subject: Re: [ltt-dev] gdb-7.2 can't build with lttng-ust-0.12
Date: Wed, 27 Apr 2011 14:32:00 -0000	[thread overview]
Message-ID: <m3ei4nlq9j.fsf@fleche.redhat.com> (raw)
In-Reply-To: <BLU0-SMTP45CC9DEEE33FD5A526EB3896990@phx.gbl> (Mathieu	Desnoyers's message of "Tue, 26 Apr 2011 17:41:40 -0400")

>>>>> "Mathieu" == Mathieu Desnoyers <compudj@krystal.dyndns.org> writes:

Mathieu> The only concern here is the packaging: if we depend on sdt.h,
Mathieu> we have to either ship it with UST, or have one more dependency
Mathieu> on a package available for all architectures that only contain
Mathieu> this header. Thoughts ?

One typical way to handle this is to put a copy of the code into your
tree, but provide an option to use the system version instead.  E.g.,
GDB does this with readline.  This makes it build fine out of the box
for casual users, but is also friendly to distros.  This implies some
discipline on your part -- updating regularly and not diverging.

Alternatively, split sdt.h out into its own project and make it a
build-time requirement of both stap and ust.  This seems pretty
heavy-weight for a couple of header files, though.

Tom


      parent reply	other threads:[~2011-04-27 14:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1865303E0DED764181A9D882DEF65FB6931C75A5AA@shsmsx502.ccr.corp.intel.com>
     [not found] ` <BLU0-SMTP7051C411EF9E3864329F4596960@phx.gbl>
2011-04-26  1:51   ` Cui, Dexuan
2011-04-26 18:47     ` Tom Tromey
2011-04-26 21:42       ` Mathieu Desnoyers
     [not found]       ` <BLU0-SMTP3759F7830D97C89E9BCE9796990@phx.gbl>
2011-04-27  0:26         ` Josh Stone
     [not found]       ` <BLU0-SMTP45CC9DEEE33FD5A526EB3896990@phx.gbl>
2011-04-27 14:32         ` Tom Tromey [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=m3ei4nlq9j.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=compudj@krystal.dyndns.org \
    --cc=dexuan.cui@intel.com \
    --cc=gdb@sourceware.org \
    --cc=jistone@redhat.com \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=systemtap@sources.redhat.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