From: Benno Schulenberg <bensberg@justemail.net>
To: Bruce Dubbs <bruce.dubbs@gmail.com>
Cc: Karel Zak <kzak@redhat.com>, "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [ANNOUNCE] util-linux v2.26-rc1
Date: Wed, 21 Jan 2015 22:05:16 +0100 [thread overview]
Message-ID: <1421874316.196312.217065457.6F95655D@webmail.messagingengine.com> (raw)
In-Reply-To: <54BF57B5.1000505@gmail.com>
On Wed, Jan 21, 2015, at 08:39, Bruce Dubbs wrote:
> Benno Schulenberg wrote:
> > $ gcc --version | head -1
> > gcc (Ubuntu 4.4.3-4ubuntu5.1) 4.4.3
>
> I don't know how far back you want to go, but that version of gcc was
> released 21-Jan-2010, fully 5 years ago.
I'm not wanting to go anywhere; it's simply the gcc that's installed
on my system. And I'm merely providing the solicited feedback.
However, if this util-linux can't be compiled with such an old gcc,
it would be nice if ./configure would report that. The same for a
minimum required kernel version.
> 2.6.32 was 14-Dec-2009 and I don't see any nano versions beyond
> linux-2.6.32.27 from 09-Dec-2010
$ uname -rv
2.6.32-71-generic #138-Ubuntu SMP Thu Dec 18 17:38:32 UTC 2014
Ubuntu Lucid is supported until April this year. Is it so strange to
try and compile a new util-linux on such a system?
Benno
--
http://www.fastmail.com - The professional email service
next prev parent reply other threads:[~2015-01-21 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 19:46 [ANNOUNCE] util-linux v2.26-rc1 Karel Zak
2015-01-18 19:10 ` Samuel Thibault
2015-01-18 22:03 ` Sami Kerola
2015-01-18 22:13 ` Samuel Thibault
2015-01-26 11:01 ` Karel Zak
2015-01-19 20:42 ` Bruce Dubbs
[not found] ` <1421786901.3565769.216421909.377E2720@webmail.messagingengine.com>
[not found] ` <54BF57B5.1000505@gmail.com>
2015-01-21 21:05 ` Benno Schulenberg [this message]
2015-01-21 21:12 ` Bruce Dubbs
2015-01-26 11:29 ` Karel Zak
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=1421874316.196312.217065457.6F95655D@webmail.messagingengine.com \
--to=bensberg@justemail.net \
--cc=bruce.dubbs@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@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