Cross Compile Problems

Cross Compile Problems

[Klaus Fetscher]

Hallo,

I want to use ALSA for my ARM based custom board, but I have the 
following problems.

- I am using a NFS-Root Filesystem for my embedded hardware. I have 
cross compiled the alsa-lib and the alsa-utils with the 
"--PREFIX=/tftpboot/acc-rootfs" . The root filesystem is mounted below 
"/tftpboot/acc-rootfs". When I start the mixer, he want to load the file 
"alsa.conf" with the complete path 
"/tftpboot/acc-rootfs/share/alsa/alsa.conf" . The problem is, that the 
correct path for the ARM CPU is only "/share/alsa/alsa.conf" . Are there 
any options to solve this problem ?

- After temporary copy the files to 
"/tftpboot/acc-rootfs/tftpboot/acc-rootfs/share/alsa/alsa.conf" I get 
the following error:
"ALSA lib control.c:629:(snd_ctl_open_conf) symbol _snd_ctl_hw_open is 
not defined inside (null)"
"amixer: Mixer attach default error: No such device or address"
Is it necessary to add entries to "/share/alsa.conf" or to 
"/etc/asound.conf" or to to ".asoundrc" ?
I couldn't not use "alsaconf" because my shell can't interpret the 
commands "dialog" or "whiptail".
The detection of the card works correct, because I have can see the card 
in the "/proc/asound" directory and also the streams under the 
"/proc/asound/card0" directory.

Thanks

Klaus Fetscher



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Takashi Iwai]

At Mon, 08 Nov 2004 23:11:26 +0100,
Klaus Fetscher wrote:
> 
> Hallo,
> 
> I want to use ALSA for my ARM based custom board, but I have the 
> following problems.
> 
> - I am using a NFS-Root Filesystem for my embedded hardware. I have 
> cross compiled the alsa-lib and the alsa-utils with the 
> "--PREFIX=/tftpboot/acc-rootfs" . The root filesystem is mounted below 
> "/tftpboot/acc-rootfs". When I start the mixer, he want to load the file 
> "alsa.conf" with the complete path 
> "/tftpboot/acc-rootfs/share/alsa/alsa.conf" . The problem is, that the 
> correct path for the ARM CPU is only "/share/alsa/alsa.conf" . Are there 
> any options to solve this problem ?

You can specify datadir, libdir, etc with configure options to
override the default values.

> - After temporary copy the files to 
> "/tftpboot/acc-rootfs/tftpboot/acc-rootfs/share/alsa/alsa.conf" I get 
> the following error:
> "ALSA lib control.c:629:(snd_ctl_open_conf) symbol _snd_ctl_hw_open is 
> not defined inside (null)"
> "amixer: Mixer attach default error: No such device or address"
> Is it necessary to add entries to "/share/alsa.conf" or to 
> "/etc/asound.conf" or to to ".asoundrc" ?

No.  I guess the shared lib file can't be read correctly because of
the installed path.  alsa-lib tries to load symbols with dlopen.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Klaus Fetscher]

>>I want to use ALSA for my ARM based custom board, but I have the 
>>following problems.
>>
>>- I am using a NFS-Root Filesystem for my embedded hardware. I have 
>>cross compiled the alsa-lib and the alsa-utils with the 
>>"--PREFIX=/tftpboot/acc-rootfs" . The root filesystem is mounted below 
>>"/tftpboot/acc-rootfs". When I start the mixer, he want to load the file 
>>"alsa.conf" with the complete path 
>>"/tftpboot/acc-rootfs/share/alsa/alsa.conf" . The problem is, that the 
>>correct path for the ARM CPU is only "/share/alsa/alsa.conf" . Are there 
>>any options to solve this problem ?
>>    
>>
>
>You can specify datadir, libdir, etc with configure options to
>override the default values.
>
>  
>
If I specify datadir or libdir, some files will be installed into that 
directory. So is it necessary to copy these files manual to the exported 
NFS directory ?
I didn't find any solution to specify the options for the different 
directories (--datadir=/dir1.. --libdir-/dir1.." and do a "make install" 
and all files will be on the correct directories.

Thanks,

Klaus



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Takashi Iwai]

At Wed, 10 Nov 2004 08:28:21 +0100,
Klaus Fetscher wrote:
> 
> 
> >>I want to use ALSA for my ARM based custom board, but I have the 
> >>following problems.
> >>
> >>- I am using a NFS-Root Filesystem for my embedded hardware. I have 
> >>cross compiled the alsa-lib and the alsa-utils with the 
> >>"--PREFIX=/tftpboot/acc-rootfs" . The root filesystem is mounted below 
> >>"/tftpboot/acc-rootfs". When I start the mixer, he want to load the file 
> >>"alsa.conf" with the complete path 
> >>"/tftpboot/acc-rootfs/share/alsa/alsa.conf" . The problem is, that the 
> >>correct path for the ARM CPU is only "/share/alsa/alsa.conf" . Are there 
> >>any options to solve this problem ?
> >>    
> >>
> >
> >You can specify datadir, libdir, etc with configure options to
> >override the default values.
> >
> >  
> >
> If I specify datadir or libdir, some files will be installed into that 
> directory. So is it necessary to copy these files manual to the exported 
> NFS directory ?

Hmm, I'm not clear why prefix must be specified in your case.

If you set up the cross compiling environment, usually prefix isn't
needed but you just need to specify the proper compiler, etc.
And, installing to other root system will be done by adding
"DESTDIR=xxx" at make install.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Klaus Fetscher]

Takashi Iwai schrieb:

>Hmm, I'm not clear why prefix must be specified in your case.
>
>If you set up the cross compiling environment, usually prefix isn't
>needed but you just need to specify the proper compiler, etc.
>And, installing to other root system will be done by adding
>"DESTDIR=xxx" at make install.
>
>
>  
>
You are right, I have installed the libraries wrong and now I have 
corrected it. Anyway, I get always the same error result.

I think you are right with your last answer that the shared lib file 
can't be read correctly because of the installed path.

How can I check if the libs are correct ?

Is it correct that I first compile and install the alsa-lib-1.0.7 (with --enable-shared=yes and --enable-static=yes --with-softfloat) and later alsa-utils-1.0.7. Is this correct ?

Thanks,

Klaus




-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Takashi Iwai]

At Thu, 11 Nov 2004 23:25:37 +0100,
Klaus Fetscher wrote:
> 
> Takashi Iwai schrieb:
> 
> >Hmm, I'm not clear why prefix must be specified in your case.
> >
> >If you set up the cross compiling environment, usually prefix isn't
> >needed but you just need to specify the proper compiler, etc.
> >And, installing to other root system will be done by adding
> >"DESTDIR=xxx" at make install.
> >
> >
> >  
> >
> You are right, I have installed the libraries wrong and now I have 
> corrected it. Anyway, I get always the same error result.

Did you remove --prefix at the compilation?

> I think you are right with your last answer that the shared lib file 
> can't be read correctly because of the installed path.
> 
> How can I check if the libs are correct ?

The only place referring to DATADIR is src/conf.c.
Make sure that DATADIR is correctly set in configure (see config
log).

> Is it correct that I first compile and install the alsa-lib-1.0.7
> (with --enable-shared=yes and --enable-static=yes --with-softfloat)
> and later alsa-utils-1.0.7. Is this correct ? 

Unfortunately, you can't build shared and static libraries at the same
time.  See INSTALL for details.

And, yes, build alsa-utils after installing alsa-lib.  In your case,
you'll need to specify --with-alsa-inc-prefix and --with-alsa-prefix
for configure of alsa-utils to specify the path of header and lib
files of the cross-compiled ALSA lib.


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

Re: Cross Compile Problems

[Klaus Fetscher]

Takashi Iwai schrieb:

Thanks Takashi for your help, now it works.

>>Is it correct that I first compile and install the alsa-lib-1.0.7
>>(with --enable-shared=yes and --enable-static=yes --with-softfloat)
>>and later alsa-utils-1.0.7. Is this correct ? 
>>    
>>
>
>Unfortunately, you can't build shared and static libraries at the same
>time.  See INSTALL for details.
>
>  
>
Is it correct, to build the libraries two times (one time shared and one 
time static) ?



Now, I will do the difficult part (ARM and DMA ..).


Thanks

Klaus



-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click