public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: collectd 5.7.2 desperately misses 'automake 1.14' ;-)
Date: Sun, 24 Sep 2017 19:32:38 +0100	[thread overview]
Message-ID: <1506277958.18494.72.camel@ipfire.org> (raw)
In-Reply-To: <997f28b3-725c-5b2e-cf8e-30d36a225064@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Hi,

I don't think this is a good idea.

In collectd 5, the format of the RRDs has changed which would require us to
migrate them all (they use DERIVE instead of COUNTER now). 

We backported quite a few patches into our version of collectd for things we
needed.

So is there any features you need or is this just to follow upstream?

-Michael

On Sun, 2017-09-24 at 16:17 +0200, Matthias Fischer wrote:
> Hi,
> 
> I'm trying to build 'collectd 5.7.2' for some testing, but it always
> fails with the following warning:
> 
> ...
>  make[2]: Entering directory '/usr/src/collectd-5.7.2/src'
> 
> cd .. && /bin/sh /usr/src/collectd-5.7.2/libltdl/config/missing
> automake-1.14 --foreign src/Makefile
> 
> /usr/src/collectd-5.7.2/libltdl/config/missing: line 81: automake-1.14:
> command not found
> 
> WARNING: 'automake-1.14' is missing on your system.
> ...
> 
> This is right, because current 'next' uses 'automake 1.15'. I tested
> with 1.15.1, tried several lfs-changes, but still no luck.
> 
> Does anyone got a tip?
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-09-24 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-24 14:17 Matthias Fischer
2017-09-24 18:32 ` Michael Tremer [this message]
2017-09-24 20:17   ` Matthias Fischer
2017-09-24 21:22     ` Michael Tremer

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=1506277958.18494.72.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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