Linux DTrace development list
 help / color / mirror / Atom feed
From: Nick Alcock <nick.alcock@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH] build: install sdt*.h in /usr/lib64/dtrace/include/sys
Date: Thu, 23 May 2024 19:49:26 +0100	[thread overview]
Message-ID: <87cypcs6rt.fsf@esperi.org.uk> (raw)
In-Reply-To: <Zk+N3P7NnwzL1ZSz@oracle.com> (Kris Van Hees's message of "Thu, 23 May 2024 14:41:32 -0400")

On 23 May 2024, Kris Van Hees verbalised:

> Can you split the move of sdt.h and sdt_internal.h into its own patch
> please?  And I guess the pkg-config stuff in a follw-up patch?  Still
> need to look into that a bit more because I have reservations.  But
> the moving of the header files is definitely something that should be
> in its own patch.

I put them in the same commit for a reason: doing otherwise would break
the installed testsuite in the intermediate commit, and I don't want to
implement *two distinct* mechanisms for locating the headers when we
already have one that works perfectly well (pkg-config).

(Also, splitting them up runs the risk of your integrating one without
the other, and they really do go together.)

> Introducing pkg-config as a mechanism that people can use is a separate
> thing (and as far as I can see, could use some extra work anyway because
> e.g. runtest.sh still has other absolute paths in it that cause failures
> when the DTrace build is configured to install things in non-standard
> locations).

Well, yes, I didn't try to make the *entire build* relocatable in this
patch. That really *would* have been too much for one commit.

  reply	other threads:[~2024-05-23 18:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 17:56 [PATCH] build: install sdt*.h in /usr/lib64/dtrace/include/sys Nick Alcock
2024-05-23 18:41 ` Kris Van Hees
2024-05-23 18:49   ` Nick Alcock [this message]
2024-05-23 18:56     ` Kris Van Hees
2024-05-23 20:02       ` Nick Alcock

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=87cypcs6rt.fsf@esperi.org.uk \
    --to=nick.alcock@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=kris.van.hees@oracle.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