From: Vladimir Shebordaev <vladimir.shebordaev@gmail.com>
To: doiggl@velocitynet.com.au
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: help wanted add-node41.patch fails to apply to reiser4progs version 1.0.9
Date: Fri, 20 Feb 2015 06:31:16 +0300 [thread overview]
Message-ID: <1424403076.4261.1.camel@home.ted.local> (raw)
In-Reply-To: <c889d4bb783dfeb04663b277628e126f@mail.velocitynet.com.au>
So, what is your question? As you have been told, you've got libtool
package missing.
I'd also say, when you get it installed, you'd better invoke autoreconf
as
# autoreconf -if
Please also ignore numerous warnings about obsolete macro names, it has
nothing to do with the patch in issue.
--
Regards.
Vladimir
On Fri, 2015-02-20 at 12:02 +1100, doiggl@velocitynet.com.au wrote:
> Hello,
> Need to figure out the next bit in relation to autoreconf.
>
> shows in buildlog as:
> [ 83s] + autoreconf
> [ 85s] aclocal: warning: autoconf input should be named 'configure.ac',
> not 'configure.in'
> [ 85s] configure.in:196: warning: macro 'AM_ENABLE_SHARED' not found in
> library
> [ 85s] configure.in:313: warning: macro 'AM_PROG_LIBTOOL' not found in
> library
>
> [1]
> asked here:
> http://lists.opensuse.org/opensuse-packaging/2015-02/msg00069.html
>
> reply here:
> http://lists.opensuse.org/opensuse-packaging/2015-02/msg00071.html
>
> --Glenn
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-02-20 3:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 12:02 help wanted add-node41.patch fails to apply to reiser4progs version 1.0.9 doiggl
2015-02-19 12:40 ` doiggl
2015-02-19 13:00 ` Jose R R
2015-02-19 12:46 ` Jose R R
2015-02-19 14:01 ` doiggl
2015-02-19 15:34 ` Jose R R
2015-02-19 18:23 ` dimas
2015-02-20 1:02 ` doiggl
2015-02-20 3:31 ` Vladimir Shebordaev [this message]
2015-02-20 3:33 ` doiggl
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=1424403076.4261.1.camel@home.ted.local \
--to=vladimir.shebordaev@gmail.com \
--cc=doiggl@velocitynet.com.au \
--cc=reiserfs-devel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).