From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: buildroot@busybox.net
Subject: [Buildroot] makedevs: line 49: regular file (...) buildroot/output/target/usr/share/udhcpc/default.script does not exist: No such file or directory
Date: Mon, 26 Jul 2010 14:32:45 +0100 [thread overview]
Message-ID: <1280151165.31502.6.camel@segulix> (raw)
In-Reply-To: <20100726082816.7a1bd8d1@surf>
On Mon, 2010-07-26 at 08:28 +0200, Thomas Petazzoni wrote:
> Hello,
>
> On Mon, 26 Jul 2010 04:48:09 +0100
> Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> wrote:
>
> > I got this error too , with buildroot-2010.05.
>
> Which error ?
Well error is in subject (Can't get Buildrooot to finish):
makedevs: line 49: regular file (...)
buildroot/output/target/usr/share/udhcpc/default.script does not exist:
No such file or directory
>
> > After read some threads in this mailing list is this some error ,
> > to work around I done:
> > cd output/target/usr/share
> > ln -s ../../../../target/generic/target_skeleton/usr/share/udhcpc
> >
> > and build rootfs , is this correct ? the target is a mips32r2 .
>
> Maybe, but as you haven't copy/pasted the error, it's hard to say :-)
>
> Regards,
>
> Thomas
--
S?rgio M. B.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3293 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100726/29584fb9/attachment.bin>
next prev parent reply other threads:[~2010-07-26 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 3:48 [Buildroot] makedevs: line 49: regular file (...) buildroot/output/target/usr/share/udhcpc/default.script does not exist: No such file or directory Sergio Monteiro Basto
2010-07-26 6:28 ` Thomas Petazzoni
2010-07-26 13:32 ` Sergio Monteiro Basto [this message]
2010-07-26 13:49 ` Thomas Petazzoni
2010-07-26 14:31 ` Sergio Monteiro Basto
2010-07-27 3:15 ` Sergio Monteiro Basto
2010-07-28 19:02 ` Sergio Monteiro Basto
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=1280151165.31502.6.camel@segulix \
--to=sergio@sergiomb.no-ip.org \
--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