bug-cpio
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-cpio] workaround bootstrap AC_INIT parsing drawback


From: Pavel Raiskup
Subject: [Bug-cpio] workaround bootstrap AC_INIT parsing drawback
Date: Fri, 31 Jan 2014 10:21:41 +0100
User-agent: KMail/4.11.5 (Linux/3.12.8-300.fc20.x86_64; KDE/4.11.5; x86_64; ; )

The bootstrap script does not parse AC_INIT from configure.ac correctly if
AC_INIT is split among two lines;  Results:

  $ ./bootstrap
  ....
  ./bootstrap: autoconf --force ...
  ./bootstrap: autoheader --force ...
  ./bootstrap: automake --add-missing --copy --force-missing ...
  doc/Makefile.am:25: error: PU_RMT_COND does not appear in AM_CONDITIONAL
  $ cat m4/paxutils.m4 | grep PAXUTILS
  AC_DEFUN([_PAXUTILS],[
  $ #       ^^^^ That should be cpio_PAXUTILS

I don't think that parsing the package like that is correct approach but
dunno what is correct.  Possibly something like this?

   autom4te --language Autoconf --trace AC_INIT configure.ac | \
      cut -d: -f 4 | sed 's|^GNU[[:space:]]||'

Not sure, but the workaround is to make it one-liner; attached.  Note that
detecting defects like this is not very trivial..

Pavel

Attachment: 0001-confiugre.ac-workaround-bootstrap-problem.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]