From: Alexandra Yates <alexandra.yates at linux.intel.com>
To: powertop@lists.01.org
Subject: Re: [Powertop] Fix out of tree builds [Was: PowerTOP v2.6.1 released]
Date: Mon, 09 Jun 2014 16:14:50 -0700 [thread overview]
Message-ID: <39770.10.7.201.30.1402355690.squirrel@linux.intel.com> (raw)
In-Reply-To: 20140604233932.GH39023@rhrk.uni-kl.de
[-- Attachment #1: Type: text/plain, Size: 1343 bytes --]
Joerg,
> Hallo Alexandra,
>
> On Wed, Jun 04, 2014 at 02:20:18PM -0700, Alexandra Yates wrote:
>> Unfortunately the patches you sent don't fix the issue. Here is how to
>> reproduced the issue:
>> 1- Applied your patches.
>> 2- Generated an new dist/tarball,
>> 3- Untared on different location
>> 4- Executed: ./autogen; ./configure; make; make clean; make
>>
>> The error still points that /bin/bash: ./csstoh.sh: No such file or
>> directory
>
>> make[2]: Entering directory `/home/magd/Downloads/powertop-2.6.1/src'
>> /bin/bash ./csstoh.sh ./powertop.css css.h
>> /bin/bash: ./csstoh.sh: No such file or directory
>
> Luckily you included your workflow - it contains a bug. As you can see the
> system has not picked up the new path (the text ./csstoh.sh no longer
> exists
> in the source). Correct order would be:
> 1- apply patches
> 2- ./autogen && ./configure
> 3- make distcheck
> 4- cp powertop-2.6.1.tar.gz <wherever>
>
> Ciao
> Jörg
> --
> Joerg Mayer <jmayer(a)loplof.de>
> We are stuck with technology when what we really want is just stuff that
> works. Some say that should read Microsoft instead of technology.
>
I still get the error, even after following your steps. You may have
other commits I don't.
Thank you,
Alexandra.
next reply other threads:[~2014-06-09 23:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 23:14 Alexandra Yates [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-10 18:30 [Powertop] Fix out of tree builds [Was: PowerTOP v2.6.1 released] Alexandra Yates
2014-06-10 17:32 Alexandra Yates
2014-06-10 7:41 Joerg Mayer
2014-06-10 7:29 Joerg Mayer
2014-06-04 23:39 Joerg Mayer
2014-06-04 21:20 Alexandra Yates
2014-06-01 7:51 Joerg Mayer
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=39770.10.7.201.30.1402355690.squirrel@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.