From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Setting custom PTXDIST_TEMPDIR for large image gen?
Date: Tue, 9 Apr 2013 20:55:59 +0200 [thread overview]
Message-ID: <20130409185559.GG32214@pengutronix.de> (raw)
In-Reply-To: <OF188E65AB.CCB9ACA5-ONC1257B48.005499AB-C1257B48.0056E751@hytera.de>
Hi,
On Tue, Apr 09, 2013 at 05:49:11PM +0200, Dennis.Herbrich@hytera.de wrote:
> I configured ptxdist 2013.03.0 to generate a rather large (8GB) hd.img for
> me,
> but genext2fs fails:
>
> Creating root.ext2 from working
> dir.../home/herbrich/AEOS2/platform-evoc-x86/sysroot-host/bin/genext2fs:
> couldn't allocate a block (no free space)
> make: *** [/home/herbrich/AEOS2/platform-evoc-x86/images/root.ext2] Error
> 1
>
> Since I had 30+GB free space in my TOPDIR, I went into the lurking depths
> of
> ptxdist and discovered what looked like a hardcoded setting of
> PTXDIST_TEMPDIR
> in the setup_libs_early() function of ptxdist itself:
[...]
> Unfortunately I don't have 8+GB of RAM+swap handy, and I failed to find a
> way to
> cleanly set this variable to a location on my HDD. In retrospect I'm glad
> that
> kernel compilation didn't (yet) die on me with my limited /tmp ramdisk
> space!
>
> So, I guess my questions are:
> 1. How can I reliably generate a large-ish hd.img with limited /tmp space?
> 2. How can I set a different PTXDIST_TEMPDIR?
>
> I am not inclined to accept "Dude, ptxdist is for embedded systems, create
> a
> smaller image already!" as an answer, though, sorry. ;)
This has nothing to do with PTXDIST_TEMPDIR. The images are all created in
platform-XXX/images/. The error means, that the specified size of the
ext2fs (as defined in the platformconfig) is too small.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2013-04-09 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 15:49 Dennis.Herbrich
2013-04-09 18:55 ` Michael Olbrich [this message]
2013-04-09 19:07 ` Erwin Rol
2013-04-10 5:47 ` Michael Olbrich
2013-04-10 5:55 ` Michael Olbrich
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=20130409185559.GG32214@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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