public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Michael DePaulo <mikedep333@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] gtkperf 0.40
Date: Thu, 05 Mar 2015 12:38:00 -0000	[thread overview]
Message-ID: <CAMKht8jOkpKikM-bNR-933gaeOPKQxGmaZE1JBk8nTzOW6s5DQ@mail.gmail.com> (raw)
In-Reply-To: <CAMKht8i2Cfv94VOmBVoovKGKLexRmpp1MgPYodry0uWPzSVt3w@mail.gmail.com>

On Fri, Feb 27, 2015 at 6:00 PM, Michael DePaulo <mikedep333@gmail.com> wrote:
> On Fri, Feb 27, 2015 at 12:37 PM, Yaakov Selkowitz
> <yselkowitz@cygwin.com> wrote:
>> On Fri, 2015-02-27 at 08:49 -0500, Michael DePaulo wrote:
>>> The benefit to Cygwin is that we will have a commonly used[1]
>>> benchmark for testing Cygwin/X performance.
>>>
>>> Thank you Jon Turney for helping me package this.
>>>
>
> Now at revision c81e08d
> https://github.com/mikedep333/gtkperf-cygport
>
>>> https://github.com/mikedep333/gtkperf-cygport
>>> Currently at commit e707eaa
>>
>> Why the NO_AUTOPOINT=1?
>
> Otherwise, you run into this problem with the very old autotools:
>
> make  all-recursive
> make[1]: Entering directory '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build'
> Making all in intl
> make[2]: Entering directory
> '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build/intl'
> make[2]: Nothing to be done for 'all'.
> make[2]: Leaving directory
> '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build/intl'
> Making all in po
> make[2]: Entering directory
> '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build/po'
> make[2]: *** No rule to make target 'Makevars', needed by 'Makefile'.  Stop.
> make[2]: Leaving directory
> '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build/po'
> Makefile:363: recipe for target 'all-recursive' failed
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory '/usr/src/gtkperf-cygport/gtkperf-0.40-1.i686/build'
> Makefile:273: recipe for target 'all' failed
> make: *** [all] Error 2
> *** ERROR: make failed
>
> I added a 3 line comment about this.
>
>>
>> You should also change the following:
>>
>> -SRC_URI=http://downloads.sourceforge.net/gtkperf/gtkperf_0.40.tar.gz
>> +HOMEPAGE="http://gtkperf.sourceforge.net/"
>> +SRC_URI="mirror://sourceforge/gtkperf/gtkperf_${VERSION}.tar.gz"
>>
>> ${VERSION} should be used in SRC_URI to prevent mistakes when (if?) this
>> package gets a new version upstream.
>
> Done.
>
> -Mike

Questions/Comments/Complaints?

  reply	other threads:[~2015-03-05 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-27 13:49 Michael DePaulo
2015-02-27 17:37 ` Yaakov Selkowitz
2015-02-27 23:00   ` Michael DePaulo
2015-03-05 12:38     ` Michael DePaulo [this message]
2015-03-05 15:07       ` Jon TURNEY

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=CAMKht8jOkpKikM-bNR-933gaeOPKQxGmaZE1JBk8nTzOW6s5DQ@mail.gmail.com \
    --to=mikedep333@gmail.com \
    --cc=cygwin-apps@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).