From: Sven Joachim <svenjoac@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Ergus <spacibba@aol.com>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: Deprecation message in Arch Linux.
Date: Wed, 28 Aug 2019 19:45:19 +0200 [thread overview]
Message-ID: <87woexjia8.fsf@turtle.gmx.de> (raw)
In-Reply-To: <c8f70a5b-1524-48ca-f2d0-221e65106044@cs.ucla.edu> (Paul Eggert's message of "Wed, 28 Aug 2019 10:19:14 -0700")
On 2019-08-28 10:19 -0700, Paul Eggert wrote:
> Ergus wrote:
>> In file included from ../../src/sound.c:78:
>> /usr/include/asoundlib.h:1:2: warning: #warning This header is
>> deprecated, use <alsa/asoundlib.h> instead. [-Wcpp]
>> 1 | #warning This header is deprecated, use <alsa/asoundlib.h> instead.
>>
>> It shouldn't be an issue, but maybe we should fix it.
>
> Sounds like a problem with your Arch Linux configuration. The command:
>
> pkg-config --cflags "alsa >= 1.0.0"
>
> should output something like "-I/usr/include/alsa" so that the
> "#include <asoundlib.h>" grabs /usr/include/alsa/asoundlib.h instead
> of /usr/include/asoundlib.h. You might look into that, and if you
> still think it's an Emacs configure problem please file a bug report.
This was a deliberate change in alsa-lib 1.1.9, as "-I/usr/include/alsa"
is considered dangerous due to possible namespace conflicts[1]. Perhaps
Emacs' configure script should test for <alsa/asoundlib.h> first, and
only try <asoundlib.h> if that fails? Right now it's done the other way
around.
Cheers,
Sven
https://git.alsa-project.org/?p=alsa-lib.git;a=commit;h=fc0e54c3cc6ad48d12d2cdad18df4473c559a448
next prev parent reply other threads:[~2019-08-28 17:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 9:41 Deprecation message in Arch Linux Ergus
2019-08-28 17:19 ` Paul Eggert
2019-08-28 17:45 ` Sven Joachim [this message]
2019-08-28 18:38 ` Paul Eggert
2019-08-28 18:49 ` Eli Zaretskii
2019-08-28 19:08 ` Sven Joachim
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87woexjia8.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=spacibba@aol.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).