Skip to content

Instantly share code, notes, and snippets.

Embed
What would you like to do?
U valgrind
Checked out revision 137.
make: *** No rule to make target 'distclean'. Stop.
running: aclocal
aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in'
running: autoheader
running: automake -a
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
configure.in:24: installing './compile'
configure.in:155: installing './config.guess'
configure.in:155: installing './config.sub'
configure.in:14: installing './install-sh'
configure.in:14: installing './missing'
automake: warning: autoconf input should be named 'configure.ac', not 'configure.in'
Makefile.am:54: error: 'pkglibdir' is not a legitimate directory for 'DATA'
Makefile.vex.am:90: warning: source file 'priv/main_globals.c' is in a subdirectory,
Makefile.vex.am:90: 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.