This is the mail archive of the
kawa@sourceware.org
mailing list for the Kawa project.
Re: Problems with duplicate declarations of modules
- From: Per Bothner <per at bothner dot com>
- To: alex mitchell <alexm at nus dot edu dot sg>
- Cc: "kawa at sources dot redhat dot com" <kawa at sources dot redhat dot com>
- Date: Wed, 24 Jun 2009 17:08:46 -0700
- Subject: Re: Problems with duplicate declarations of modules
- References: <C667C121.1B91B%alexm@nus.edu.sg>
On 06/23/2009 08:40 PM, alex mitchell wrote:
I have a fairly complex project, with roughly 20 .scm files that form a set
of libraries, which are then used by numerous other files. Several of the
library files make use of other library files. Occasionally, when I require
two of these library files, I get errors that there are duplicate
declarations of the files that THEY require.
What kind of errors? What kind of declarations?
Could you send me the error messages, and the source files?
At least the declarations being complained about.
This feels like a bug, but as mentioned I haven't (yet) managed to isolate
it. It also feels like there are some intermediate files being kept around
between runs, otherwise I can't understand why the fresh copy on a new
machine complains about missing definitions, whereas my development machine
does complain about this. However, I don't see any way to do a "clean" to
get my dev machine into the same state as the fresh machine.
If you have Unix commands available, I'd try:
rm -f `find . -name '*.class'` `find . -name '*.jar'`
That doesn't do it?
--
--Per Bothner
per@bothner.com http://per.bothner.com/