From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/multimedia/alsa-utils
Date: Wed, 04 Mar 2009 14:34:19 +0100 [thread overview]
Message-ID: <87k575h0o4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49AE81A9.2090605@atmel.com> (Hans-Christian Egtvedt's message of "Wed\, 04 Mar 2009 14\:27\:05 +0100")
>>>>> "Hans-Christian" == Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com> writes:
Hi,
>> config BR2_PACKAGE_ALSA_UTILS_APLAY
>> bool "aplay"
>> - select BR2_LARGEFILE
>> + depends on BR2_LARGEFILE
>> depends on BR2_PACKAGE_ALSA_UTILS
>> +comment "aplay requires a toolchain with LARGEFILE support"
>> + depends on !BR2_LARGEFILE
>> +
>> config BR2_PACKAGE_ALSA_UTILS_ARECORD
>> bool "arecord"
>> depends on BR2_PACKAGE_ALSA_UTILS
>>
Hans-Christian> I guess this also depends on LARGEFILE, arecord is
Hans-Christian> just a symlink to aplay.
Ok, but why do we have the config option if it's just a symlink?
.. checking the .mk - Ahh, we always build everything and the config
options is just to decide what gets copied to the target, so I guess
alsa-utils is broken on !BR2_LARGEFILE or the depends was wrong to
begin with.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-03-04 13:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 13:22 [Buildroot] svn commit: trunk/buildroot/package/multimedia/alsa-utils jacmet at uclibc.org
2009-03-04 13:27 ` Hans-Christian Egtvedt
2009-03-04 13:34 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-04 14:17 jacmet at uclibc.org
2009-03-04 13:22 jacmet at uclibc.org
2009-02-19 16:04 jacmet at uclibc.org
2009-01-22 23:06 ulf at uclibc.org
2009-01-16 22:06 ulf at uclibc.org
2008-12-04 16:10 egtvedt at uclibc.org
2008-12-04 16:28 ` Peter Korsgaard
2008-12-04 16:34 ` Hans-Christian Egtvedt
2008-12-04 16:45 ` Peter Korsgaard
2008-12-04 16:10 egtvedt at uclibc.org
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=87k575h0o4.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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