public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Brian Jones <cbj@gnu.org>
To: "Patrick Ellis" <Patrick.Ellis@sas.com>
Cc: <mauve-discuss@sources.redhat.com>
Subject: Re: Error compiling Mauve Net after updating on March 25,2003
Date: Thu, 27 Mar 2003 03:39:00 -0000	[thread overview]
Message-ID: <m38yv1mqac.fsf@lyta.haphazard.org> (raw)
In-Reply-To: <F2E670D5036BE14E89473A3FAEDE6ACE028067DB@merc18.na.sas.com>

"Patrick Ellis" <Patrick.Ellis@sas.com> writes:

> I get the following compilation error for mauve Net. 
> The code is being compiled on an ALX machine.
> I have tried java versions : 1.4.0 and 1.4.1  
> betageek> java -version
> java version "1.4.0"
> Java(TM) 2 Runtime Environment, Standard Edition
> Fast VM (build 1.4.0-1, native threads, mixed mode, precompiled rt.jar, 09/05/2002-19:05)
> 
> Thanks for any hints on what is going on.....
> 
> Pat
> 
> gnu/testlet/java/net/Socket/TestSocketImplFactory.java:27: duplicate class: gnu.testlet.java.net.Socket.TestSocketImplFactory
> public class TestSocketImplFactory
>        ^
> gnu/testlet/java/net/Socket/TestSocketImplFactory.java:30: return outside method
>   public SocketImpl createSocketImpl () { return null; }
>                                           ^
> Note: Some input files use or override a deprecated API.
> Note: Recompile with -deprecation for details.

I do not get any error message with either jikes 1.18 or javac from
Sun's JDK 1.4.1 for GNU/Linux x86.  The error above about the return
outside method appears bogus...  I suspect your other email may be
experiencing similar failures.

Brian
-- 
Brian Jones <cbj@gnu.org>

      reply	other threads:[~2003-03-27  3:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-26 15:37 Patrick Ellis
2003-03-27  3:39 ` Brian Jones [this message]

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=m38yv1mqac.fsf@lyta.haphazard.org \
    --to=cbj@gnu.org \
    --cc=Patrick.Ellis@sas.com \
    --cc=mauve-discuss@sources.redhat.com \
    /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).