From: "Måns Rullgård" <mans@mansr.com>
To: Jan Stary <hans@stare.cz>
Cc: sox-devel@lists.sourceforge.net
Subject: Re: Build system cleanup
Date: Fri, 21 Aug 2020 18:08:27 +0100 [thread overview]
Message-ID: <yw1x7dtsncz8.fsf@mansr.com> (raw)
In-Reply-To: <20200821152130.GA6847@www.stare.cz> (Jan Stary's message of "Fri, 21 Aug 2020 17:21:31 +0200")
Jan Stary <hans@stare.cz> writes:
> On Aug 21 17:16:12, hans@stare.cz wrote:
>> > checking for magic.h... no
>> > checking for zlib.h... yes
>> > checking for uncompress in -lz... yes
>> > checking for png.h... no
>> > checking for mad.h... no
>> > checking for id3tag.h... no
>> > checking for lame/lame.h... no
>> > checking for lame.h... no
>> >
>> > $ pkg_info -L lame | grep .h$
>> > /usr/local/include/lame/lame.h
>> >
>> > OpenBSD installs third-party packages into /usr/local/,
>> > but the configure script does not look there; it porbably
>> > only searches in /usr, because that's where linux distributions
>> > install their packages. (I'm not saying it should
>> > -- I will test the same with -I added to the CPPFLAGS,
>> > as the OpenBSD port of SoX does.)
>>
>> Running ./configure with CPPFLAGS and LDFLAGS,
>> so that the headers and libraries are found,
>> as per ./configure --help:
>>
>> LDFLAGS linker flags, e.g. -L<lib dir>
>> if you have libraries in a nonstandard directory <lib dir>
>>
>> CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir>
>> if you have headers in a nonstandard directory <include dir>
>>
>> I am looking at png as an example.
>>
>> With plain ./configure , png.h (which is /usr/local/include/png.h)
>> is not found, as described above.
>>
>> checking for png.h... no
>>
>> With ./configure CPPFLAGS='-I/usr/local/include' the png.h header is found,
>> but the library is not, unsurprisingly. But:
>>
>> $ ./configure CPPFLAGS='-I/usr/local/include'
>> [...]
>> checking for png.h... yes
>> checking for png_set_rows in -l101... no
>>
>> I have no idea how the -l101 got there.
>
> not sure if it has anything to do with it, but:
>
> autom4te.cache/output.0: HAVE_LIBLTDL=${with_libltdl:-101}
> autom4te.cache/output.0: HAVE_MAGIC=${with_magic:-101}
> autom4te.cache/output.0: HAVE_PNG=${with_png:-101}
> autom4te.cache/output.0: HAVE_MAD=${with_mad:-101}
> autom4te.cache/output.0: HAVE_ID3TAG=${with_id3tag:-101}
> autom4te.cache/output.0: HAVE_LAME=${with_lame:-101}
> autom4te.cache/output.0: HAVE_TWOLAME=${with_twolame:-101}
> autom4te.cache/output.0: HAVE_LIBGSM=${with_libgsm:-101}
> autom4te.cache/output.0: HAVE_OPENCORE_AMRWB=${with_opencore_amrwb:-101}
> autom4te.cache/output.0: HAVE_VO_AMRWBENC=${with_vo_amrwbenc:-101}
> autom4te.cache/output.0: HAVE_OPENCORE_AMRNB=${with_opencore_amrnb:-101}
> autom4te.cache/output.0: HAVE_LIBSNDFILE=${with_libsndfile:-101}
Fixed.
--
Måns Rullgård
_______________________________________________
SoX-devel mailing list
SoX-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sox-devel
next prev parent reply other threads:[~2020-08-21 17:08 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 20:40 Build system cleanup Måns Rullgård
2020-08-20 20:40 ` Wolfgang Stoeggl via SoX-devel
2020-08-20 21:22 ` Måns Rullgård
2020-08-20 22:15 ` Wolfgang Stoeggl via SoX-devel
2020-08-21 8:24 ` Jan Stary
2020-08-21 8:16 ` Jan Stary
2020-08-21 8:31 ` Jan Stary
2020-08-21 10:28 ` Måns Rullgård
2020-08-21 12:24 ` Jan Stary
2020-08-21 12:46 ` Måns Rullgård
2020-08-21 8:49 ` Jan Stary
2020-08-21 10:33 ` Måns Rullgård
2020-08-21 12:49 ` Jan Stary
2020-08-21 12:50 ` Jan Stary
2020-08-21 13:32 ` Måns Rullgård
2020-08-21 14:09 ` Jan Stary
2020-08-21 11:15 ` Måns Rullgård
2020-08-21 14:04 ` Jan Stary
2020-08-21 14:47 ` Måns Rullgård
2020-08-21 19:26 ` Wolfgang Stoeggl
2020-08-21 20:20 ` Jan Stary
2020-08-21 15:16 ` Jan Stary
2020-08-21 15:21 ` Jan Stary
2020-08-21 17:08 ` Måns Rullgård [this message]
2020-08-21 17:43 ` Jan Stary
2020-08-21 17:52 ` Måns Rullgård
2020-08-21 17:57 ` Jan Stary
2020-08-21 20:17 ` Jan Stary
2020-08-21 20:45 ` Jan Stary
2020-08-21 21:43 ` Måns Rullgård
2020-08-22 8:17 ` Jan Stary
2020-08-22 10:10 ` Måns Rullgård
2020-08-22 15:35 ` Jan Stary
2020-08-22 15:44 ` Jan Stary
2020-08-22 20:54 ` Måns Rullgård
2020-08-23 14:07 ` Jan Stary
2020-08-23 17:13 ` Måns Rullgård
2020-08-23 19:46 ` Jan Stary
2020-08-24 11:04 ` Måns Rullgård
2020-08-24 11:19 ` Jan Stary
2020-08-27 9:38 ` Jan Stary
2020-08-27 10:53 ` Måns Rullgård
2020-08-23 21:55 ` Jan Stary
2020-08-24 6:56 ` Jan Stary
2020-08-27 9:40 ` Jan Stary
2020-08-27 11:08 ` Måns Rullgård
2020-08-27 11:37 ` Jan Stary
2020-08-27 11:53 ` Måns Rullgård
2020-08-27 13:05 ` Jan Stary
2020-08-27 13:31 ` Måns Rullgård
2020-08-27 14:10 ` Jan Stary
2020-08-27 14:38 ` Jan Stary
2020-08-27 15:11 ` Måns Rullgård
2020-08-27 17:41 ` Jan Stary
2020-08-27 18:50 ` Måns Rullgård
2020-08-27 19:18 ` Jan Stary
2020-08-28 4:54 ` Jan Stary
2020-08-28 9:13 ` Måns Rullgård
2020-08-24 12:19 ` Måns Rullgård
2020-08-24 14:43 ` Jan Stary
2020-08-24 14:59 ` Måns Rullgård
2020-08-27 9:44 ` Jan Stary
2020-08-27 11:08 ` Måns Rullgård
2020-08-24 17:22 ` Måns Rullgård
2020-08-22 15:43 ` Jan Stary
2020-08-22 15:48 ` Jan Stary
2020-08-24 12:18 ` Jan Stary
2020-08-24 12:27 ` Måns Rullgård
2020-08-24 13:16 ` Jan Stary
2020-08-24 14:15 ` Måns Rullgård
2020-08-27 9:52 ` Jan Stary
2020-08-27 11:10 ` Måns Rullgård
-- strict thread matches above, loose matches on Subject: below --
2020-08-21 8:52 Jan Stary
2020-08-21 10:36 ` Måns Rullgård
2020-08-21 12:22 ` Jan Stary
2020-08-21 12:27 ` Måns Rullgård
2020-08-27 9:21 Jan Stary
2020-08-27 10:54 ` Jan Stary
2020-08-27 11:52 ` Måns Rullgård
2020-08-27 12:40 ` Jan Stary
2020-08-27 12:44 ` Jan Stary
2020-08-27 12:45 ` Måns Rullgård
2020-08-27 17:45 ` Jan Stary
2020-08-27 18:59 ` Måns Rullgård
2020-08-27 19:51 ` Jan Stary
2020-08-27 20:01 ` Jan Stary
2020-08-28 9:21 ` Måns Rullgård
2020-08-28 9:35 ` Jan Stary
2020-08-28 9:43 ` Måns Rullgård
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=yw1x7dtsncz8.fsf@mansr.com \
--to=sox-devel@lists.sourceforge.net \
--cc=hans@stare.cz \
/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).