public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Tiago Daitx <tiago.daitx@canonical.com>
To: mauve-discuss@sourceware.org
Subject: Project status
Date: Thu, 23 Feb 2017 18:17:00 -0000	[thread overview]
Message-ID: <CAC-Dh98=cUj0h2QikLSDVe6adVTpg6wcoN7VbUS10vvFps8q+Q@mail.gmail.com> (raw)

Hi,

I have been trying to follow up on Mauve and to build it, but that has
not been working really well.

First of all, the project is lacking a web presence, it seems dead
outside the CVS repo. Most of the links from the main page at
sourceware [1] are not working:

- "Download" [2] points to nightly snapshots [3] which is empty
- "CVS" [4] points to the cvsweb [5] which then redirects to a
repository listing [6] where mauve is missing
- The mailing lists archives seem to indicate some activity
(month/year links which seem to skip periods with no activity), but
clicking on the respective month/year leads to a "No messages here";
the exception here is a single message in mauve-patches for 2017 that
seems pretty much like spam

Checking out CVS repository does show that the last commits are dated
8/April/2016.

The README seems to be out of date, as some arguments for the
configure script have been removed on a previous commit
(--with-bootclasspath, --with-gcj).

Trying to run the testsuite (java Harness) brings up lots of errors
when using the autocompile.

Trying to compile the gnu/testlet testsuite before hand will also
throw out errors with both gcj as well as openjdk.

For gcj-5 (full log at [7]):
$ cd gnu/testlet
$ /usr/lib/jvm/java-gcj/bin/javac -nowarn -cp ../../:. .
...
148 problems (148 errors)

For openjdk-8 (full log at [8]):
$ cd gnu/testlet
$ find -name '*.java' -type f | sort -u > java_files
$ javac -cp /usr/share/java/libgcj-5.jar:../../:. -g -source 1.5
-target 1.5 -nowarn @java_files
...
32 errors

Trying to run the tests after compiling also does not work that well,
lots of errors like:
FAIL: gnu.java.security.hash.TestOfHashFactory
  line 42: TestOfHashFactory [1] -- uncaught exception:
   java.lang.NoClassDefFoundError: gnu/java/security/hash/HashFactory

even though /usr/share/java/libgcj-5.jar is in the classpath and
contains the class.

It would be nice if I could get some pointers on what I'm doing wrong
and on whether the project is still being supported.

Best regards,
Tiago

[1] https://www.sourceware.org/mauve/
[2] https://www.sourceware.org/mauve/download.html
[3] ftp://sourceware.org/pub/mauve/snapshot/
[4] https://www.sourceware.org/mauve/cvs.html
[5] http://sourceware.org/cgi-bin/cvsweb.cgi/?cvsroot=mauve
[6] https://sourceware.org/viewvc
[7] https://pastebin.ubuntu.com/24054344/
[8] https://pastebin.ubuntu.com/24054354/

-- 
Tiago Stürmer Daitx
Software Engineer
tiago.daitx@canonical.com

PGP Key: 4096R/F5B213BE (hkp://keyserver.ubuntu.com)
Fingerprint = 45D0 FE5A 8109 1E91 866E  8CA4 1931 8D5E F5B2 13BE

             reply	other threads:[~2017-02-23 18:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-23 18:17 Tiago Daitx [this message]
2017-02-27 19:49 ` Anthony Green
2017-02-27 19:51   ` Deepak Bhole
2017-02-27 19:52     ` Deepak Bhole
2017-02-28  8:11       ` Jiri Vanek
2017-02-28 12:31         ` Anthony Green
2017-02-28 13:00           ` Mark Wielaard
2017-02-28 13:11             ` Anthony Green
2017-03-01  3:00     ` Andrew Hughes

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='CAC-Dh98=cUj0h2QikLSDVe6adVTpg6wcoN7VbUS10vvFps8q+Q@mail.gmail.com' \
    --to=tiago.daitx@canonical.com \
    --cc=mauve-discuss@sourceware.org \
    /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).