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: Tue, 27 Jul 2010 04:15:46 +0100 [thread overview]
Message-ID: <1280200547.30894.34.camel@segulix> (raw)
In-Reply-To: <1280154696.31502.11.camel@segulix>
On Mon, 2010-07-26 at 15:31 +0100, Sergio Monteiro Basto wrote:
> On Mon, 2010-07-26 at 15:49 +0200, Thomas Petazzoni wrote:
> > Hello,
> >
> > On Mon, 26 Jul 2010 14:32:45 +0100
> > Sergio Monteiro Basto <sergio@sergiomb.no-ip.org> wrote:
> >
> > > > 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):
> >
> > Aah, okay, I missed it.
> >
> > > makedevs: line 49: regular file (...)
> > > buildroot/output/target/usr/share/udhcpc/default.script does not
> > > exist: No such file or directory
> >
> > Can you post your Buildroot .config for us to reproduce the issue ?
>
> ok .config in attach as emtec.config.without qt version 4 .
>
> >
> > > > > 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 :-)
> >
> > In fact, the work around is not correct. You're creating a symbolic
> > link from the target directory to the outside. While this symbolic may
> > work on the development system where Buildroot runs, it will miserably
> > fail on the target system.
>
> oh no,
>
> I successfully build and run bash on my emtec R100 !
Ok , first I move to git version of buildroot, which make xconfig works
and gives a great help.
I think with this main change:
-# BR2_PROGRAM_INVOCATION is not set
+BR2_PROGRAM_INVOCATION=y
Give me the habitability to build libglib2-2.22.5 which give an error
like buildroot/output/build/libglib2-2.22.5/.stamp_configured] Error 1,
(I lost the error message). Which, let me think, that libglib2 also
needs depend on PROGRAM_INVOCATION in .config, like tar and coreutils.
And finally I had successfully made output/images/rootfs.ext2.lzma,
without tricky links and finish the building.
Thanks,
BTW:
I still don't build a kernel image because seems that I don't have a
_defconfig for mipsel. What least I don't found one .
still can't build miniperl, with error:
ext/util/make_ext: line 122: ../../miniperl: No such file or directory
and mplayer gives the error: It seems nobody has ported MPlayer to your
OS or CPU type yet. (which is mipsel)
Thanks,
--
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/20100727/acf8da27/attachment.bin>
next prev parent reply other threads:[~2010-07-27 3:15 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
2010-07-26 13:49 ` Thomas Petazzoni
2010-07-26 14:31 ` Sergio Monteiro Basto
2010-07-27 3:15 ` Sergio Monteiro Basto [this message]
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=1280200547.30894.34.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