From: Chris Ferron <chris.e.ferron at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] [PATCH] Relaxed autoconf version restriction for scratchbox build
Date: Mon, 23 Jul 2012 08:10:30 -0700 [thread overview]
Message-ID: <500D6966.9040302@linux.intel.com> (raw)
In-Reply-To: 1342905401.4237.2.camel@mattotaupa
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
On 07/21/2012 02:16 PM, Paul Menzel wrote:
> Dear Chris,
>
>
> Am Freitag, den 20.07.2012, 10:27 -0700 schrieb Chris Ferron:
>> On 07/19/2012 11:52 PM, Igor Zhbanov wrote:
>>> Relaxed autoconf version restriction for scratchbox build.
>>> PowerTOP successfully builds with 2.67 version of Autotools.
>>> ---
>>> configure.ac | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/configure.ac b/configure.ac
>>> index 4b3d027..e1e670a 100644
>>> --- a/configure.ac
>>> +++ b/configure.ac
>>> @@ -1,7 +1,7 @@
>>> # -*- Autoconf -*-
>>> # Process this file with autoconf to produce a configure script.
>>>
>>> -AC_PREREQ([2.68])
>>> +AC_PREREQ([2.67])
>>> AC_INIT([powertop], [2.0], [powertop(a)lists.01.org])
>>> AM_INIT_AUTOMAKE([-Wall foreign ])
>>> AC_LANG([C++])
>> What is the problem? Why do you need to do this? What is the benefit to
>> the PowerTOP project?
> Hm, the commit message says it all if you know what Scratchbox [1] is.
I know a little about scratchbox. You should be talking the release tar
yes?
> I guess Scratchbox only includes Autoconf 2.67 so PowerTOP does not
> build out of the box with Scratchbox.
>
>
> Thanks,
>
> Paul
>
>
> [1] http://www.elinux.org/Toolchains#Scratchbox
next reply other threads:[~2012-07-23 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 15:10 Chris Ferron [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-23 6:19 [Powertop] [PATCH] Relaxed autoconf version restriction for scratchbox build Igor Zhbanov
2012-07-21 21:16 Paul Menzel
2012-07-20 17:27 Chris Ferron
2012-07-20 6:52 Igor Zhbanov
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=500D6966.9040302@linux.intel.com \
--to=powertop@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.