On 08/20/02 Gaurav Vaish wrote: > The corlib.dll goes out of sync with its runtime field when I compile a > small program on Mono. :( > > Attaching the program (useless) and the log, of the result of executing: > mono --debug --trace hello.cs > > Also, during fresh compilation today, I found two unusual errors. While > executing monoburg, the file libglib.so.2.0 was reported missing, though > it's in /usr/local/lib with the path well set in /etc/ld.so.conf. I had to > explicitly set LD_LIBRARY_PATH to make it work !! > > Any clues on how to rectify the problems?
If you use mono from cvs, you need to be prepared for changes in the runtime internals. This means that you should keep a working setup before blindling updating (a working setup may just be the last released tarball or a recent binary snapshot). Usually, compiling corlib with mcs before recompiling the C runtime does the right thing (but it may not always work). lupus -- ----------------------------------------------------------------- [EMAIL PROTECTED] debian/rules [EMAIL PROTECTED] Monkeys do it better _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
