From: Per Bothner <per@bothner.com>
To: David Pirotte <david@altosw.be>
Cc: kawa@sourceware.org
Subject: Re: kawa 2.2 last call
Date: Sat, 15 Oct 2016 00:38:00 -0000 [thread overview]
Message-ID: <022d1e4d-f3e4-bcff-44c1-8c50aa72f166@bothner.com> (raw)
In-Reply-To: <20161014211645.1554e57c@capac>
On 10/14/2016 05:16 PM, David Pirotte wrote:
> Still have errors though:
>
> david@capac:/usr/local/src/kawa/svn 39 $ javac -version
> javac 1.8.0_102
> ...
> mv tmp-list tmp-sources1.list
> javac -d . -classpath ".:.:$CLASSPATH" -g @tmp-sources1.list
> ./gnu/expr/ApplicationMainSupport.java:71: error: cannot find symbol
> commandLineArguments = FVector.makeConstant(array); // FIXME scsh has list
> ^
> symbol: method makeConstant(Object[])
> location: class FVector
> ./gnu/kawa/reflect/Invoke.java:184: error: cannot find symbol
> return FVector.makeConstant((Object[]) arr);
> ^
> symbol: method makeConstant(Object[])
> location: class FVector
> ./gnu/kawa/lispexpr/ReaderVector.java:56: error: incompatible types: Object[] cannot be converted to UnaryOperator
> result.replaceAll(((LList) head.getCdr()).toArray());
> ^
> ./gnu/kawa/xml/HttpPrinter.java:186: error: method writeTo in class ByteVector<E> cannot be applied to given types;
> ((Blob) v).writeTo(outs);
> ^
> required: int,int,OutputStream
> found: OutputStream
> reason: actual and formal argument lists differ in length
> where E is a type-variable:
> E extends Object declared in class ByteVector
> ./kawa/lang/Quote.java:354: error: cannot find symbol
> result = FVector.<Object>makeConstant(buffer);
> ^
> symbol: method <Object>makeConstant(Object[])
> location: class FVector
Strange. I'm guessing one of:
(1) an inconsistent Subversion check-out.
(There should be *two* writeTo methods in ByteVector.)
(2) Some stale classes or a bogus .jar in your classpath.
(a) Make sure CLASSPATH is not set in your environment.
(b) Do a "make clean" followed by "find . -name '*.class'"
My guess is (2a).
--
--Per Bothner
per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2016-10-15 0:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 20:59 Per Bothner
2016-10-14 23:39 ` David Pirotte
2016-10-14 23:45 ` Per Bothner
2016-10-15 0:17 ` David Pirotte
2016-10-15 0:38 ` Per Bothner [this message]
2016-10-15 20:56 ` Sudarshan S Chawathe
2016-10-15 21:03 ` Andrea Bernardini
2016-10-15 21:14 ` Per Bothner
2016-10-15 21:32 ` David Pirotte
2016-10-15 21:49 ` Per Bothner
2016-10-15 22:10 ` Per Bothner
2016-10-15 22:28 ` Andrea Bernardini
2016-10-15 23:05 ` Per Bothner
2016-10-15 23:19 ` Per Bothner
2016-10-15 23:39 ` Andrea Bernardini
2016-10-15 23:41 ` David Pirotte
2016-10-16 1:04 ` Per Bothner
2016-10-16 2:37 ` David Pirotte
2016-10-16 13:46 ` Debian Jessie success report. " Sudarshan S Chawathe
2016-10-16 0:09 ` Sudarshan S Chawathe
2016-10-16 1:17 ` Per Bothner
2016-10-16 1:51 ` Per Bothner
2016-10-15 22:40 ` Sudarshan S Chawathe
2016-10-15 21:10 ` Per Bothner
2016-10-15 21:22 ` Per Bothner
2016-10-15 21:58 ` Sudarshan S Chawathe
2016-10-15 22:23 ` makeinfo (version?) problem. " Sudarshan S Chawathe
2016-10-15 22:29 ` Per Bothner
2016-10-16 15:54 ` 'images' directory for Info docs. " Sudarshan S Chawathe
2016-10-16 19:41 ` Per Bothner
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=022d1e4d-f3e4-bcff-44c1-8c50aa72f166@bothner.com \
--to=per@bothner.com \
--cc=david@altosw.be \
--cc=kawa@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).