public inbox for
 help / color / mirror / Atom feed
From: Kris Van Hees <>
Subject: Again the build is broken :(
Date: Fri, 24 Aug 2007 05:51:00 -0000	[thread overview]
Message-ID: <> (raw)

Again, we have a broken build with the following error:

<<part truncated because it is not relevant>>
Running autoconf ... for libunwind
Running aclocal ... for frysk-imports
Running autoconf ... for frysk-imports
Running automake ... for frysk-imports installing `./install-sh' installing `./missing'
tests/ installing `./compile'
tests/ installing `./depcomp'
common/ installing `./config.guess'
common/ installing `./config.sub'
common/Makefile.rules:101: variable `GEN_GCJ_LDADD' is defined but no program or
common/Makefile.rules:101: library has `GEN_GCJ' as canonic name (possible typo)   `common/Makefile.rules' included from here
Problem in directory frysk-imports
../frysk_config/ line 57: ../frysk_config/configure: No such file or directory

The cause seems to be the following commit:

        2007-08-23  Andrew Cagney  <>

        * Makefile.rules (fryski, Delete targets.

I hope Mark or anyone else in a more convenient timezone may be able to commit
a fix for this.  Still recovering a bit from my travel yesterday, I'm more
likely to cause additional problems than to solve this one right now.

Finally, it seems like we're getting a lot more broken build cases lately than
we've had in the past months.  I am not sure what is causing this, because it
seems like there have not really been any procedural changes that would cause
this regression in quality.  That leaves the question: what can we do about
this?  Assuming pre-commit testing is being done appropriately (i.e. using a
clean slate - no left over configure scipts etc generated in a previous build),
a problem like this can only be the result of a problem in how we perform the
pre-commit testing.  What can we do to improive upon it?


             reply	other threads:[~2007-08-24  5:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  5:51 Kris Van Hees [this message]
2007-08-24  8:16 ` Mark Wielaard
2007-08-24 11:12   ` Mark Wielaard
2007-08-24 11:47     ` Mark Wielaard
2007-08-24 12:34   ` Andrew Cagney
2007-08-24 14:26     ` Elena Zannoni
2007-08-24 14:39       ` Mark Wielaard
2007-08-24 15:17         ` Phil Muldoon
2007-08-24 16:14           ` Elena Zannoni
2007-08-24 21:00             ` Andrew Cagney
2007-08-28  0:19             ` Phil Muldoon
2007-08-24 16:44         ` Kris Van Hees
2007-08-26 21:21 Kris Van Hees

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).