From: Nigel Kukard <nkukard@lbsd.net>
To: buildroot@busybox.net
Subject: [Buildroot] Error when compiling Buildroot to create .iso (cannot stat /.../i386-linux-2.6.24-20
Date: Fri, 04 Apr 2008 06:26:37 +0000 [thread overview]
Message-ID: <1207290397.2660.1.camel@nigel-x60> (raw)
In-Reply-To: <BLU136-W53B177A876BAF0750E74CCC3F60@phx.gbl>
On Thu, 2008-04-03 at 22:36 -0700, Ma Andrew wrote:
> Hello Nigel,
>
> I didn't have a chance to compile from a fresh checkout copy, and only do a "svn update" when I see your email. The copy that I compiled is checked out from yesterday. The revision that I am in is 21630. I am still suffering from the same problem if the sym link is removed.
Nuke all the files in the destination dir, if the symlink is there its
not going to copy over the dereferenced file in any case.
So nuke all the files, and rebuild.
-N
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://busybox.net/lists/buildroot/attachments/20080404/51726774/attachment.pgp
next prev parent reply other threads:[~2008-04-04 6:26 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
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 [this message]
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=1207290397.2660.1.camel@nigel-x60 \
--to=nkukard@lbsd.net \
--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