From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] No proc mounted
Date: Wed, 23 Oct 2013 19:39:11 +0200 [thread overview]
Message-ID: <526809BF.5030500@mind.be> (raw)
In-Reply-To: <OF7B6E1B94.FFB21E9B-ON85257C0D.005FDC58-85257C0D.005FEE0A@LocalDomain>
On 23/10/13 19:27, Naitik Amin wrote:
> There isn't !
>
> /system/skeleton$ ls
> bin dev etc home media mnt opt run sbin sys usr var
That's weird... You're also missing lib, root and tmp...
Where did you get this buildroot tree?
You didn't put this on a FAT or NTFS partition, did you? That won't
work (but I would expect buildroot to barf on it much earlier already).
> Should just create one by hand, or is there an option in menuconfig that
> needs to be set ?
You can create lib, proc, root and tmp by hand, but then you have to do
a 'make clean' to make sure they're actually in the target. So you should
probably also create them in the target as a quick verification if that
solves the issue for you.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-10-23 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 19:30 [Buildroot] No proc mounted Naitik Amin
2013-10-22 21:15 ` Peter Korsgaard
2013-10-23 12:56 ` Naitik Amin
2013-10-23 17:17 ` Arnout Vandecappelle
2013-10-23 17:21 ` Naitik Amin
2013-10-23 17:23 ` Arnout Vandecappelle
2013-10-23 17:27 ` Naitik Amin
2013-10-23 17:39 ` Arnout Vandecappelle [this message]
2013-10-23 21:26 ` Naitik Amin
2013-10-23 21:36 ` Arnout Vandecappelle
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=526809BF.5030500@mind.be \
--to=arnout@mind.be \
--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