All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Haleigh Novak <haleigh@edt.com>,
	"yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Adding Utilities to /proc
Date: Fri, 1 Apr 2016 13:38:45 -0400	[thread overview]
Message-ID: <56FEB225.9070308@windriver.com> (raw)
In-Reply-To: <1459526845123.21634@edt.com>

[-- Attachment #1: Type: text/plain, Size: 2635 bytes --]

On 2016-04-01 12:07 PM, Haleigh Novak wrote:
>
> Hello All,
>
>
> Firstly I would like to say that I am new here and fairly new to 
> Yocto, so I do apologize if this is the wrong board for this question. 
> (And if it is could someone direct me to the correct board?) 
> Background on me: graduated OSU before Fall 2015 started with a BA 
> Computer Science Computer Systems - minimal yocto ~2 months baby level 
> stuff.
>
>
> Some background on the issue: I am following these directions 
> http://www.crashcourse.ca/introduction-linux-kernel-programming/lesson-11-adding-proc-files-your-modules-part-1 to 
> create a jiffies utility  folder in /proc as a precursor to a larger 
> project. I have made the appropriate changes within the 
> /usr/src/kernel/fs/proc folder and now I am trying to compile and load 
> the module, to place a jiffies entry in /proc. Well when I run 'make' 
> from /usr/src/kernel/ I get most of the way through, way past building 
> my jiffies.o file in user/src/kernel/fs/proc, without errors but 
> toward the end I get the following error.
>
>
> LZO     arch/arm/boot/compressed/piggy.lzo
> /bin/sh: lzop: command not found
> /usr/src/kernel/arch/arm/boot/compressed/Makefile:193: recipe for 
> target 'arch/arm/boot/compressed/piggy.lzo' failed
> make[2]: *** [arch/arm/boot/compressed/piggy.lzo] Error 1
> /usr/src/kernel/arch/arm/boot/Makefile:52: recipe for target 
> 'arch/arm/boot/compressed/vmlinux' failed
> make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
> /usr/src/kernel/arch/arm/Makefile:305: recipe for target 'zImage' failed
> make: *** [zImage] Error 2
>
> I had not though to try to 'make' in this manner before I attempted 
> this project so I don't know if this worked originally. My yocto build 
> is located on one host machine and the actual implementation / working 
> area is on another with an arm processor. I ssh into my device that 
> the yocto build is for and from there I work with the code. If I try 
> to 'make' on the host machine I get an error that it can not 
> find/access some generated files so  hat option I think is out and 
> googling only resulted in that type of solution one to be done on my 
> host machine.
>
> Has anyone ever had this problem before or could point me in a better 
> direction?

If you are generating a module that needs lzo compression .. does your host
distro have lzo installed ? If the kernel recipe you are using doesn't 
specify
lzo-native as a DEPENDS, then there won't be the right tool available to 
do that
compression.

Bruce

>
> Thank you.
>
>
>
>
>


[-- Attachment #2: Type: text/html, Size: 6282 bytes --]

      reply	other threads:[~2016-04-01 17:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01 16:07 Adding Utilities to /proc Haleigh Novak
2016-04-01 17:38 ` Bruce Ashfield [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=56FEB225.9070308@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=haleigh@edt.com \
    --cc=yocto@yoctoproject.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.