Managed code is executed during the FX build. Thus FJIT has to be functional in order to build the FX folder. Your changes most likely broke FJIT.
You can check the fx\src\builddf.log for more detailed error description. It may give you a hint on what got broken. The FX build is not the easier place to debug FJIT. You may want to ignore the FX build failure, and instead run some of the short BVTs (run "..\rrun.pl" in sscli\tests\bvt) or il_bvts (execute "..\rrun.pl" in sscli\tests\il_bvt). It is very likely that some of them are going to fail. You can then use the failing tests to trace down what got broken. -Jan This posting is provided "AS IS" with no warranties, and confers no rights. -----Original Message----- From: Discussion of the Rotor Shared Source CLI implementation [mailto:[EMAIL PROTECTED] On Behalf Of Krishna APB Sent: Tuesday, July 15, 2003 9:08 PM To: [EMAIL PROTECTED] Subject: [DOTNET-ROTOR] Error from SSCLI\fx\src folder When I modify FJIT, I am getting following 2 errors in different folder (as per SCLI\fx\src\builddf.err). What is fx folder all about and why am I getting errors when I am adding new code to vm and fjit folders. Cheers Chris ---xml\binplace : error BNP0000: Unable to place file objdf\rotor_x86\System.Xml.dll - exiting. ---sys\binplace : error BNP0000: Unable to place file objdf\rotor_x86\System.dll - exiting. ____________________________________________________________ Get advanced SPAM filtering on Webmail or POP Mail ... Get Lycos Mail! http://login.mail.lycos.com/r/referral?aid=27005
