From: K.Fetscher@t-online.de (Klaus Fetscher)
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Cross Compile Problems
Date: Wed, 10 Nov 2004 08:28:21 +0100 [thread overview]
Message-ID: <4191C315.7050206@fetron.de> (raw)
In-Reply-To: <s5h3bzjs9hr.wl@alsa2.suse.de>
>>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
next prev parent reply other threads:[~2004-11-10 7:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 22:11 Cross Compile Problems Klaus Fetscher
2004-11-09 8:38 ` Takashi Iwai
2004-11-10 7:28 ` Klaus Fetscher [this message]
2004-11-10 9:52 ` Takashi Iwai
2004-11-11 22:25 ` Klaus Fetscher
2004-11-12 10:51 ` Takashi Iwai
2004-11-12 12:35 ` Klaus Fetscher
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=4191C315.7050206@fetron.de \
--to=k.fetscher@t-online.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.