From: "Måns Rullgård" <mans@mansr.com>
To: sox-devel@lists.sourceforge.net
Subject: Re: --without-amrwb --without-amrnb looks for AMR
Date: Sun, 18 Mar 2018 14:49:07 +0000 [thread overview]
Message-ID: <yw1xa7v5igm4.fsf@mansr.com> (raw)
In-Reply-To: <20180317143300.GA62585@www.stare.cz> (Jan Stary's message of "Sat, 17 Mar 2018 15:33:00 +0100")
Jan Stary <hans@stare.cz> writes:
> This is current git (from git://git.code.sf.net/p/sox/code)
> on OpenBSD current/amd64. Configuring SoX with (full output below)
>
> $ ./configure --without-amrwb --without-amrnb \
> CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib
>
> it still seems to look for AMR (and finds the library).
>
> checking opencore-amrwb/dec_if.h usability... yes
> checking opencore-amrwb/dec_if.h presence... yes
> checking for opencore-amrwb/dec_if.h... yes
> checking for D_IF_init in -lopencore-amrwb... yes
> checking opencore-amrnb/interf_dec.h usability... yes
> checking opencore-amrnb/interf_dec.h presence... yes
> checking for opencore-amrnb/interf_dec.h... yes
> checking for Decoder_Interface_init in -lopencore-amrnb... yes
>
> Why is that? Why does SoX try looking for the headers
> and the library when it is explicitly told not to?
Whoever wrote the configure script was lazy. The checks are always
done, but the format support is only built if requested.
--
Måns Rullgård
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
prev parent reply other threads:[~2018-03-18 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-17 14:33 --without-amrwb --without-amrnb looks for AMR Jan Stary
2018-03-18 14:49 ` Måns Rullgård [this message]
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.sourceforge.net/lists/listinfo/sox-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1xa7v5igm4.fsf@mansr.com \
--to=sox-devel@lists.sourceforge.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/sox.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).