[bitc-dev] Fedora5 install experience

Swaroop Sridhar swaroop at cs.jhu.edu
Wed May 17 16:25:21 EDT 2006


Tom Bachmann wrote:
> - - some of the unit tests (seem to) fail
> 
> - - make run in defloop or reachbug fails with "make: *** No rule to make
> target `srca.c', needed by `BUILD/srca.o'.  Stop."
> 
> - - make run in general fails with
> 
> ../../frontend/BUILD/bitcc -I ../../runtime -I. -L ../../libbitc -l
> showtypes  basic.bitc
> basic.bitc:47:35: Redefinition of Symbol eqls. Already defined at
> basic.bitc:45:10.
> Exiting due to errors during Symbol Resolution
> make: *** [all] Error 1


Nigel Williams wrote:
>>- - some of the unit tests (seem to) fail
> 
> 
> You are ahead of me; I am so far only working in
> ../bitcc-bootstrap/tests/unit
> 
> I just tried using the Makefile from the above directory for tests/general (as
> tests/general/Makefile appears to be out of date) and I see compile errors
> too.

Thanks for all the input.

To clarify issues:

_Only_ the tests/unit directory contains unit tests. This directory 
contains examples which are expected to work. In some cases, the 
expected behavior is to throw an exception at run time, but there must 
not be any compile time fault.

The tests/general and other directories (other than tests/unit) are 
mainly for experimentation during development. They have many test cases 
that are expected to fail (that is, they test for error cases that 
should not  compile successfully). They also contain many old examples 
that are now deprecated, and are rejected by current version of the 
compiler. basic.bitc, in particular, exists only for historical value, 
it has many test cases that I wrote ever since the first version of the 
compiler. Also, the Makefiles in these directories are either 
deprecated, or have a different custom structure.

I should have noted this earlier, my mistake.

Of course, if you notice a problem in compiling a program that is 
correct according to the current spec, (within the other test 
directories, or your own programs, etc), please let us know.

Thanks,
Swaroop.


More information about the bitc-dev mailing list