From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Cc: linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hverkuil@xs4all.nl
Subject: Re: [v4l-utils PATCH 1/2] v4l: libv4l1, libv4l2: Use $(mkdir_p) instead of deprecated $(MKDIR_P)
Date: Mon, 1 Feb 2016 15:14:53 +0200 [thread overview]
Message-ID: <56AF5A4D.4020500@linux.intel.com> (raw)
In-Reply-To: <20160201105945.20dd5087@recife.lan>
Hi Mauro,
Mauro Carvalho Chehab wrote:
> Em Mon, 25 Jan 2016 14:41:23 +0200
> Sakari Ailus <sakari.ailus@linux.intel.com> escreveu:
>
>> autoconf thinks $(MKDIR_P) is deprecated. Use $(mkdir_p) instead.
>
> Did you get any troubles with the deprecated macro?
>
> At least here (version 2.69), I don't see any error by using $(MKDIR_P).
I have the same version.
-----8<------
$ autoreconf -vfi
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: AM_GNU_GETTEXT is used, but not
AM_GNU_GETTEXT_VERSION
autoreconf: running: libtoolize --copy --force
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `build-aux'.
libtoolize: copying file `build-aux/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
autoreconf: running: /usr/bin/autoconf --force
autoreconf: running: /usr/bin/autoheader --force
autoreconf: running: automake --add-missing --copy --force-missing
configure.ac:85: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and
its use is discouraged.
configure.ac:85: You should use the Autoconf-provided 'AC_PROG_MKDIR_P'
macro instead,
configure.ac:85: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your
Makefile.am files.
autoreconf: Leaving directory `.'
-----8<------
Perhaps automake version makes a difference. I have 1.14.1 here (Ubuntu
package 1:1.14.1-2ubuntu1 from Ubuntu 14.10).
There are no errors due to this, just a warning.
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2016-02-01 13:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 12:41 [v4l-utils PATCH 0/2] automake fixes Sakari Ailus
2016-01-25 12:41 ` [v4l-utils PATCH 1/2] v4l: libv4l1, libv4l2: Use $(mkdir_p) instead of deprecated $(MKDIR_P) Sakari Ailus
2016-02-01 12:59 ` Mauro Carvalho Chehab
2016-02-01 13:14 ` Sakari Ailus [this message]
2016-01-25 12:41 ` [v4l-utils PATCH 2/2] Fix configure script errors Sakari Ailus
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=56AF5A4D.4020500@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.