From: John Rigg <aldev@jrigg.co.uk>
To: alsa-devel@alsa-project.org
Subject: alsa-utils-1.0.24.2 won't compile on x86_64 - CoreFoundation error
Date: Sun, 22 Jan 2012 21:19:47 +0000 [thread overview]
Message-ID: <20120122211947.GA3594@localhost0.localdomain> (raw)
Apologies if this should have gone to alsa-user instead, but I've
just tried compiling alsa-utils-1.0.24.2 on a Debian testing amd64 system,
and configure gave a list of errors related to CoreFoundation.
There were several similar to this in config.log:
...
configure:4589: checking for CFPreferencesCopyAppValue
configure:4607: gcc -o conftest -g -O2 conftest.c -Wl,-framework -Wl,CoreFoundation >&5
conftest.c:11:42: fatal error: CoreFoundation/CFPreferences.h: No such file or directory
compilation terminated.
...
I ran ./configure with default settings.
Kernel is 3.2.1 compiled for k8 from kernel.org source.
alsa-lib-1.0.24.1 compiled and installed sucessfully.
Possibly a stupid question, but why is it checking for CoreFoundation
on a Linux system?
John
next reply other threads:[~2012-01-22 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-22 21:19 John Rigg [this message]
2012-01-22 21:33 ` alsa-utils-1.0.24.2 won't compile on x86_64 - CoreFoundation error Clemens Ladisch
2012-01-23 10:15 ` Ozan Çağlayan
2012-01-23 15:48 ` John Rigg
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=20120122211947.GA3594@localhost0.localdomain \
--to=aldev@jrigg.co.uk \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).