Thank you very much for replying, Igor. Em 31-07-2013 04:19, Igor Živković escreveu: > On 07/31/2013 05:35 AM, Fernando de Oliveira wrote: >> Igor, I do not know what I did wrong, perhaps nothing, in doubt, sent >> here, instead of -support. >> >> $ autoreconf --version >> autoreconf (GNU Autoconf) 2.69 >> >> Problem and solution: >> >> patch -Np1 -i ../faad2-2.7-mp4ff-1.patch && >> #aclocal: warning: autoconf input should be named 'configure.ac', >> not 'configure.in' >> #configure.in:28: error: 'AM_CONFIG_HEADER': this macro is obsolete. >> # You should use the 'AC_CONFIG_HEADERS' macro instead. >> #/usr/share/aclocal-1.13/obsolete-err.m4:12: AM_CONFIG_HEADER is >> expanded from... >> #configure.in:28: the top level >> #autom4te: /usr/bin/m4 failed with exit status: 1 >> #aclocal: error: echo failed with exit status: 1 >> #autoreconf: aclocal failed with exit status: 1 >> mv -vi configure.in configure.ac && >> sed -i 's/AM_CONFIG_HEADER/AC_CONFIG_HEADERS/' configure.ac && >> autoreconf -fi && >> >> With that, it worked. >> >> Of course, without the patch, no need for autoreconf, configure >> succeeded, too. >> > > I've got: > > $ autoreconf --version > > autoreconf (GNU Autoconf) 2.69 > > $ patch -Np1 -i ../faad2-2.7-mp4ff-1.patch > > patching file common/mp4ff/Makefile.am > > $ autoreconf -fi > > aclocal: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
It seems mine is doing this. > libtoolize: copying file `./ltmain.sh' > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and > libtoolize: rerunning libtoolize, to keep the correct libtool macros > in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > aclocal: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > automake: warning: autoconf input should be named 'configure.ac', not > 'configure.in' > configure.in:12: warning: AM_INIT_AUTOMAKE: two- and three-arguments > forms are deprecated. For more info, see: > configure.in:12: > http://www.gnu.org/software/automake/manual/automake.html#Modernize-AM_005fINIT_005fAUTOMAKE-invocation > automake: warning: autoconf input should be named 'configure.ac', not > 'configure.in' Here, warning is similar to mine. > frontend/Makefile.am:4: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') > frontend/Makefile.am:10: warning: source file > '$(top_srcdir)/common/faad/getopt.c' is in a subdirectory, > frontend/Makefile.am:10: but option 'subdir-objects' is disabled > automake: warning: possible forward-incompatibility. > automake: At least a source file is in a subdirectory, but the > 'subdir-objects' > automake: automake option hasn't been enabled. For now, the > corresponding output > automake: object file(s) will be placed in the top-level directory. > However, > automake: this behaviour will change in future Automake versions: they will > automake: unconditionally cause object files to be placed in the same > subdirectory > automake: of the corresponding sources. > automake: You are advised to start using 'subdir-objects' option > throughout your > automake: project, to avoid future incompatibilities. > plugins/mpeg4ip/Makefile.am:16: warning: 'INCLUDES' is the old name for > 'AM_CPPFLAGS' (or '*_CPPFLAGS') I would like to understand what I am or why the system is doing differently. Please, what would be the relevant information for comparison? I have: fernando [ ~ ]$ uname -a Linux VMWLFS73 3.10.2 #1 SMP Mon Jul 22 12:13:23 BRT 2013 x86_64 GNU/Linux fernando [ ~ ]$ cat /etc/lfs-release SVN-20130512 fernando [ ~ ]$ cat /etc/lsb-release DISTRIB_ID="Linux From Scratch" DISTRIB_RELEASE="SVN-20130512" DISTRIB_CODENAME="lfs-jhalfs" DISTRIB_DESCRIPTION="Linux From Scratch" fernando [ ~ ]$ gcc --version gcc (GCC) 4.8.0 ... fernando [ ~ ]$ make --version GNU Make 3.82 Built for x86_64-unknown-linux-gnu ... Thanks in advance. -- []s, Fernando -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
