I've added the missing newline to the error message in CVS.  However, it needs to be clarified as to the intention of the -e option.  As mentioned in the original bug report, passing a valid argument to -e (as suggested in the man page) should permit the linker to utilize the provided argument and not the default.  What we really need is definitive direction on this particular issue from upper management. :)

Currently cscc -e never seems to be able to resolve an entry point.

cscc -e EntryPointTwo entry.cs
program has multiple entry points
a.out: could not locate the entry point `EntryPointTwo'

Also using "cscc -e Class.Main" does not work (both should, according to the man page of cscc)

Btw. there is a missing newline at the end of the error message which screws up the terminal :)

Testcase is attached.