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

Hi Kris,

On Fri, 2007-08-24 at 10:16 +0200, Mark Wielaard wrote: 
> > 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.
> As it happens in this timezone everything works after a fresh checkout
> and fresh build (Fedora Core 6/x86_64, gcc 4.1.2-13, automake 1.9.6,
> autoconf 2.59 and Fedora 7/x86, gcc 4.1.2-12, automake 1.10, autoconf
> 2.61).
> I personally suspect the autotools or having to completely throw away
> your build dir (which is what I just do each morning).

Doh. I lied (a little). Now that I do a completely fresh build
(including cloning a fresh source repository) I did get the same

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/ line 57: ../frysk/configure: No such file or directory

The reason I didn't see it before was that I wasn't doing a full clean
build and there was still an old configure file left. Investigating.



  reply	other threads:[~2007-08-24 11:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-24  5:51 Kris Van Hees
2007-08-24  8:16 ` Mark Wielaard
2007-08-24 11:12   ` Mark Wielaard [this message]
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).