Linux DTrace development list
 help / color / mirror / Atom feed
From: Kris Van Hees <kris.van.hees@oracle.com>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev
Subject: Re: [PATCH] build: install all pregenerated dlibs
Date: Thu, 2 May 2024 02:15:57 -0400	[thread overview]
Message-ID: <ZjMvnWqk4Xp2Ty7U@oracle.com> (raw)
In-Reply-To: <ZjMq7lGJ7h9Ko+5e@oracle.com>

On Thu, May 02, 2024 at 01:55:58AM -0400, Kris Van Hees wrote:
> From: Nick Alcock <nick.alcock@oracle.com>
> 
> Signed-off-by: Nick Alcock <nick.alcock@oracle.com>

Reviewed-by: Kris Van Hees <kris.van.hees@oracle.com>

> ---
>  libdtrace/Build | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/libdtrace/Build b/libdtrace/Build
> index 473b4d5a58da0..b0e372f9a948a 100644
> --- a/libdtrace/Build
> +++ b/libdtrace/Build
> @@ -295,7 +295,7 @@ install::
>  	$(if $(NATIVE_BITNESS_ONLY),,install -m 644 $(DRTI32_OBJ) $(INSTLIBDIR)/dtrace/drti)
>  	$(call describe-install-target,$(INSTLIBDIR)/dtrace/drti,drti-vers)
>  	install -m 644 $(objdir)/dlibs/drti/drti-vers $(INSTLIBDIR)/dtrace/drti
> -	for kernel in $(SHORTKERNELS); do \
> +	for kernel in $$(cd $(objdir)/dlibs; echo [0-9]*); do \
>  		$(call describe-expanded-install-target,$(INSTLIBDIR)/dtrace/$$kernel,$(WORKING_DLIBS)) \
>  		mkdir -p $(INSTLIBDIR)/dtrace/$$kernel && \
>  		cd $(objdir)/dlibs/$$kernel && install -m 644 $(WORKING_DLIBS) $(INSTLIBDIR)/dtrace/$$kernel; \
> 
> base-commit: 6c5f67cc8ea1d694da8043c8f5aeb2f97b69997a
> -- 
> 2.44.0.273.ge0bd14271f

      reply	other threads:[~2024-05-02  6:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-02  5:55 [PATCH] build: install all pregenerated dlibs Kris Van Hees
2024-05-02  6:15 ` Kris Van Hees [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=ZjMvnWqk4Xp2Ty7U@oracle.com \
    --to=kris.van.hees@oracle.com \
    --cc=dtrace@lists.linux.dev \
    /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