Age | Commit message (Collapse) | Author |
|
Even though we pass a -I option to tell alsa-lib to look for Python
includes in the STAGING_DIR, alsa-lib build process still looks in
/usr/include for some stuff, causing bug #321.
This fix is the one suggested by Ulf Samuelsson in bug #321, and
allows to make alsa-lib with Python support to build properly on a 64
bits machine with python-dev installed on the host. Without this fix,
the build fails with exactly the same problem that Ulf reported.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
|
The current version of alsa-lib (1.0.22) does not build when
--disable-pcm is used at configure time. I've reported the issue at
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=4913.
In the mean time, we can prevent the user from not selecting PCM
support by using the following patch.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
|
|
Signed-off-by: William Wagner <will_wagner@carallon.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
|
|
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
|
|
A C library will have been built by the toolchain makefiles, so there is no
need for packages to explicitly depend on uclibc.
Signed-off-by: Will Newton <will.newton@gmail.com>
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
|
|
Closes #191.
|
|
|
|
As reported by Dirk Vermaak and Daniel Mack. Fixes runtime issues with
alsa-lib, see
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-February/014999.html
for details.
|
|
As discussed on the list.
|
|
Tell it where to find the python headers.
|
|
As discussed on the list. I suspect the ARM abi thing isn't needed anymore
now we use the correct abi in the first place, but I'll leave it in until
after the release.
|
|
break, feedback to AVR32 compiler team will be sent
|
|
Thanks to Will Wagner <will_wagner@carallon.com> for reporting and working
with upstream to get it fixed. Patch from alsa-lib.git.
|
|
|
|
selected
|
|
|
|
|
|
|
|
|
|
|
|
Prepare for the merge of audio and video packages. Many packages cannot
properly be assigned to either audio or video, because they have support
for both (libogg, mplayer, vlc).
Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
|