couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Davis <paul.joseph.da...@gmail.com>
Subject Re: buildbot failure in ASF Buildbot on couchdb-trunk
Date Mon, 02 May 2011 16:29:46 GMT
On Mon, May 2, 2011 at 9:45 AM, Filipe David Manana <fdmanana@apache.org> wrote:
> The buildbot complains about no target rule to make snappy.in:
>
> Making all in snappy
> make[4]: Entering directory
> `/home/buildslave3/slave3/couchdb-trunk/build/apache-couchdb-1.2.0a-1098558/_build/src/snappy'
> make[4]: *** No rule to make target `snappy.app', needed by `all-am'.  Stop.
> make[4]: Leaving directory
> `/home/buildslave3/slave3/couchdb-trunk/build/apache-couchdb-1.2.0a-
>
> However src/snappy/Makefile.am specifies a build rule for *.app as:
>
> %.app: %.app.in
>        cp $< $@
>
> This is exactly the same as in src/ejson/Makefile.am
>
> I've just tried out a new checkout from git.apache.org and I'm able to build it.
> Paul, is this some buildbot issue or is there something missing in the
> automake config?
>
>
>
> On Mon, May 2, 2011 at 2:32 PM,  <buildbot@apache.org> wrote:
>> The Buildbot has detected a new failure on builder couchdb-trunk while building ASF
Buildbot.
>> Full details are available at:
>>  http://ci.apache.org/builders/couchdb-trunk/builds/577
>>
>> Buildbot URL: http://ci.apache.org/
>>
>> Buildslave for this Build: bb-vm_ubuntu
>>
>> Build Reason: scheduler
>> Build Source Stamp: [branch couchdb/trunk] 1098558
>> Blamelist: fdmanana
>>
>> BUILD FAILED: failed compile_5
>>
>> sincerely,
>>  -The Buildbot
>>
>>
>
>
>
> --
> Filipe David Manana,
> fdmanana@gmail.com, fdmanana@apache.org
>
> "Reasonable men adapt themselves to the world.
>  Unreasonable men adapt the world to themselves.
>  That's why all progress depends on unreasonable men."
>

Time for me to be a bit of a bitch.

I told you last time to make sure and run `make distcheck` after you
do anything to the build system. You'll find the parts of the
Autotools book on VPATH builds helpful in figuring out this error.

Mime
View raw message