Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Cherry <ncherry@linuxha.com>
To: buildroot@busybox.net
Subject: [Buildroot] Following direction, but failing to compile
Date: Wed, 08 Jul 2009 11:19:57 -0400	[thread overview]
Message-ID: <4A54B91D.4070701@linuxha.com> (raw)
In-Reply-To: <87a5b0800907070308y1aa17e91x591256e28f8879a7@mail.gmail.com>

Will Newton wrote:
> On Thu, Jul 2, 2009 at 7:04 PM, Neil Cherry<ncherry@linuxha.com> wrote:

>> When I'm compiling all goes well until I hit this:
>>
>>        :
>>  DEPMOD  2.6.29.4-test
>> make[1]: Leaving directory
>> `/home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/linux-2.6.29.4'
>> + rm -f
>> /home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root/lib/modules/2.6.29.4/build
>> /home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root/lib/modules/2.6.29.4/source
>> + /home/njc/stuff/buildroot-2009.05/build_i586/staging_dir/bin/i586-linux-depmod26 -b
>> /home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root 2.6.29.4
>> WARNING: Couldn't open directory
>> /home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root/lib/modules/2.6.29.4: No
>> such file or directory
>> FATAL: Could not open
>> /home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root/lib/modules/2.6.29.4/modules.dep.temp
>> for writing: No such file or directory
>> make: ***
>> [/home/njc/stuff/buildroot-2009.05/project_build_i586/LORHA/root/lib/modules/2.6.29.4/modules.dep]
>> Error 1
>>
>> I'm having trouble finding where the sequence of commands are
>> executed so I can figure out why the directory is not being created.
>>
>> I can go into the linux-2.6.29.4 directory and manually compile
>> the kernel with no errors.
>>
>> Any pointers would be appreciated.
> 
> It looks like it's the modules_install target in the kernel Makefile
> that is failing. Can you make that target successfully i.e. make
> modules_install in the kernel tree?

Sorry for the delay.

Yes when I go into the kernel directory I can compile the modules
with no problems. My fix was to add a mkdir just after the rm -rf
in that section of the make file (I can't find it right now).

I'll find that info and post it here so we can see if it makes
any sense to anyone.

Thanks

-- 
Linux Home Automation         Neil Cherry       ncherry at linuxha.com
http://www.linuxha.com/                         Main site
http://linuxha.blogspot.com/                    My HA Blog
Author of:    	Linux Smart Homes For Dummies

      reply	other threads:[~2009-07-08 15:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 18:04 [Buildroot] Following direction, but failing to compile Neil Cherry
2009-07-07 10:08 ` Will Newton
2009-07-08 15:19   ` Neil Cherry [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=4A54B91D.4070701@linuxha.com \
    --to=ncherry@linuxha.com \
    --cc=buildroot@busybox.net \
    /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