[Bug 667293] build: Make sure AC_INCLUDES_DEFAULT is used

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=667293
  GStreamer | gstreamer (core) | git

Tim-Philipp Müller <t.i.m> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |t.i.m at zen.co.uk
     Ever Confirmed|0                           |1

--- Comment #1 from Tim-Philipp Müller <t.i.m at zen.co.uk> 2012-01-05 00:47:51 UTC ---
An informative commit message, hooray!

I was curious why AC_CHECK_HEADER doesn't just default to AC_INCLUDES_DEFAULT
if the argument is not provided. Short snippet from
/usr/share/autoconf/autoconf/headers.m4:

# AC_CHECK_HEADER(HEADER-FILE,
#          [ACTION-IF-FOUND], [ACTION-IF-NOT-FOUND],
#          [INCLUDES])
# ---------------------------------------------------------
# We are slowly moving to checking headers with the compiler instead
# of the preproc, so that we actually learn about the usability of a
# header instead of its mere presence.  But since users are used to
# the old semantics, they check for headers in random order and
# without providing prerequisite headers.  This macro implements the
# transition phase, and should be cleaned up latter to use compilation
# only.
#
# If INCLUDES is empty, then check both via the compiler and preproc.
# If the results are different, issue a warning, but keep the preproc
# result.
#
# If INCLUDES is `-', keep only the old semantics.
#
# If INCLUDES is specified and different from `-', then use the new
# semantics only.

This makes me wonder if there isn't a more proper way..

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.