public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: Andrew Cagney <>
Cc: frysk <>
Subject: Re: got JNI; but only just :-)
Date: Sat, 12 Apr 2008 21:01:00 -0000	[thread overview]
Message-ID: <1208033592.3608.9.camel@localhost.localdomain> (raw)
In-Reply-To: <>

On Fri, 2008-04-11 at 17:32 -0400, Andrew Cagney wrote:
> I've just pushed changes to frysk's build system that add the ability to 
> build JNI code vis:
> - automatically generate required jni headers
> - compile */jni/*.cxx files into a separate shared object
> while at the same time continuing to build the existing CNI code.  By 
> being able to build/run both side-by-side we'll hopefully help to ease 
> the migration pain.

Nice, but something broke all the TestTypeFactory tests:

Running test_char_var(frysk.debuginfo.TestTypeFactory) ...execve: No such file
or directory
  junit.framework.AssertionFailedError: event loop run explictly stopped (run to
blocked exec)

I tried to git bi-sect to see which commit actually broke it, but not
all the commits actually compile :{ So for now I filed a bug report
#6396 and marked the tests unresolved. Could you take a look what causes
the funit-type-class not to be compiled/found?



2008-04-12  Mark Wielaard  <>

    * Mark unresolved #6396.

index 0a36801..7a82702 100644
--- a/frysk-core/frysk/debuginfo/
+++ b/frysk-core/frysk/debuginfo/
@@ -135,6 +135,7 @@ public class %s extends TestLib {
     def start_test(self, executable, name):
         print("    public void test_%s () {" % (name))
+        print("      if (unresolved(6396)) return;");
         tokens = os.path.splitext(os.path.abspath(executable))
         print('        TypeTestbed typeTestbed = new TypeTestbed("%s", "test%s"

  reply	other threads:[~2008-04-12 20:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12 20:53 Andrew Cagney
2008-04-12 21:01 ` Mark Wielaard [this message]
2008-04-14 13:26   ` Andrew Cagney

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 \
    --in-reply-to=1208033592.3608.9.camel@localhost.localdomain \ \ \ \

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