All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: Jan Engelhardt <jengelh@inai.de>
Cc: factory@lists.opensuse.org, linux-trace-devel@vger.kernel.org
Subject: Re: trace-cmd build fails due to due make 'not recursively expanding'
Date: Fri, 25 Nov 2022 11:31:47 +0100	[thread overview]
Message-ID: <20221125103147.arrsukzbgiegfux5@carbon> (raw)
In-Reply-To: <1o2r1723-o3o5-3p83-8131-896soq68o76@vanv.qr>

On Fri, Nov 25, 2022 at 11:15:38AM +0100, Jan Engelhardt wrote:
> 
> On Friday 2022-11-25 10:20, Daniel Wagner wrote:
> >
> >trace-cmd stop building and due to make getting stuck in loop
> >and complaining with:
> >
> >  $ make -d
> >  Makefile:79: not recursively expanding pkgconfig_dir to export to shell function
> >
> >I don't really know what's going on. Any ideas?
> 
> https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/FPNDORIL6NDJD3HFQ76LQBIRBCWVG6TV/
> (I already informed Steven last night via email. / Wasn't aware there 
> is a linux-trace-devel@)

Oops, didn't check the factory mailing list first. So there is no easy
workaround.

FWIW, I've got a bunch of initial Meson patches for libtraceevent and
libtracefs. I suppose I should also look at trace-cmd. Steven told me
that he will look at those patches but not before the holiday season.

Daniel

  reply	other threads:[~2022-11-25 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-25  9:20 trace-cmd build fails due to due make 'not recursively expanding' Daniel Wagner
2022-11-25 10:15 ` Jan Engelhardt
2022-11-25 10:31   ` Daniel Wagner [this message]
2022-11-25 23:20     ` Steven Rostedt

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=20221125103147.arrsukzbgiegfux5@carbon \
    --to=dwagner@suse.de \
    --cc=factory@lists.opensuse.org \
    --cc=jengelh@inai.de \
    --cc=linux-trace-devel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.