This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH] Add the '-p4' options when exemplifying the module compilation
- From: Josh Stone <jistone at redhat dot com>
- To: nborisov <n dot borisov dot lkml at gmail dot com>, systemtap at sourceware dot org
- Cc: fche at redhat dot com
- Date: Mon, 27 Jun 2016 17:44:04 -0700
- Subject: Re: [PATCH] Add the '-p4' options when exemplifying the module compilation
- Authentication-results: sourceware.org; auth=none
- References: <1467045995-7718-1-git-send-email-n dot borisov dot lkml at gmail dot com> <1340d1c4-cf0b-e012-f732-79561ff1a03b at redhat dot com> <5771C792 dot 5030209 at gmail dot com>
On 06/27/2016 05:40 PM, nborisov wrote:
>
>
> On 27.06.2016 20:14, Josh Stone wrote:
>> On 06/27/2016 09:46 AM, Nikolay Borisov wrote:
>>> Currently the example command which supposedly should compile the
>>> instrumentation module is missing the '-p4' option, meaning that
>>> upon running it will compile and run the module. In order to make
>>> the command more in sync with what this particular chapter is about,
>>> add the -p4 options so that after running the command the user gets
>>> to copy the resulting module.
>>
>> It's implicitly limited to -p4 already when the chosen -r kernel doesn't
>> match the locally running kernel. You'll see:
>
> Actually when I ran the command given in the book, the script would
> compile and run.
Was your "-r kernel" the same as the running kernel?
Otherwise it really shouldn't happen, so we may have a bug...
>> WARNING: kernel release/architecture mismatch with host forces
>> last-pass 4.
>>
>> Making it explicit to avoid the warning is good though. It looks like
>> fche already pushed your patch.
>
>
>>