mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zamir SUN <sztsian@gmail.com>
To: Vladislav Valtchev <vladislav.valtchev@gmail.com>,
	Steven Rostedt <rostedt@goodmis.org>
Cc: johannes.berg@intel.com, johannes@sipsolutions.net,
	linux-kernel@vger.kernel.org, zsun@redhat.com
Subject: Re: [PATCH 1/2] trace-cmd: Fix the detection for swig
Date: Thu, 8 Feb 2018 20:05:13 +0800	[thread overview]
Message-ID: <a1c2c3f6-8d69-227d-51d4-1c40c53e0645@gmail.com> (raw)
In-Reply-To: <1518024315.3742.16.camel@gmail.com>



On 02/08/2018 01:25 AM, Vladislav Valtchev wrote:
> On Wed, 2018-02-07 at 22:01 +0800, Zamir SUN wrote:
>>
>> While just a note for this, in Fedora 27:
>>
>> $ if command -v swig; then echo 1; else echo 0; fi
>> /usr/bin/swig
>> 1
>>
>> Actually this test has the same problem as of `which swig` - When swig
>> exists, the var SWIG_DEFINED will not be 1 (as shown above).
>>
>> I see Vladislav is already on this thread. I hope this can be fixed
>> before merging the patch set.
>>
> 
> Hi Zamir,
> I'm sorry but I'm unable to reproduce the issue on Fedora 27,
> after applying my series of patches.
> 
> In my case (fresh install of Fedora27, no customizations):
> 	if command -v swig; then echo 1; else echo 0; fi
> works as expected.
> 
> SWIG_DEFINED does not have to be '1' in order the Makefile to work.
> Because the check in my branch is:
> 
> ifeq ($(SWIG_DEFINED), 0)
> BUILD_PYTHON := report_noswig
> NO_PYTHON = 1
> endif
> 
> So there should be no problem. Just to be sure, I've tried to compile trace-cmd
> with my patches first without 'swig' and later with it (on Fedora).
> The result was that, in the first case the message 'no swig installed'
> was displayed, while in the other case it was not. Or better, a message
> saying that 'python-dev' is missing was shown.
> [Yes, both swig and python-dev are necessary].
> 
> After installing also 'python-devel' (in Ubuntu is just '-dev'), the
> build system was able to build the rest of the python targets as well.
> 
> 
> Could you please try by using my fork on GitHub?
> https://github.com/vvaltchev/trace-cmd-fork
> BRANCH NAME: make8.
> 
> Let me know if you still experience the issue.
> 

Hi Vladislav,

Thanks for the URL. I tried to build from your make8 branch, it works
fine. I must made some copy-paste mistake yesterday.

Sorry for the noise.

Thanks.

> Thanks,
> Vlad
> 
> 
> 

-- 
Zamir SUN
Fedora user
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E

  reply	other threads:[~2018-02-08 12:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  3:20 [PATCH 0/2] trace-cmd: Improves python plugin support sztsian
2018-02-04  3:20 ` [PATCH 1/2] trace-cmd: Fix the detection for swig sztsian
2018-02-06 23:18   ` Steven Rostedt
2018-02-07 14:01     ` Zamir SUN
2018-02-07 14:40       ` Steven Rostedt
2018-02-07 15:09         ` Zamir SUN
2018-02-07 17:25       ` Vladislav Valtchev
2018-02-08 12:05         ` Zamir SUN [this message]
2018-02-08 14:04           ` Vladislav Valtchev
2018-02-04  3:20 ` [PATCH 2/2] trace-cmd: Change the way of getting python ldflags sztsian
2018-02-08 23:54   ` Steven Rostedt
2018-03-22 23:13   ` Steven Rostedt
2018-03-23 12:19     ` Zamir SUN
2018-02-06 12:31 ` [PATCH 0/2] trace-cmd: Improves python plugin support Zamir SUN
2018-02-06 14:14   ` 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=a1c2c3f6-8d69-227d-51d4-1c40c53e0645@gmail.com \
    --to=sztsian@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vladislav.valtchev@gmail.com \
    --cc=zsun@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

all inboxes | Powered by JetHome®