| Summary: | alsa-lib headers problem that prevents to compile alsa dependent projects | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Juan <jrmcorreo-linux> |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | minor | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2015.02 | ||
| Target Milestone: | 2015.05 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: |
alsa-utils compilation errors
alsa-lib config log kernel config buildroot config config for S3C2440 (ARM920t) with ALSA kernel config for S3C2440 (ARM920t) with ALSA |
||
|
Description
Juan
2015-04-22 11:18:25 UTC
Can you post the defconfig you use, so we can try to reproduce it? I'm sorry for the delay as other matters nedded my attention. I'll attach defconfig file from kernel and alsa-lib. Created attachment 6026 [details]
alsa-lib config log
Created attachment 6031 [details]
kernel config
I attach buildroot config too. Created attachment 6036 [details]
buildroot config
The Buildroot .config you provided does not have alsa-utils enabled, so it is not possible that you got this error. Also, can you confirm that you get the error after a full "make clean all" cycle? I've just tried building the following defconfig, which includes the amidi alsa-utils, and it builds fine: BR2_arm=y BR2_TOOLCHAIN_EXTERNAL=y BR2_TOOLCHAIN_EXTERNAL_CUSTOM=y BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/tarballs/br-arm-full-2015.02.tar.bz2" BR2_TOOLCHAIN_EXTERNAL_HEADERS_3_18=y BR2_TOOLCHAIN_EXTERNAL_LOCALE=y # BR2_TOOLCHAIN_EXTERNAL_HAS_THREADS_DEBUG is not set BR2_TOOLCHAIN_EXTERNAL_INET_RPC=y BR2_TOOLCHAIN_EXTERNAL_CXX=y BR2_INIT_NONE=y BR2_SYSTEM_BIN_SH_NONE=y # BR2_PACKAGE_BUSYBOX is not set BR2_PACKAGE_ALSA_UTILS=y # BR2_PACKAGE_ALSA_UTILS_ALSACTL is not set # BR2_PACKAGE_ALSA_UTILS_ALSAMIXER is not set BR2_PACKAGE_ALSA_UTILS_AMIDI=y # BR2_TARGET_ROOTFS_TAR is not set Can you give more details? Also, please reproduce with the official Buildroot, without any patches. We cannot debug modified versions of Buildroot for which we don't have the source code. Hi Thomas, First of all thank you for your help. About the alsa-utils option, forgive me if it wasn't unchecked but I've copied the config several days after my post and I'm not able to remember now when it was modified for last time, I'll check and try to recompile again after a "make clean all". About openjdk and patches, I've included the openjdk package following the usual way (and the manual) to the official buildroot distribution, and the patches are applied only if openjdk is compiled. As I said, I'll try again and will post here the result as soon as possible. Hi Thomas, Yesterday I've made a rebuild with success after a "make clean". First I built alsa-lib and alsa-utils, then openjdk with success too (but with an installation error after compiling that I'll try to solve shortly in time). I attach the right buildrooot and kernel configs here. When the installation problem of openjdk could be solved, and the binaries tested, if possible in two different ARM SoC (ARM920t and Cortex A7), I'll send/post the patches and makefile to the contrib address/URL. Thank you for your help Juan Created attachment 6051 [details]
config for S3C2440 (ARM920t) with ALSA
Correct configuration.
Created attachment 6056 [details]
kernel config for S3C2440 (ARM920t) with ALSA
Correct configuration.
The Buildroot configuration you provided builds just fine (I've only disabled the kernel, but it's irrelevant to the alsa-utils problem). And you also say that you managed to build alsa-utils successfully. So: what is the bug ? As you said, at last it worked fine. I can only say that now it works and before not. I think the problem was related about make clean command, that didn't cleaned properly the compile environment. The first time I compiled alsa was in order to compile openjdk, and I've applied both at once. This time I've compiled first buildroot with alsa, then I added openjdk after. Sincerely, I thought that it was a bug because after applying a make clean command and try to compile only alsa didn't worked fine, but finally it worked... and worked without removing competely the buildroot environment I'm using since the begining. If you can't reproduce it and don't consider it as a bug, then is not a bug and probably was caused after introducing a new package not in the official/mainstream release. Problem no longer reproducible. Might have been caused by a lack of a full rebuild (i.e "make clean all"). |