Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ma Andrew <andrewma83@hotmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20
Date: Thu, 3 Apr 2008 16:59:43 -0700	[thread overview]
Message-ID: <BLU136-W408F3BBAFC783BCAF49646C3F70@phx.gbl> (raw)
In-Reply-To: <326f33790804031646w6a11671fgba1f50aba995f450@mail.gmail.com>


ok hope this one would help.

'ln -s project_build_i386/uclibc/linux-2.6-24/arch/x86 x86' in your buildroot.  It should at least let you pass through the error that you post on the email.

--Andrew
________________________________
> Date: Thu, 3 Apr 2008 16:46:03 -0700
> From: reddyac at gmail.com
> To: andrewma83 at hotmail.com
> Subject: Re: [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20
> CC: buildroot at uclibc.org
> 
> Hi Andrew,
> 
> I found the actual bzImage (not the symbolic links) at:
> 
> /buildroot/project_build_i386/uclibc/linux-2.6-24/arch/x86/boot/bzImage
> 
> So I made a symbolic link to that bzImage and I can see it within /buildroot/binaries/$PROJECT.
> 
> Unfortunately the .iso file is no where to be found after I compile. Hopefully someone can give some feedback on this. Thanks again for your suggestions Andrew!
> 
> 2008/4/3 Ma Andrew>:
> 
> Sorry I want to send the command but somehow hotmail doens't let me.  There is a missing part on the command that I suggest.  You can do a "find . -name bzImage -print" on "/root/buildroot" will show all the path that contain bzImage.  Only one contains the real file, all of them are just symbolic links.  I believe the script is trying to look for bzImage but it is a sym link point to somewhere it doesn't exists.
> 
> Perhaps, there may be a better way to solve it in "make menuconfig" instead of hacking it through sym link.
> 
> --Andrew
> ________________________________
>> Date: Thu, 3 Apr 2008 15:13:41 -0700
>> From: reddyac at gmail.com
>> To: andrewma83 at hotmail.com
>> Subject: Re: [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20
>> CC: buildroot at uclibc.org
>>
>> Thanks a lot for your suggestion. I made a symbolic link to the x86 directory but I still don't find my rootfs.i386.iso file within buildroot/binaries/$PROJECT.
>>
>> I also didn't see any errors this time, but I piped the errors to error.log and checked it, and still get the message that reads i386-linux-2.6.24-20080403 cannot be found.
>>
>> On Thu, Apr 3, 2008 at 2:33 PM, Ma Andrew> wrote:
>>
>> I think you can make a sym link like this on your /root/buildroot directory.
>> "ln -s ./project_build_i686//linux-2.6.24/arch/x86 x86" and see if it works for you.
>>
>>
>>
>> ________________________________
>>> Date: Thu, 3 Apr 2008 13:58:28 -0700
>>> From: reddyac at gmail.com
>>> To: buildroot at uclibc.org
>>> Subject: [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20080403)
>>>
>>> Hi everyone.
>>>
>>> I am able to successfully compile Buildroot and I end up with a resulting file system image rootfs.i386.ext2 and a bzImage for the kernel. I want to boot up my newly created kernel in VirtualBox, and I will need an .iso to do that. So modified menuconfig to give me an .iso and typed make again. Unfortunately I run into an error that states:
>>>
>>> cp: cannot stat '/root/buildroot/binaries/uclibc/i386-linux-2.6.24-20080403': No such file or directory
>>> make: *** [/root/buildroot/binaries/uclibc/rootfs.i386.iso] Error 1
>>>
>>> I checked that folder and I see file named i386-linux-2.6.24-20080403, and cannot understand why it is giving me this error. Can someone give me a clearer indication to what this error is referring and how I can go about fixing it?
>>>
>>> Thank you in advance for your response!
>>
>> _________________________________________________________________
>> ??????????????? ? MSN ?????
>> http://toolbar.live.com/
> 
> _________________________________________________________________
> ?? Windows Live Messenger 8.5 ??????????????????????????? ????
> http://get.live.com/zh-cht-tw/betas/messenger_betas

_________________________________________________________________
??? Windows Live Messenger ? Hotmail????????????? ? Windows Live for Mobile 
http://www.msn.com.tw/msnmobile/ 

  reply	other threads:[~2008-04-03 23:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 20:58 [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20080403) Arun Reddy
2008-04-03 21:33 ` [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20 Ma Andrew
2008-04-03 22:07   ` Ma Andrew
2008-04-03 22:13   ` Arun Reddy
2008-04-03 23:04     ` Ma Andrew
2008-04-03 23:46       ` Arun Reddy
2008-04-03 23:59         ` Ma Andrew [this message]
2008-04-04  0:22           ` Arun Reddy
2008-04-04  2:03             ` Ma Andrew
2008-04-04  4:48               ` Nigel Kukard
2008-04-04  5:36                 ` Ma Andrew
2008-04-04  6:26                   ` Nigel Kukard
2008-04-04 17:37                     ` Ma Andrew

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=BLU136-W408F3BBAFC783BCAF49646C3F70@phx.gbl \
    --to=andrewma83@hotmail.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