From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] List of working packages for ARM
Date: Wed, 21 Jan 2009 21:07:43 +0100 [thread overview]
Message-ID: <1232568463.11888.74.camel@elrond.atmel.com> (raw)
In-Reply-To: <87skncsurl.fsf@macbook.be.48ers.dk>
ons 2009-01-21 klockan 13:34 +0100 skrev Peter Korsgaard:
> >>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
>
> Ulf> Using gcc-4.2.4, bu-2.18, uclibc-0.9.30
> Ulf> wchar, largefile,ipv6, NWFPE
>
> Again, it would be neat to have such a list with the toolchain config
> that really matters.
You have it now, and it is easy to generate.
"scripts/buildall.sh" will do it for you
by running "scripts/mkpkg" on all listed packages
Calling it "buildall" is not 100% correct,
since a few packages are not built.
database and qtopia, X windows related packages
are notable exceptions as well as java and games.
The comments after OK/FAIL etc, are manually added.
buildall.sh creates the log directory and
then the log/OK and log/FAIL.
log/FAIL contains one log file per built package.
>
> Ulf> nmk valgrind DISABLED x86 specific
>
> i386/x86-64/powerpc
>
>
> Ulf> mk libconfuse FAIL "error: 'input' defined but not used"
>
> How is that an error?
>
Ask the compiler writer, I was also confused, but that is
maybe appropriate for a package named "libconfuse" ;-)
There is a comment just before the "error".
"cc1: warnings being treated as errors" so the maintainer
wants to make dead sure that the lexer.c is real clean.
> Ulf> nmk database DISABLED Need to enter subdirectory
>
> ? So you didn't test sqlite/mysql?
No, I just did an ls of package to start with, and never bothered to
update, There is a significant number of packages that does not build
so until I run out of FAILs, this just adds compile time.
Feel free to add package
>
> Ulf> mk libcurl FAIL "checking for socklen_t
> Ulf> equivalent... unknown"
>
> I have recently built that on armv4l without problems.
Since I am not running a regular make, problems could occur,
If the dependencies in the Makefile are incomplete.
The make maybe runs in the correct order for other reasons.
>
> Ulf> mk madplay OK "Depends on python"
> Ulf> mk mpg123 FAIL "Depends on python"
>
> That sounds unlikely - Do you have a build log?
Have build logs for everything.
For the release toochain, the mpg123 build
aborts with a segmentation fault.
BR
Ulf Samuelsson
next prev parent reply other threads:[~2009-01-21 20:07 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 7:42 [Buildroot] List of working packages for ARM Ulf Samuelsson
2009-01-21 8:36 ` Sven Neumann
2009-01-21 8:53 ` Peter Korsgaard
2009-01-21 11:38 ` Ulf Samuelsson
2009-01-21 8:52 ` Peter Korsgaard
2009-01-21 11:40 ` Ulf Samuelsson
2009-01-21 12:28 ` Peter Korsgaard
2009-01-21 17:52 ` Ulf Samuelsson
2009-01-21 20:14 ` Peter Korsgaard
2009-01-21 21:25 ` Ulf Samuelsson
2009-01-21 20:22 ` Peter Korsgaard
2009-01-21 21:32 ` Ulf Samuelsson
2009-01-21 20:58 ` Peter Korsgaard
2009-01-21 21:52 ` Ulf Samuelsson
2009-01-21 11:33 ` Gustavo Zacarias
2009-01-21 12:34 ` Peter Korsgaard
2009-01-21 20:07 ` Ulf Samuelsson [this message]
2009-01-21 20:12 ` Peter Korsgaard
[not found] ` <200901221429040909225@163.com>
2009-01-22 7:03 ` [Buildroot] Does anyone have done truecrypt on buildroot? Daniel
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=1232568463.11888.74.camel@elrond.atmel.com \
--to=ulf.samuelsson@atmel.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