From: mike <wtf62@rovoreed.com>
To: buildroot@busybox.net
Subject: [Buildroot] genext2fs problem
Date: Sun, 15 Apr 2007 18:33:58 +0000 [thread overview]
Message-ID: <1176662039.1050.7.camel@glynys> (raw)
I've started getting a problem with genext2fs, where it complains that a
file is not a directory. In the example below it flags up on
pcmcia_core.o, but each time I 'make' it reports a different file.
I don't know what is going on, or why this has just started. Can anyone
help ?
# Use fakeroot so genext2fs believes the previous fakery
GENEXT2_REALSIZE=`LANG=C du -l -s -c
-k /home/mike/buildroot/build_i386/root | grep total | sed -e
"s/total//"`; \
GENEXT2_ADDTOROOTSIZE=`if [ $GENEXT2_REALSIZE -ge 20000 ] ; then echo
16384; else echo 2400; fi`; \
GENEXT2_SIZE=`expr $GENEXT2_REALSIZE + $GENEXT2_ADDTOROOTSIZE`; \
GENEXT2_ADDTOINODESIZE=`find /home/mike/buildroot/build_i386/root | wc
-l`; \
GENEXT2_INODES=`expr $GENEXT2_ADDTOINODESIZE + 400`; \
set -x; \
/home/mike/buildroot/build_i386/staging_dir/usr/bin/fakeroot \
-i /home/mike/buildroot/build_i386/staging_dir/fakeroot.env \
-s /home/mike/buildroot/build_i386/staging_dir/fakeroot.env -- \
/home/mike/buildroot/build_i386/genext2fs-1.3/genext2fs \
-b $GENEXT2_SIZE \
-i $GENEXT2_INODES \
-d /home/mike/buildroot/build_i386/root \
/home/mike/buildroot/rootfs.i386.ext2
+ /home/mike/buildroot/build_i386/staging_dir/usr/bin/fakeroot
-i /home/mike/buildroot/build_i386/staging_dir/fakeroot.env
-s /home/mike/buildroot/build_i386/staging_dir/fakeroot.env
-- /home/mike/buildroot/build_i386/genext2fs-1.3/genext2fs -b 7756 -i
969
-d /home/mike/buildroot/build_i386/root /home/mike/buildroot/rootfs.i386.ext2
/home/mike/buildroot/build_i386/genext2fs-1.3/genext2fs: pcmcia_core.o:
Not a directory
make: *** [/home/mike/buildroot/rootfs.i386.ext2] Error 1
[mike at glynys
buildroot]$
reply other threads:[~2007-04-15 18:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1176662039.1050.7.camel@glynys \
--to=wtf62@rovoreed.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