Protobuf installation fails due to version mismatch of Automake












0















I was following the answer on: How can I install protoc on Ubuntu 16.04?



But, my protobuf installation make fails with versioning issue in Automake



/protobuf/missing automake-1.15 --foreign
configure.ac:48: error: version mismatch. This is Automake 1.15,
configure.ac:48: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:48: comes from Automake 1.15.1. You should recreate
configure.ac:48: aclocal.m4 with aclocal and run automake again.
WARNING: 'automake-1.15' is probably too old.
You should only need it if you modified 'Makefile.am' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'automake' program is part of the GNU Automake package:
<http://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<http://www.gnu.org/software/autoconf>
<http://www.gnu.org/software/m4/>
<http://www.perl.org/>
Makefile:1451: recipe for target 'Makefile.in' failed
make: *** [Makefile.in] Error 1









share|improve this question

























  • I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

    – steeldriver
    Feb 7 at 13:15











  • ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

    – Binita Bharati
    Feb 7 at 15:07


















0















I was following the answer on: How can I install protoc on Ubuntu 16.04?



But, my protobuf installation make fails with versioning issue in Automake



/protobuf/missing automake-1.15 --foreign
configure.ac:48: error: version mismatch. This is Automake 1.15,
configure.ac:48: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:48: comes from Automake 1.15.1. You should recreate
configure.ac:48: aclocal.m4 with aclocal and run automake again.
WARNING: 'automake-1.15' is probably too old.
You should only need it if you modified 'Makefile.am' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'automake' program is part of the GNU Automake package:
<http://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<http://www.gnu.org/software/autoconf>
<http://www.gnu.org/software/m4/>
<http://www.perl.org/>
Makefile:1451: recipe for target 'Makefile.in' failed
make: *** [Makefile.in] Error 1









share|improve this question

























  • I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

    – steeldriver
    Feb 7 at 13:15











  • ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

    – Binita Bharati
    Feb 7 at 15:07
















0












0








0








I was following the answer on: How can I install protoc on Ubuntu 16.04?



But, my protobuf installation make fails with versioning issue in Automake



/protobuf/missing automake-1.15 --foreign
configure.ac:48: error: version mismatch. This is Automake 1.15,
configure.ac:48: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:48: comes from Automake 1.15.1. You should recreate
configure.ac:48: aclocal.m4 with aclocal and run automake again.
WARNING: 'automake-1.15' is probably too old.
You should only need it if you modified 'Makefile.am' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'automake' program is part of the GNU Automake package:
<http://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<http://www.gnu.org/software/autoconf>
<http://www.gnu.org/software/m4/>
<http://www.perl.org/>
Makefile:1451: recipe for target 'Makefile.in' failed
make: *** [Makefile.in] Error 1









share|improve this question
















I was following the answer on: How can I install protoc on Ubuntu 16.04?



But, my protobuf installation make fails with versioning issue in Automake



/protobuf/missing automake-1.15 --foreign
configure.ac:48: error: version mismatch. This is Automake 1.15,
configure.ac:48: but the definition used by this AM_INIT_AUTOMAKE
configure.ac:48: comes from Automake 1.15.1. You should recreate
configure.ac:48: aclocal.m4 with aclocal and run automake again.
WARNING: 'automake-1.15' is probably too old.
You should only need it if you modified 'Makefile.am' or
'configure.ac' or m4 files included by 'configure.ac'.
The 'automake' program is part of the GNU Automake package:
<http://www.gnu.org/software/automake>
It also requires GNU Autoconf, GNU m4 and Perl in order to run:
<http://www.gnu.org/software/autoconf>
<http://www.gnu.org/software/m4/>
<http://www.perl.org/>
Makefile:1451: recipe for target 'Makefile.in' failed
make: *** [Makefile.in] Error 1






16.04 automake






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 7 at 6:57









Kulfy

5,03551744




5,03551744










asked Feb 7 at 6:44









Binita BharatiBinita Bharati

1011




1011













  • I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

    – steeldriver
    Feb 7 at 13:15











  • ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

    – Binita Bharati
    Feb 7 at 15:07





















  • I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

    – steeldriver
    Feb 7 at 13:15











  • ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

    – Binita Bharati
    Feb 7 at 15:07



















I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

– steeldriver
Feb 7 at 13:15





I'm curious why make would even need to invoke automake here - that should only happen if the configure script became out-of-date (for example, if configure.ac was changed after you ran ./configure). Perhaps it would be useful to add the output of ls -l config* to your question so we can see the timestamps?

– steeldriver
Feb 7 at 13:15













ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

– Binita Bharati
Feb 7 at 15:07







ls -l config* output : vagrant@net1mc2:~/temp$ ls -l config* -rwxr-xr-x 1 vagrant vagrant 43815 Jul 30 2018 config.guess -rw-r--r-- 1 vagrant vagrant 3846 Jul 30 2018 config.h.in -rwxr-xr-x 1 vagrant vagrant 36692 Jul 30 2018 config.sub -rwxr-xr-x 1 vagrant vagrant 723617 Jul 30 2018 configure -rw-r--r-- 1 vagrant vagrant 7158 Jul 30 2018 configure.ac

– Binita Bharati
Feb 7 at 15:07












0






active

oldest

votes












Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116315%2fprotobuf-installation-fails-due-to-version-mismatch-of-automake%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1116315%2fprotobuf-installation-fails-due-to-version-mismatch-of-automake%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Human spaceflight

Can not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?

File:DeusFollowingSea.jpg