From: Hamish Moffatt <hamish@cloud.net.au>
To: buildroot@busybox.net
Subject: [Buildroot] alsa-lib error
Date: Mon, 22 Dec 2008 12:16:50 +1100 [thread overview]
Message-ID: <20081222011650.GA18859@cloud.net.au> (raw)
In-Reply-To: <20081219184804.186620@gmx.net>
On Fri, Dec 19, 2008 at 07:48:04PM +0100, Matt Wood wrote:
> Has anyone tried to compile alsa-lib lately? Just tried and got the following error:
>
> /usr/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-gcc -Os -I/usr/arm/buildroot/build_arm/staging_dir/usr/include -I/usr/arm/buildroot/build_arm/staging_dir/include --sysroot=/usr/arm/buildroot/build_arm/staging_dir/ -isysroot /usr/arm/buildroot/build_arm/staging_dir -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -shared .libs/hda.o .libs/sbasedl.o -Wl,--rpath -Wl,/usr/arm/buildroot/build_arm/alsa-lib-1.0.18/src/.libs -L/usr/arm/buildroot/build_arm/staging_dir/lib -L/usr/arm/buildroot/build_arm/staging_dir/usr/lib -lm ../../../src/.libs/libasound.so -mabi=aapcs-linux -Wl,-soname -Wl,smixer-hda.so -o .libs/smixer-hda.so
> In file included from /usr/include/python2.5/Python.h:62,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> from python.c:22:
> /usr/include/python2.5/pyport.h:761:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)."
> /usr/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ar cru .libs/smixer-hda.a hda.o sbasedl.o
> /usr/arm/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ranlib .libs/smixer-hda.a
>
> Any ideas?
It appears to be using files from your host Python installation. Unless
you need alsa-lib to build Python modules there might be a configure
flag to disable it, or set the correct path etc?
Hamish
--
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>
prev parent reply other threads:[~2008-12-22 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 18:48 [Buildroot] alsa-lib error Matt Wood
2008-12-22 1:16 ` Hamish Moffatt [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=20081222011650.GA18859@cloud.net.au \
--to=hamish@cloud.net.au \
--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