[Mono-dev] Problem with mcs build
chaselton at gmail.com
Fri Oct 21 20:34:22 UTC 2016
Building a simple hello world worked. Running it with the runtime worked as
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 'continue') the build runs and exits normally.
I'm guessing this means either some reference is missing or incorrect for
the basic.exe build, there's a bug in one of the source files for basic.exe
or the Makefile for basic.exe has a bug. Unfortunately, without some help
on how to make the monolite bootstrap output more useful info than just
silently failing, or throwing useless make errors, I'm at a dead end.
I'll google, but any ideas are appreciated.
On Oct 21, 2016 3:11 PM, "Cyd Haselton" <chaselton at gmail.com> wrote:
> 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, "Marek Safar" <marek.safar at gmail.com> wrote:
> 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: *** [../build/executable.make:116: ../class/lib/basic/basic.exe] Error 1
> On Fri, Oct 21, 2016 at 11:50 AM, Cyd Haselton <chaselton at gmail.com>
>> 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
>> Loading assembly `Microsoft.CSharp.dll'
>> [LWP 1665 exited]
>> [LWP 1650 exited]
>> [Inferior 1 (process 1650) exited with code 01]
>> I'm guessing the code 01 is for the SDK not resolved warning, so not an
>> Given that, and the info in previous email, any thoughts on why basic.exe
>> is not building?
>> On Oct 20, 2016 8:56 PM, "Cyd Haselton" <chaselton at gmail.com> wrote:
>> I manually re-ran the last command before the build failed. No errors
>> occurred, but basic.exe did not build.
>> I manually re-ran the last command again after adding --mcs-debug 2 and
>> -warn:4 to the command line options. Again, no errors, and no build.exe.
>> Build log is here: http://pastebin.com/9KFNWq4p
>> At this point is it safe to assume that the problem isn't with the
>> runtime? If so, why is basic.exe not being built?
>> On Oct 20, 2016 2:28 PM, "Cyd Haselton" <chaselton at gmail.com> wrote:
>>> Or are you talking about the make errors?
>>> On Oct 20, 2016 11:17 AM, "Cyd Haselton" <chaselton at gmail.com> wrote:
>>>> Also, to which error code are you referring? All I'm seeing are the
>>>> make error codes…which aren't very helpful
>>>> On Oct 20, 2016 10:29 AM, "Cyd Haselton" <chaselton at gmail.com> wrote:
>>>>> I ran gdb on the runtime by adding it to mono-wrapper; it runs without
>>>>> On Oct 20, 2016 8:53 AM, "Marek Safar" <marek.safar at gmail.com> wrote:
>>>>>> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list