Linux DTrace development list
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: Kris Van Hees <kris.van.hees@oracle.com>,
	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 14:56:36 -0400	[thread overview]
Message-ID: <Zk+RZEAcL32ziSrF@oracle.com> (raw)
In-Reply-To: <87cypcs6rt.fsf@esperi.org.uk>

On Thu, May 23, 2024 at 07:49:26PM +0100, Nick Alcock wrote:
> 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).

Do the first patch with the moving of the sdt header files, adding an
explicit -I/usr/lib64/dtrace/include to the CFLAGS, and the testsuite
should work perfectly fine with the file move.  That is hardly another
mechanism.

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

They are two different things - I mentioned that from the very beginning
of the discussions to deal with the sys/sdt.h conflict,  Please split it
into two patches.  The pkg-config support is bigger than just this sdt
header file move.

> > 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.

Yet the purpose of introducing pkg-config is to deal with installs in
non-standard locations.  If we are not caring about that right now, then
there is no need to introduce pkg-config just yet either, and definitely
not as part of the patch of moving the sdt header files.

  reply	other threads:[~2024-05-23 18:56 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
2024-05-23 18:56     ` Kris Van Hees [this message]
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=Zk+RZEAcL32ziSrF@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=dtrace-devel@oss.oracle.com \
    --cc=dtrace@lists.linux.dev \
    --cc=nick.alcock@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