From: Ossy <ossy1980@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] squashfs-tools do not compile
Date: Thu, 17 Jun 2010 21:57:42 +0200 [thread overview]
Message-ID: <4C1A7E36.2030105@gmx.net> (raw)
In-Reply-To: <4C194BD2.3060600@gmx.net>
Hi mailinglist,
Is someone one able to confirm, that squashfstools cannot be linked for
arm? Please find attached my configurations.
Kind regards,
Marcus
Am 17.06.2010 00:10, schrieb Ossy:
> Dear buildrootmailinglist,
>
> The squashfs-tools do not compile. I use arm926t as build target.
> I haven't found a bug in the database.
>
> Kind regards,
> Marcus
>
>
> /home/ossy/buildroot/buildroot-dev/output/staging/usr/bin/arm-unknown-linux-uclibcgnueabi-gcc
> -L/home/ossy/buildroot/buildroot-dev/output/st
> aging/lib -L/home/ossy/buildroot/buildroot-dev/output/staging/usr/lib
> --sysroot=/home/ossy/buildroot/buildroot-dev/output/staging/ mksquashf
> s.o read_fs.o sort.o swap.o pseudo.o -lz -lpthread -lm -o mksquashfs
> mksquashfs.o: In function `initialise_threads':
> mksquashfs.c:(.text+0x1d74): undefined reference to `get_nprocs'
> collect2: ld returned 1 exit status
> make[1]: *** [mksquashfs] Fehler 1
> make[1]: Leaving directory
> `/home/ossy/buildroot/buildroot-dev/output/build/squashfs-4.0/squashfs-tools'
>
> make: ***
> [/home/ossy/buildroot/buildroot-dev/output/build/squashfs-4.0/.stamp_built]
> Fehler 2
> ossy at debian-virtual:~/buildroot/buildroot-dev$
>
> ossy at debian-virtual:~/buildroot/buildroot-dev$ cat .git/FETCH_HEAD
> 5fd095b3748115d7cbe89524332e4b310550b7c3 branch 'master' of
> http://git.buildroot.net/buildroot
> ossy at debian-virtual:~/buildroot/buildroot-dev$
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config-buildroot
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100617/0b895321/attachment-0004.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config-busybox
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100617/0b895321/attachment-0005.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: config-uclibc
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100617/0b895321/attachment-0006.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: FETCH_HEAD
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100617/0b895321/attachment-0007.ksh>
next prev parent reply other threads:[~2010-06-17 19:57 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 [this message]
2010-06-17 20:48 ` Peter Korsgaard
2010-06-17 21:35 ` Ossy
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=4C1A7E36.2030105@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.