From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] squashfs-tools do not compile
Date: Thu, 17 Jun 2010 23:35:04 +0200 [thread overview]
Message-ID: <4C1A9508.3010507@gmx.net> (raw)
In-Reply-To: <87r5k5bd1w.fsf@macbook.be.48ers.dk>
Am 17.06.2010 22:48, schrieb Peter Korsgaard:
>>>>>> "Ossy" == Ossy<ossy1980@gmx.net> writes:
>
> Ossy> Dear buildrootmailinglist,
> Ossy> The squashfs-tools do not compile. I use arm926t as build target.
> Ossy> I haven't found a bug in the database.
>
> Are you sure you want to build squashfs-tools FOR your target? Normally
> you just create filesystems on your host (E.G. using buildroot), and
> then read them on the target. The squashfs package is to get mksquashfs
> / unsquashfs to run on the target.
>
> Anyway, the issue was that squashfs-tools used the GNU extension
> get_nprocs() - I have fixed it in git (dfa2a513e).
Yes, you are right. Once I would have built the squash-rootfs I won't
need to make a squashfs anymore. But nevertheless I'm on the safe side
if I like to create one on a free mtd-block in some unusual situation.
prev parent reply other threads:[~2010-06-17 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 22:10 [Buildroot] squashfs-tools do not compile Ossy
2010-06-17 19:57 ` Ossy
2010-06-17 20:48 ` Peter Korsgaard
2010-06-17 21:35 ` Ossy [this message]
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=4C1A9508.3010507@gmx.net \
--to=ossy1980@gmx.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