[Pnet-developers] FW: Compiling pnetlib

[gene . livshits]

Hi,
        I have downloaded the latest stable source of pnetlib on
Solaris 2.8.  I am using gcc 3.4.1.  I have compiled pnet and treecc
with no problems.   But when I am compiling pnetlib, I am getting
the following error for 'runtime' portion:

..snip..
ilasm -o
./Microsoft/Internal/Deployment/InternalActivationContextHelper.objtmp -g
-f plugin-cs-path= -f unsafe -f assembly-version=2.0.3600.0 -f
assembly-key=neutral -f latin1-charset -f metadata-version=v2.0.40607 -f
resources=./../resources/en_US/runtime/runtime.resources -f
target-assembly-name=mscorlib -- -
stdin:5373: syntax error, unexpected $end, expecting "::"
ilasm: exited with signal 11 (core dumped)
*** Target `all' for project `pnetlib runtime' failed ***
*** Project `pnetlib runtime' build failed ***
make[1]: *** [mscorlib.dll] Error 1
make[1]: Leaving directory `/var/tmp/local/dotNET/pnetlib-0.6.8/runtime'
make: *** [all-recursive] Error 1

( I have cut off the multipage listing of the *.cs files that where called
from the Makefile as an argument
to cscc.  This portion is marked by .snip. ).

Could you please help me rectify this problem?

        -Gene.

-----Original Message-----
From: address@hidden [mailto:address@hidden 
Sent: Tuesday, August 31, 2004 5:37 PM
To: Gene X Livshits
Subject: Re: Compiling pnetlib

On Wednesday 01 September 2004 08:44 am, address@hidden wrote:
> No.

I suggest that you post the original problem on the
address@hidden 
mailing list, with the added information that the backtrace wasn't
helpful, 
and that "Rhys is stumped".  There are a few other DotGNU'ers who have 
Solaris who might be able to replicate the problem.  Just not me, I'm
afraid.  
See www.dotgnu.org for subscription details for the mailing list.

Cheers,

Rhys.




This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data 
and other information are not warranted as to completeness or accuracy and 
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.