Re: [Mono-dev] Problem with mcs build

Of course, almost immediately after sending previous email I believe I've found the problem. Running 'make distclean' in the root build tree fails to delete the *.o, *.lo files in mono/mini, the *.Plo and *.Po files in mono/mini/.libs and the files in mono/mini/.deps. I manually removed those

Re: [Mono-dev] Problem with mcs build

Building a simple hello world worked. Running it with the runtime worked as well. I deleted hello.exe and re-ran the build with gdb added to the mono-wrapper script. When stepping through the build…using various values for 's'…I got a SIGILL. When continuing through the build (i.e. 'start' then

Re: [Mono-dev] Problem with mcs build

But running the command BEFORE the build fail returns zero errors. If you look at the build log I posted in my last email…the one for running the manual command…you can see that it exits with no indication of an error. I'll try building a hello world, see what it does On Oct 21, 2016 6:37 AM,

Re: [Mono-dev] Problem with mcs build

No, the exit code 1 is an error. I don't know where in runtime it happens but for some reason your runtime returns it. Relevant makefile line make[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe] Error 1 Marek On Fri, Oct 21, 2016 at 11:50 AM, Cyd Haselton

Re: [Mono-dev] Problem with mcs build

Additional info: To confirm health of the built runtime I added gdb to the mono-wrapper script and manually re-ran the pre-build fail command again. Loading assembly `Microsoft.CSharp.dll' [LWP 1665 exited] [LWP 1650 exited] [Inferior 1 (process 1650) exited with code 01] I'm guessing the

Re: [Mono-dev] Problem with mcs build

That's just a warning you can safely ignore. What is more important is that basic.exe failed with error code which at this point looks like some sort of runtime error/problem. Marek ​ ___ Mono-devel-list mailing list Mono-devel-list@lists.dot.net

Re: [Mono-dev] Problem with mcs build

Did some searching last night and came across this link: http://koushd.blogspot.com/2009/01/building-mono-for-android.html It has recommendations for building on Android. I ran distclean, then re-ran configure with the recommended switches. The build still fails, but without the unhandled

Re: [Mono-dev] Problem with mcs build

I noticed that the error thrown when the build fails is a 'MissingMethodException' and that it references Mono.CSharp.DecimalConstant.Emit. I disabled decimal in configure with the --enable-minimal option. Could that be causing the error? Here's part of the error: Unhandled Exception:

Re: [Mono-dev] Problem with mcs build

Hi, Try to do `make get-monolite-latest` if that will resolve the issue. jay is using C compiler therefore does not need working C# compiler. On Wed, Oct 19, 2016 at 5:54 PM, Cyd Haselton wrote: > Wouldn't the build of jay fail if the monolite version was out of sync? > >

Re: [Mono-dev] Problem with mcs build

Wouldn't the build of jay fail if the monolite version was out of sync? On Oct 19, 2016 10:01 AM, "Cyd Haselton" wrote: > The monolite files were included with the source tarball, so hopefully > they are in line with the runtime. > > I can always run make

Re: [Mono-dev] Problem with mcs build

The monolite files were included with the source tarball, so hopefully they are in line with the runtime. I can always run make get-monolite-latest. On Oct 19, 2016 8:53 AM, "Marek Safar" wrote: > Hi, > > How did you install monolite? It looks like it's out of sync to

Re: [Mono-dev] Problem with mcs build

One simple question: Since the build in the mono subdir was successful, would building within the mcs subdirs be an appropriate troubleshooting step? I know that the mcs/jay subdir builds successfully before the overall build fails; there's an mcs/jay/jay binary that executes. I'm guessing the

Re: [Mono-dev] Problem with mcs build

Just in case, I ran 'make clean' and redid the build. Link to build log: http://pastebin.com/TBSUNH4x On Oct 18, 2016 2:20 PM, "Cyd Haselton" wrote: > From previous conversation: > > On Oct 18, 2016 9:08 AM, "Marek Safar" wrote: > > Yes, please > >

Re: [Mono-dev] Problem with mcs build

>From previous conversation: On Oct 18, 2016 9:08 AM, "Marek Safar" wrote: Yes, please On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton @gmail.com >wrote: I've already posted full build logs from root source folder. Do you want me to also cd to mono,

Re: [Mono-dev] Problem with mcs build

Do you want me to re-build in root directory and post that log again? On Oct 18, 2016 11:39 AM, "Cyd Haselton" wrote: > Forgot to include mono-dev list > > The mono build log is fairly large; pastebin may be slow in displaying the > entire log. > > On Oct 18, 2016 11:38 AM,

Re: [Mono-dev] Problem with mcs build

Forgot to include mono-dev list The mono build log is fairly large; pastebin may be slow in displaying the entire log. On Oct 18, 2016 11:38 AM, "Cyd Haselton" wrote: > The mono build log is fairly large; pastebin may be slow in displaying the > entire log. > > On Oct 18,

Re: [Mono-dev] Problem with mcs build

Build in mono dir completed successfully Link to logs: http://pastebin.com/2YwrnFCe On Oct 18, 2016 10:05 AM, "Cyd Haselton" wrote: > That's just it; it doesn't fail. I'll post the pastebin links when I have > them. > > On Oct 18, 2016 10:02 AM, "Marek Safar"

Re: [Mono-dev] Problem with mcs build

Thanks Marek, Any input on the logs? In the meantime I've deleted the build tree and re-downloaded the sources so that I can start over from scratch. Don't know if this is relevant but I have noticed that the Makefiles and various other scripts do not pick up the CONFIG_SHELL and SHELL vars that

Re: [Mono-dev] Problem with mcs build

No, bootstrap process is not deprecated and it's still actively used especially when system mono is unavailable or too old. Marek On Tue, Oct 18, 2016 at 12:23 PM, Cyd Haselton wrote: > Ping for any input on pastebin logs (see previous emails) and if > bootstrapping mcs

Re: [Mono-dev] Problem with mcs build

October 2016 at 15:55 To: Miguel de Icaza <mig...@microsoft.com> Cc: mono-devel <mono-devel-l...@lists.ximian.com> Subject: Re: [Mono-dev] Problem with mcs build Full backtrace log posted here: http://pastebin.com/ncbnBWxh<https://na01.safelinks.protection.outlook.com/?url=http%3A%2

Re: [Mono-dev] Problem with mcs build

While waiting for a response I deleted the build tree, downloaded another tarball from the site, unpacked and re-ran 'autogen.sh && make' The build errored out at the same place, with the same prior warnings. At this point I'm at a loss. Any input would be welcome. On Sep 21, 2016 7:10 AM,

Re: [Mono-dev] Problem with mcs build

Any thoughts? Or is this another stale build? On Tue, Sep 20, 2016 at 8:47 AM, Cyd Haselton wrote: > Additionally I Googled the warning that appears before the build error: > warning CS8001: SDK path could not be resolved > > The first two hits mention that the cause is

Re: [Mono-dev] Problem with mcs build

I ran make distclean, reset some env vars and reran the make, using autogen.sh. This time I got a much different error. Here are the links to the config.log and build.log config.log: http://pastebin.com/Pme5tx4W build log: http://pastebin.com/puCMusV7 On Sep 18, 2016 8:32 PM, "Miguel de Icaza"