Re: [Mono-dev] Problem with mcs build

2016-10-22 Thread Cyd Haselton
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 files and re-ran ./configure. The build is
progressing past the error posted previously
(mcs/build/executable.make:116) and running 'ls mcs/class/lib/basic' shows
that executables are being built.

On Oct 21, 2016 3:34 PM, "Cyd Haselton"  wrote:

> 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 '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"  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"  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[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe] 
>> Error 1
>>
>> Marek
>>
>>
>> On Fri, Oct 21, 2016 at 11:50 AM, Cyd Haselton 
>> wrote:
>>
>>> 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 code 01 is for the SDK not resolved warning, so not an
>>> issue.
>>>
>>> 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"  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"  wrote:
>>>
 Or are you talking about the make errors?

 On Oct 20, 2016 11:17 AM, "Cyd Haselton"  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"  wrote:
>
>> I ran gdb on the runtime by adding it to mono-wrapper; it runs
>> without errors.
>>
>> On Oct 20, 2016 8:53 AM, "Marek Safar"  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.
>>>
>>> Marek
>>> ​
>>>
>>
>>>
>>
>>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-21 Thread Cyd Haselton
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 '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"  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"  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[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe] 
> Error 1
>
> Marek
>
>
> On Fri, Oct 21, 2016 at 11:50 AM, Cyd Haselton 
> wrote:
>
>> 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 code 01 is for the SDK not resolved warning, so not an
>> issue.
>>
>> 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"  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"  wrote:
>>
>>> Or are you talking about the make errors?
>>>
>>> On Oct 20, 2016 11:17 AM, "Cyd Haselton"  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"  wrote:

> I ran gdb on the runtime by adding it to mono-wrapper; it runs without
> errors.
>
> On Oct 20, 2016 8:53 AM, "Marek Safar"  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.
>>
>> Marek
>> ​
>>
>
>>
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-21 Thread Cyd Haselton
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"  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[7]: *** [../build/executable.make:116:
../class/lib/basic/basic.exe] Error 1

Marek


On Fri, Oct 21, 2016 at 11:50 AM, Cyd Haselton  wrote:

> 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 code 01 is for the SDK not resolved warning, so not an
> issue.
>
> 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"  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"  wrote:
>
>> Or are you talking about the make errors?
>>
>> On Oct 20, 2016 11:17 AM, "Cyd Haselton"  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"  wrote:
>>>
 I ran gdb on the runtime by adding it to mono-wrapper; it runs without
 errors.

 On Oct 20, 2016 8:53 AM, "Marek Safar"  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.
>
> Marek
> ​
>

>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-21 Thread Marek Safar
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  wrote:

> 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 code 01 is for the SDK not resolved warning, so not an
> issue.
>
> 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"  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"  wrote:
>
>> Or are you talking about the make errors?
>>
>> On Oct 20, 2016 11:17 AM, "Cyd Haselton"  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"  wrote:
>>>
 I ran gdb on the runtime by adding it to mono-wrapper; it runs without
 errors.

 On Oct 20, 2016 8:53 AM, "Marek Safar"  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.
>
> Marek
> ​
>

>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-21 Thread Cyd Haselton
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 code 01 is for the SDK not resolved warning, so not an
issue.

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"  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"  wrote:

> Or are you talking about the make errors?
>
> On Oct 20, 2016 11:17 AM, "Cyd Haselton"  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"  wrote:
>>
>>> I ran gdb on the runtime by adding it to mono-wrapper; it runs without
>>> errors.
>>>
>>> On Oct 20, 2016 8:53 AM, "Marek Safar"  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.

 Marek
 ​

>>>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-20 Thread Marek Safar
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
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-10-20 Thread Cyd Haselton
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 exception error…just the
'warning: SDK path could not be resolved.'

I have a hunch that it's something to do with Mono.CSharp.Location, but
I'll post build logs when I've uploaded them.

On Oct 20, 2016 2:52 AM, "Marek Safar"  wrote:

> You are still missing some of required runtime methods to bootstrap. At
> this stage we don't have great error reporting but for some reason you are
> missing native implementation for required icall.
>
> Marek
>
> On Wed, Oct 19, 2016 at 8:45 PM, Cyd Haselton  wrote:
>
>> Answer to previous question is 'no.' I ran 'make distclean' then ran
>> configure with 'decimal' removed from --enable-minimal. Same error at same
>> point in build process.
>>
>> Any thoughts?
>>
>> On Oct 19, 2016 12:39 PM, "Cyd Haselton"  wrote:
>>
>>> 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:
>>> Mono.CSharp.InternalErrorException: cs-tokenizer.cs(1664,20):
>>> Mono.CSharp.Tokenizer.adjust_real(System.TypeCode,
>>> Mono.CSharp.Location) ---> Mono.CSharp.InternalErrorException:
>>> cs-tokenizer.cs(1665,3): ---> System.MissingMethodException:
>>> Arg_MissingMethodException   at
>>> Mono.CSharp.DecimalConstant.Emit (Mono.CSharp.EmitContext ec) [0x0002f]
>>> in <117fbdbdcd0745089048f52eb03cb7af>:0
>>>
>>> On Oct 19, 2016 12:25 PM, "Cyd Haselton"  wrote:
>>>
 The clean build still fails, even with the updated monolite.  Do you
 want build logs?

 On Oct 19, 2016 11:49 AM, "Cyd Haselton"  wrote:

> Ran make get-monolite-latest then re-ran make. That failed.  Will run
> make clean, then re-run make now that monolite was updated, but I'm not
> hopeful.
>
> Additional FYI, as a troubleshooting step I symlinked mscorlib.dll to
> the $PREFIX/lib/mono/4.5 location that the build was complaining about.
>
> The build still failed.
>
> On Oct 19, 2016 10:57 AM, "Marek Safar"  wrote:
>
>> 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?
>>>
>>> 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 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
> your runtime.
>
> Marek
>
> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton  > wrote:
>
>> 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
>>>
>>> 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, run make and post build logs from 
>>> that?
>>>
>>> I posted full build logs about four replies back; here are the
>>> links:
>>>
>>> autogen.sh:http://pastebin.com/P4LcBWpZ
>>> make: http://pastebin.com/JvdhWhCC
>>>
>>> On Oct 18, 2016 1:23 PM, "Marek Safar" 
>>> wrote:
>>>
 I asked for "full mono build" not for build of mono subfolder

 On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton <
 chasel...@gmail.com> wrote:

> That's it. You asked me to build in the mono directory…that's
> the result.

Re: [Mono-dev] Problem with mcs build

2016-10-19 Thread Cyd Haselton
Answer to previous question is 'no.' I ran 'make distclean' then ran
configure with 'decimal' removed from --enable-minimal. Same error at same
point in build process.

Any thoughts?

On Oct 19, 2016 12:39 PM, "Cyd Haselton"  wrote:

> 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:
> Mono.CSharp.InternalErrorException: cs-tokenizer.cs(1664,20):
> Mono.CSharp.Tokenizer.adjust_real(System.TypeCode, Mono.CSharp.Location)
> ---> Mono.CSharp.InternalErrorException: cs-tokenizer.cs(1665,3): --->
> System.MissingMethodException: Arg_MissingMethodException
> at Mono.CSharp.DecimalConstant.Emit (Mono.CSharp.EmitContext ec)
> [0x0002f] in <117fbdbdcd0745089048f52eb03cb7af>:0
>
> On Oct 19, 2016 12:25 PM, "Cyd Haselton"  wrote:
>
>> The clean build still fails, even with the updated monolite.  Do you want
>> build logs?
>>
>> On Oct 19, 2016 11:49 AM, "Cyd Haselton"  wrote:
>>
>>> Ran make get-monolite-latest then re-ran make. That failed.  Will run
>>> make clean, then re-run make now that monolite was updated, but I'm not
>>> hopeful.
>>>
>>> Additional FYI, as a troubleshooting step I symlinked mscorlib.dll to
>>> the $PREFIX/lib/mono/4.5 location that the build was complaining about.
>>>
>>> The build still failed.
>>>
>>> On Oct 19, 2016 10:57 AM, "Marek Safar"  wrote:
>>>
 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?
>
> 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 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 your
>>> runtime.
>>>
>>> Marek
>>>
>>> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton 
>>> wrote:
>>>
 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
>
> 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, run make and post build logs from 
> that?
>
> I posted full build logs about four replies back; here are the
> links:
>
> autogen.sh:http://pastebin.com/P4LcBWpZ
> make: http://pastebin.com/JvdhWhCC
>
> On Oct 18, 2016 1:23 PM, "Marek Safar" 
> wrote:
>
>> I asked for "full mono build" not for build of mono subfolder
>>
>> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> That's it. You asked me to build in the mono directory…that's
>>> the result.
>>> When I go back and build in the root source directory it fails
>>> with the same error as you saw in the full build log
>>>
>>> On Oct 18, 2016 10:38 AM, "Marek Safar" 
>>> wrote:
>>>
 and then it stopped or where is the rest of the build output?

 On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton <
 chasel...@gmail.com> wrote:

> 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" <
>> marek.sa...@gmail.com> wrote:
>>
>>> I'd like to see full mono build wherever it fails, just gist
>>> that.
>>>
>>> On Tue, Oct 18, 2016 at 4:53 

Re: [Mono-dev] Problem with mcs build

2016-10-19 Thread Cyd Haselton
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:
Mono.CSharp.InternalErrorException: cs-tokenizer.cs(1664,20):
Mono.CSharp.Tokenizer.adjust_real(System.TypeCode, Mono.CSharp.Location)
---> Mono.CSharp.InternalErrorException: cs-tokenizer.cs(1665,3): --->
System.MissingMethodException: Arg_MissingMethodException   at
Mono.CSharp.DecimalConstant.Emit (Mono.CSharp.EmitContext ec) [0x0002f] in
<117fbdbdcd0745089048f52eb03cb7af>:0

On Oct 19, 2016 12:25 PM, "Cyd Haselton"  wrote:

> The clean build still fails, even with the updated monolite.  Do you want
> build logs?
>
> On Oct 19, 2016 11:49 AM, "Cyd Haselton"  wrote:
>
>> Ran make get-monolite-latest then re-ran make. That failed.  Will run
>> make clean, then re-run make now that monolite was updated, but I'm not
>> hopeful.
>>
>> Additional FYI, as a troubleshooting step I symlinked mscorlib.dll to the
>> $PREFIX/lib/mono/4.5 location that the build was complaining about.
>>
>> The build still failed.
>>
>> On Oct 19, 2016 10:57 AM, "Marek Safar"  wrote:
>>
>>> 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?

 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 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 your
>> runtime.
>>
>> Marek
>>
>> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton 
>> wrote:
>>
>>> 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

 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, run make and post build logs from that?

 I posted full build logs about four replies back; here are the
 links:

 autogen.sh:http://pastebin.com/P4LcBWpZ
 make: http://pastebin.com/JvdhWhCC

 On Oct 18, 2016 1:23 PM, "Marek Safar" 
 wrote:

> I asked for "full mono build" not for build of mono subfolder
>
> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton  > wrote:
>
>> That's it. You asked me to build in the mono directory…that's the
>> result.
>> When I go back and build in the root source directory it fails
>> with the same error as you saw in the full build log
>>
>> On Oct 18, 2016 10:38 AM, "Marek Safar" 
>> wrote:
>>
>>> and then it stopped or where is the rest of the build output?
>>>
>>> On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 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" 
> wrote:
>
>> I'd like to see full mono build wherever it fails, just gist
>> that.
>>
>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> The build fails at the end because of a dependency on
>>> libeglib, so I have to cd to eglib and build there as well. Do 
>>> you want
>>> logs from that build too?
>>>
>>> On Oct 18, 2016 9:08 AM, "Marek Safar" <
>>> 

Re: [Mono-dev] Problem with mcs build

2016-10-19 Thread Marek Safar
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?
>
> 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 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 your
>>> runtime.
>>>
>>> Marek
>>>
>>> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton 
>>> wrote:
>>>
 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
>
> 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, run make and post build logs from that?
>
> I posted full build logs about four replies back; here are the links:
>
> autogen.sh:http://pastebin.com/P4LcBWpZ
> make: http://pastebin.com/JvdhWhCC
>
> On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:
>
>> I asked for "full mono build" not for build of mono subfolder
>>
>> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton 
>> wrote:
>>
>>> That's it. You asked me to build in the mono directory…that's the
>>> result.
>>> When I go back and build in the root source directory it fails with
>>> the same error as you saw in the full build log
>>>
>>> On Oct 18, 2016 10:38 AM, "Marek Safar" 
>>> wrote:
>>>
 and then it stopped or where is the rest of the build output?

 On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
 wrote:

> 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" 
>> wrote:
>>
>>> I'd like to see full mono build wherever it fails, just gist
>>> that.
>>>
>>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 The build fails at the end because of a dependency on libeglib,
 so I have to cd to eglib and build there as well. Do you want logs 
 from
 that build too?

 On Oct 18, 2016 9:08 AM, "Marek Safar" 
 wrote:

> Yes, please
>
> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton <
> chasel...@gmail.com> wrote:
>
>> I've already posted full build logs from root source folder.
>> Do you want me to also cd to mono, run make and post build logs 
>> from that?
>>
>> On Oct 18, 2016 8:30 AM, "Marek Safar" 
>> wrote:
>>
>>> You should not be using make within mcs/mcs if you haven't
>>> compiled mono successfully before that. Start from scratch and 
>>> paste full
>>> log when building from root mono folder.
>>>
>>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 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 I specify when running the top-level configure 
 and/or
 autogen.sh.  Instead they default to /bin/sh, which will 
 definitely error
 out on my platform.  I've patched as many of the offending 
 files I've found.

Re: [Mono-dev] Problem with mcs build

2016-10-19 Thread Cyd Haselton
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 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 your
>> runtime.
>>
>> Marek
>>
>> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton 
>> wrote:
>>
>>> 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

 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, run make and post build logs from that?

 I posted full build logs about four replies back; here are the links:

 autogen.sh:http://pastebin.com/P4LcBWpZ
 make: http://pastebin.com/JvdhWhCC

 On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:

> I asked for "full mono build" not for build of mono subfolder
>
> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton 
> wrote:
>
>> That's it. You asked me to build in the mono directory…that's the
>> result.
>> When I go back and build in the root source directory it fails with
>> the same error as you saw in the full build log
>>
>> On Oct 18, 2016 10:38 AM, "Marek Safar" 
>> wrote:
>>
>>> and then it stopped or where is the rest of the build output?
>>>
>>> On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
>>> wrote:
>>>
 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" 
> wrote:
>
>> I'd like to see full mono build wherever it fails, just gist that.
>>
>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> The build fails at the end because of a dependency on libeglib,
>>> so I have to cd to eglib and build there as well. Do you want logs 
>>> from
>>> that build too?
>>>
>>> On Oct 18, 2016 9:08 AM, "Marek Safar" 
>>> wrote:
>>>
 Yes, please

 On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton <
 chasel...@gmail.com> wrote:

> I've already posted full build logs from root source folder.
> Do you want me to also cd to mono, run make and post build logs 
> from that?
>
> On Oct 18, 2016 8:30 AM, "Marek Safar" 
> wrote:
>
>> You should not be using make within mcs/mcs if you haven't
>> compiled mono successfully before that. Start from scratch and 
>> paste full
>> log when building from root mono folder.
>>
>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> 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 I specify when running the top-level configure 
>>> and/or
>>> autogen.sh.  Instead they default to /bin/sh, which will 
>>> definitely error
>>> out on my platform.  I've patched as many of the offending 
>>> files I've found.
>>>
>>> On Oct 18, 2016 7:54 AM, "Marek Safar" <
>>> marek.sa...@gmail.com> wrote:
>>>
 No, bootstrap process is not deprecated and it's still
 actively used especially when system mono is unavailable or 
 too old.

 Marek

 On Tue, 

Re: [Mono-dev] Problem with mcs build

2016-10-19 Thread Cyd Haselton
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 your
> runtime.
>
> Marek
>
> On Tue, Oct 18, 2016 at 9:58 PM, Cyd Haselton  wrote:
>
>> 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
>>>
>>> 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, run make and post build logs from that?
>>>
>>> I posted full build logs about four replies back; here are the links:
>>>
>>> autogen.sh:http://pastebin.com/P4LcBWpZ
>>> make: http://pastebin.com/JvdhWhCC
>>>
>>> On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:
>>>
 I asked for "full mono build" not for build of mono subfolder

 On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton 
 wrote:

> That's it. You asked me to build in the mono directory…that's the
> result.
> When I go back and build in the root source directory it fails with
> the same error as you saw in the full build log
>
> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>
>> and then it stopped or where is the rest of the build output?
>>
>> On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
>> wrote:
>>
>>> 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" 
 wrote:

> I'd like to see full mono build wherever it fails, just gist that.
>
> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton  > wrote:
>
>> The build fails at the end because of a dependency on libeglib,
>> so I have to cd to eglib and build there as well. Do you want logs 
>> from
>> that build too?
>>
>> On Oct 18, 2016 9:08 AM, "Marek Safar" 
>> wrote:
>>
>>> Yes, please
>>>
>>> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 I've already posted full build logs from root source folder.
 Do you want me to also cd to mono, run make and post build logs 
 from that?

 On Oct 18, 2016 8:30 AM, "Marek Safar" 
 wrote:

> You should not be using make within mcs/mcs if you haven't
> compiled mono successfully before that. Start from scratch and 
> paste full
> log when building from root mono folder.
>
> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
> chasel...@gmail.com> wrote:
>
>> 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 I specify when running the top-level configure 
>> and/or
>> autogen.sh.  Instead they default to /bin/sh, which will 
>> definitely error
>> out on my platform.  I've patched as many of the offending files 
>> I've found.
>>
>> On Oct 18, 2016 7:54 AM, "Marek Safar" 
>> wrote:
>>
>>> 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 <
>>> chasel...@gmail.com> wrote:
>>>
 Ping for any input on pastebin logs (see previous emails)
 and if bootstrapping mcs was/is/will be deprecated.

 On Oct 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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 build
failure occurs in the subdir targeted after mcs/jay.

On Oct 18, 2016 2:58 PM, "Cyd Haselton"  wrote:

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
>
> 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, run make and post build logs from that?
>
> I posted full build logs about four replies back; here are the links:
>
> autogen.sh:http://pastebin.com/P4LcBWpZ
> make: http://pastebin.com/JvdhWhCC
>
> On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:
>
>> I asked for "full mono build" not for build of mono subfolder
>>
>> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton 
>> wrote:
>>
>>> That's it. You asked me to build in the mono directory…that's the result.
>>> When I go back and build in the root source directory it fails with the
>>> same error as you saw in the full build log
>>>
>>> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>>>
 and then it stopped or where is the rest of the build output?

 On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
 wrote:

> 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" 
>> wrote:
>>
>>> I'd like to see full mono build wherever it fails, just gist that.
>>>
>>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>>> wrote:
>>>
 The build fails at the end because of a dependency on libeglib, so
 I have to cd to eglib and build there as well. Do you want logs from 
 that
 build too?

 On Oct 18, 2016 9:08 AM, "Marek Safar" 
 wrote:

> Yes, please
>
> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton  > wrote:
>
>> I've already posted full build logs from root source folder.  Do
>> you want me to also cd to mono, run make and post build logs from 
>> that?
>>
>> On Oct 18, 2016 8:30 AM, "Marek Safar" 
>> wrote:
>>
>>> You should not be using make within mcs/mcs if you haven't
>>> compiled mono successfully before that. Start from scratch and 
>>> paste full
>>> log when building from root mono folder.
>>>
>>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 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 I specify when running the top-level configure 
 and/or
 autogen.sh.  Instead they default to /bin/sh, which will 
 definitely error
 out on my platform.  I've patched as many of the offending files 
 I've found.

 On Oct 18, 2016 7:54 AM, "Marek Safar" 
 wrote:

> 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 <
> chasel...@gmail.com> wrote:
>
>> Ping for any input on pastebin logs (see previous emails) and
>> if bootstrapping mcs was/is/will be deprecated.
>>
>> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
>> wrote:
>>
>>> Still troubleshooting, though I'm running out of ideas.
>>>
>>> Is it possible bootstrapping mcs 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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
>
> 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, run make and post build logs from that?
>
> I posted full build logs about four replies back; here are the links:
>
> autogen.sh:http://pastebin.com/P4LcBWpZ
> make: http://pastebin.com/JvdhWhCC
>
> On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:
>
>> I asked for "full mono build" not for build of mono subfolder
>>
>> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton 
>> wrote:
>>
>>> That's it. You asked me to build in the mono directory…that's the result.
>>> When I go back and build in the root source directory it fails with the
>>> same error as you saw in the full build log
>>>
>>> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>>>
 and then it stopped or where is the rest of the build output?

 On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
 wrote:

> 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" 
>> wrote:
>>
>>> I'd like to see full mono build wherever it fails, just gist that.
>>>
>>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>>> wrote:
>>>
 The build fails at the end because of a dependency on libeglib, so
 I have to cd to eglib and build there as well. Do you want logs from 
 that
 build too?

 On Oct 18, 2016 9:08 AM, "Marek Safar" 
 wrote:

> Yes, please
>
> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton  > wrote:
>
>> I've already posted full build logs from root source folder.  Do
>> you want me to also cd to mono, run make and post build logs from 
>> that?
>>
>> On Oct 18, 2016 8:30 AM, "Marek Safar" 
>> wrote:
>>
>>> You should not be using make within mcs/mcs if you haven't
>>> compiled mono successfully before that. Start from scratch and 
>>> paste full
>>> log when building from root mono folder.
>>>
>>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 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 I specify when running the top-level configure 
 and/or
 autogen.sh.  Instead they default to /bin/sh, which will 
 definitely error
 out on my platform.  I've patched as many of the offending files 
 I've found.

 On Oct 18, 2016 7:54 AM, "Marek Safar" 
 wrote:

> 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 <
> chasel...@gmail.com> wrote:
>
>> Ping for any input on pastebin logs (see previous emails) and
>> if bootstrapping mcs was/is/will be deprecated.
>>
>> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
>> wrote:
>>
>>> Still troubleshooting, though I'm running out of ideas.
>>>
>>> Is it possible bootstrapping mcs was deprecated?
>>>
>>> On Oct 15, 2016 6:52 PM, "Cyd Haselton" 
>>> wrote:
>>>
 I blew away the build directory, downloaded the 10/13
 tarball from mono/sources (http://download.mono-project.
 com/sources/mono/nightly/) and started over from scratch.
 I got the same error that you can see in 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
>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, run make and post build logs from that?

I posted full build logs about four replies back; here are the links:

autogen.sh:http://pastebin.com/P4LcBWpZ
make: http://pastebin.com/JvdhWhCC

On Oct 18, 2016 1:23 PM, "Marek Safar"  wrote:

> I asked for "full mono build" not for build of mono subfolder
>
> On Tue, Oct 18, 2016 at 6:17 PM, Cyd Haselton  wrote:
>
>> That's it. You asked me to build in the mono directory…that's the result.
>> When I go back and build in the root source directory it fails with the
>> same error as you saw in the full build log
>>
>> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>>
>>> and then it stopped or where is the rest of the build output?
>>>
>>> On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
>>> wrote:
>>>
 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"  wrote:
>
>> I'd like to see full mono build wherever it fails, just gist that.
>>
>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>> wrote:
>>
>>> The build fails at the end because of a dependency on libeglib, so I
>>> have to cd to eglib and build there as well. Do you want logs from that
>>> build too?
>>>
>>> On Oct 18, 2016 9:08 AM, "Marek Safar" 
>>> wrote:
>>>
 Yes, please

 On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton 
 wrote:

> I've already posted full build logs from root source folder.  Do
> you want me to also cd to mono, run make and post build logs from 
> that?
>
> On Oct 18, 2016 8:30 AM, "Marek Safar" 
> wrote:
>
>> You should not be using make within mcs/mcs if you haven't
>> compiled mono successfully before that. Start from scratch and paste 
>> full
>> log when building from root mono folder.
>>
>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> 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 I specify when running the top-level configure 
>>> and/or
>>> autogen.sh.  Instead they default to /bin/sh, which will definitely 
>>> error
>>> out on my platform.  I've patched as many of the offending files 
>>> I've found.
>>>
>>> On Oct 18, 2016 7:54 AM, "Marek Safar" 
>>> wrote:
>>>
 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 <
 chasel...@gmail.com> wrote:

> Ping for any input on pastebin logs (see previous emails) and
> if bootstrapping mcs was/is/will be deprecated.
>
> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
> wrote:
>
>> Still troubleshooting, though I'm running out of ideas.
>>
>> Is it possible bootstrapping mcs was deprecated?
>>
>> On Oct 15, 2016 6:52 PM, "Cyd Haselton" 
>> wrote:
>>
>>> I blew away the build directory, downloaded the 10/13
>>> tarball from mono/sources (http://download.mono-project.
>>> com/sources/mono/nightly/) and started over from scratch.
>>> I got the same error that you can see in the pastebin log; 
>>> something in the
>>> build is expecting mscorlib.dll to be installed at 
>>> usr/lib/mono/4.5.
>>>
>>> Just for kicks I created the usr/lib/mono/4.5 directory and
>>> softlinked mscorlib.dll to that location. The build progresses, 
>>> then fails

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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, "Cyd Haselton"  wrote:
>
>> The mono build log is fairly large; pastebin may be slow in displaying
>> the entire log.
>>
>> On Oct 18, 2016 11:17 AM, "Cyd Haselton"  wrote:
>>
>>> That's it. You asked me to build in the mono directory…that's the result.
>>> When I go back and build in the root source directory it fails with the
>>> same error as you saw in the full build log
>>>
>>> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>>>
 and then it stopped or where is the rest of the build output?

 On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
 wrote:

> 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" 
>> wrote:
>>
>>> I'd like to see full mono build wherever it fails, just gist that.
>>>
>>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>>> wrote:
>>>
 The build fails at the end because of a dependency on libeglib, so
 I have to cd to eglib and build there as well. Do you want logs from 
 that
 build too?

 On Oct 18, 2016 9:08 AM, "Marek Safar" 
 wrote:

> Yes, please
>
> On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton  > wrote:
>
>> I've already posted full build logs from root source folder.  Do
>> you want me to also cd to mono, run make and post build logs from 
>> that?
>>
>> On Oct 18, 2016 8:30 AM, "Marek Safar" 
>> wrote:
>>
>>> You should not be using make within mcs/mcs if you haven't
>>> compiled mono successfully before that. Start from scratch and 
>>> paste full
>>> log when building from root mono folder.
>>>
>>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>>> chasel...@gmail.com> wrote:
>>>
 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 I specify when running the top-level configure 
 and/or
 autogen.sh.  Instead they default to /bin/sh, which will 
 definitely error
 out on my platform.  I've patched as many of the offending files 
 I've found.

 On Oct 18, 2016 7:54 AM, "Marek Safar" 
 wrote:

> 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 <
> chasel...@gmail.com> wrote:
>
>> Ping for any input on pastebin logs (see previous emails) and
>> if bootstrapping mcs was/is/will be deprecated.
>>
>> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
>> wrote:
>>
>>> Still troubleshooting, though I'm running out of ideas.
>>>
>>> Is it possible bootstrapping mcs was deprecated?
>>>
>>> On Oct 15, 2016 6:52 PM, "Cyd Haselton" 
>>> wrote:
>>>
 I blew away the build directory, downloaded the 10/13
 tarball from mono/sources (http://download.mono-project.
 com/sources/mono/nightly/) and started over from scratch.
 I got the same error that you can see in the pastebin log; 
 something in the
 build is expecting mscorlib.dll to be installed at 
 usr/lib/mono/4.5.

 Just for kicks I created the usr/lib/mono/4.5 directory and
 softlinked mscorlib.dll to that location. The build 
 progresses, then fails
 with the dreaded 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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, 2016 11:17 AM, "Cyd Haselton"  wrote:
>
>> That's it. You asked me to build in the mono directory…that's the result.
>> When I go back and build in the root source directory it fails with the
>> same error as you saw in the full build log
>>
>> On Oct 18, 2016 10:38 AM, "Marek Safar"  wrote:
>>
>>> and then it stopped or where is the rest of the build output?
>>>
>>> On Tue, Oct 18, 2016 at 5:29 PM, Cyd Haselton 
>>> wrote:
>>>
 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"  wrote:
>
>> I'd like to see full mono build wherever it fails, just gist that.
>>
>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>> wrote:
>>
>>> The build fails at the end because of a dependency on libeglib, so I
>>> have to cd to eglib and build there as well. Do you want logs from that
>>> build too?
>>>
>>> On Oct 18, 2016 9:08 AM, "Marek Safar" 
>>> wrote:
>>>
 Yes, please

 On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton 
 wrote:

> I've already posted full build logs from root source folder.  Do
> you want me to also cd to mono, run make and post build logs from 
> that?
>
> On Oct 18, 2016 8:30 AM, "Marek Safar" 
> wrote:
>
>> You should not be using make within mcs/mcs if you haven't
>> compiled mono successfully before that. Start from scratch and paste 
>> full
>> log when building from root mono folder.
>>
>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton <
>> chasel...@gmail.com> wrote:
>>
>>> 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 I specify when running the top-level configure 
>>> and/or
>>> autogen.sh.  Instead they default to /bin/sh, which will definitely 
>>> error
>>> out on my platform.  I've patched as many of the offending files 
>>> I've found.
>>>
>>> On Oct 18, 2016 7:54 AM, "Marek Safar" 
>>> wrote:
>>>
 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 <
 chasel...@gmail.com> wrote:

> Ping for any input on pastebin logs (see previous emails) and
> if bootstrapping mcs was/is/will be deprecated.
>
> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
> wrote:
>
>> Still troubleshooting, though I'm running out of ideas.
>>
>> Is it possible bootstrapping mcs was deprecated?
>>
>> On Oct 15, 2016 6:52 PM, "Cyd Haselton" 
>> wrote:
>>
>>> I blew away the build directory, downloaded the 10/13
>>> tarball from mono/sources (http://download.mono-project.
>>> com/sources/mono/nightly/) and started over from scratch.
>>> I got the same error that you can see in the pastebin log; 
>>> something in the
>>> build is expecting mscorlib.dll to be installed at 
>>> usr/lib/mono/4.5.
>>>
>>> Just for kicks I created the usr/lib/mono/4.5 directory and
>>> softlinked mscorlib.dll to that location. The build progresses, 
>>> then fails
>>> with the dreaded Mono.CSharp.InternalErrorException error.
>>>
>>> After that error I navigated to mcs/mcs, ran make and got an
>>> error that the build 'cannot find ./../mcs/class/lib/mcs.exe.'  
>>> Which is
>>> odd because the build shouldn't be using mcs.exe; it isn't 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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"  wrote:
>
>> I'd like to see full mono build wherever it fails, just gist that.
>>
>> On Tue, Oct 18, 2016 at 4:53 PM, Cyd Haselton 
>> wrote:
>>
>>> The build fails at the end because of a dependency on libeglib, so I
>>> have to cd to eglib and build there as well. Do you want logs from that
>>> build too?
>>>
>>> On Oct 18, 2016 9:08 AM, "Marek Safar"  wrote:
>>>
 Yes, please

 On Tue, Oct 18, 2016 at 3:53 PM, Cyd Haselton 
 wrote:

> I've already posted full build logs from root source folder.  Do you
> want me to also cd to mono, run make and post build logs from that?
>
> On Oct 18, 2016 8:30 AM, "Marek Safar"  wrote:
>
>> You should not be using make within mcs/mcs if you haven't compiled
>> mono successfully before that. Start from scratch and paste full log when
>> building from root mono folder.
>>
>> On Tue, Oct 18, 2016 at 3:20 PM, Cyd Haselton 
>> wrote:
>>
>>> 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 I specify when running the top-level configure and/or autogen.sh.
>>> Instead they default to /bin/sh, which will definitely error out on my
>>> platform.  I've patched as many of the offending files I've found.
>>>
>>> On Oct 18, 2016 7:54 AM, "Marek Safar" 
>>> wrote:
>>>
 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 was/is/will be deprecated.
>
> On Oct 16, 2016 2:28 PM, "Cyd Haselton" 
> wrote:
>
>> Still troubleshooting, though I'm running out of ideas.
>>
>> Is it possible bootstrapping mcs was deprecated?
>>
>> On Oct 15, 2016 6:52 PM, "Cyd Haselton" 
>> wrote:
>>
>>> I blew away the build directory, downloaded the 10/13 tarball
>>> from mono/sources (http://download.mono-project.
>>> com/sources/mono/nightly/) and started over from scratch.  I
>>> got the same error that you can see in the pastebin log; something 
>>> in the
>>> build is expecting mscorlib.dll to be installed at usr/lib/mono/4.5.
>>>
>>> Just for kicks I created the usr/lib/mono/4.5 directory and
>>> softlinked mscorlib.dll to that location. The build progresses, 
>>> then fails
>>> with the dreaded Mono.CSharp.InternalErrorException error.
>>>
>>> After that error I navigated to mcs/mcs, ran make and got an
>>> error that the build 'cannot find ./../mcs/class/lib/mcs.exe.'  
>>> Which is
>>> odd because the build shouldn't be using mcs.exe; it isn't 
>>> installed on my
>>> system.
>>>
>>> Pastebin of mcs/mcs make errors here:
>>> http://pastebin.com/mxBLYmnH
>>>
>>> Thanks,
>>> Cyd
>>>
>>> On Oct 15, 2016 2:42 PM, "Cyd Haselton" 
>>> wrote:
>>>
 I can't ignore the error as it stops the build completely.
 Key note: I do not have a working mcs; I'm using the monolite
 bootstrap method. In this case, mscorlib.dll…along with other 
 files…IS
 located at mcs/class/lib/monolite

 Here are the requested logs:

 autogen.sh: http://pastebin.com/P4LcBWpZ
 make: http://pastebin.com/JvdhWhCC

 Additionally, here's a pastebin of the list of files in the
 ./mcs/class/lib/monolite directory:
 http://pastebin.com/ZcLLwWHz

 Thanks,
 Cyd

 On Oct 14, 2016 6:17 PM, "Alexander Köplinger" <
 alk...@microsoft.com> wrote:

> That is just the default message that is compiled into the
> runtime, you can ignore it. The MONO_PATH env 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
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 I
specify when running the top-level configure and/or autogen.sh.  Instead
they default to /bin/sh, which will definitely error out on my platform.
I've patched as many of the offending files I've found.

On Oct 18, 2016 7:54 AM, "Marek Safar"  wrote:

> 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 was/is/will be deprecated.
>>
>> On Oct 16, 2016 2:28 PM, "Cyd Haselton"  wrote:
>>
>>> Still troubleshooting, though I'm running out of ideas.
>>>
>>> Is it possible bootstrapping mcs was deprecated?
>>>
>>> On Oct 15, 2016 6:52 PM, "Cyd Haselton"  wrote:
>>>
 I blew away the build directory, downloaded the 10/13 tarball from
 mono/sources (http://download.mono-project.com/sources/mono/nightly/)
 and started over from scratch.  I got the same error that you can see in
 the pastebin log; something in the build is expecting mscorlib.dll to be
 installed at usr/lib/mono/4.5.

 Just for kicks I created the usr/lib/mono/4.5 directory and softlinked
 mscorlib.dll to that location. The build progresses, then fails with the
 dreaded Mono.CSharp.InternalErrorException error.

 After that error I navigated to mcs/mcs, ran make and got an error that
 the build 'cannot find ./../mcs/class/lib/mcs.exe.'  Which is odd because
 the build shouldn't be using mcs.exe; it isn't installed on my system.

 Pastebin of mcs/mcs make errors here: http://pastebin.com/mxBLYmnH

 Thanks,
 Cyd

 On Oct 15, 2016 2:42 PM, "Cyd Haselton"  wrote:

> I can't ignore the error as it stops the build completely.
> Key note: I do not have a working mcs; I'm using the monolite
> bootstrap method. In this case, mscorlib.dll…along with other files…IS
> located at mcs/class/lib/monolite
>
> Here are the requested logs:
>
> autogen.sh: http://pastebin.com/P4LcBWpZ
> make: http://pastebin.com/JvdhWhCC
>
> Additionally, here's a pastebin of the list of files in the
> ./mcs/class/lib/monolite directory: http://pastebin.com/ZcLLwWHz
>
> Thanks,
> Cyd
>
> On Oct 14, 2016 6:17 PM, "Alexander Köplinger" 
> wrote:
>
>> That is just the default message that is compiled into the runtime,
>> you can ignore it. The MONO_PATH env variable controls where Mono tries 
>> to
>> locate the framework assemblies in this case.
>> It is weird though that this is set to /class/lib/monolite, no wonder
>> it can’t find mscorlib.dll there.
>>
>> Can you please share the full build log including
>> autogen.sh/configure invocations and so on in a gist or pastebin?
>>
>> Thanks,
>> Alex
>>
>> On 15 Oct 2016, at 01:07, Cyd Haselton  wrote:
>>
>> So I scrapped everything and downloaded a newer snapshot from the
>> mono/sources site.
>>
>> This time I can't seem to bootstrap the mcs build; the runtime
>> appears to be hardcoded to check for the mscorlib.dll file in
>> $PREFIX/lib/mono/4.5 instead of in the monolite directory.
>>
>> make[2]: Leaving directory '/data/data/com.termux/files/p
>> kg/ps/mono-4.9.0/data' Making all in
>> runtime
>> make[2]: Entering directory '/data/data/com.termux/files/p
>> kg/ps/mono-4.9.0/runtime' if test -w
>> /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs; then :; else
>> chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs;
>> ficd
>> /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs && make
>> --no-print-directory -s NO_DIR_CHECK=1 
>> PROFILES='binary_reference_assemblies
>> net_4_x xbuild_12 xbuild_14  ' CC='gcc -fPIC -fPIE'
>> all-profiles
>> MONO_PATH=/class/lib/monolite: /data/data/com.termux/files/pk
>> g/ps/mono-4.9.0/runtime/mono-wrapper .//class/lib/monolite/basic.ex
>> e   The assembly
>> mscorlib.dll was not found or could not be loaded.
>> It should have been installed in the 
>> `/data/data/com.termux/files/usr/lib/mono/4.5/mscorlib.dll'
>> directory.
>>
>> Any thoughts?
>>
>> On Oct 12, 2016 5:15 PM, "Cyd Haselton"  wrote:
>>
>>> Hello Alex,
>>>
>>> I'm 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Marek Safar
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 was/is/will be deprecated.
>
> On Oct 16, 2016 2:28 PM, "Cyd Haselton"  wrote:
>
>> Still troubleshooting, though I'm running out of ideas.
>>
>> Is it possible bootstrapping mcs was deprecated?
>>
>> On Oct 15, 2016 6:52 PM, "Cyd Haselton"  wrote:
>>
>>> I blew away the build directory, downloaded the 10/13 tarball from
>>> mono/sources (http://download.mono-project.com/sources/mono/nightly/)
>>> and started over from scratch.  I got the same error that you can see in
>>> the pastebin log; something in the build is expecting mscorlib.dll to be
>>> installed at usr/lib/mono/4.5.
>>>
>>> Just for kicks I created the usr/lib/mono/4.5 directory and softlinked
>>> mscorlib.dll to that location. The build progresses, then fails with the
>>> dreaded Mono.CSharp.InternalErrorException error.
>>>
>>> After that error I navigated to mcs/mcs, ran make and got an error that
>>> the build 'cannot find ./../mcs/class/lib/mcs.exe.'  Which is odd because
>>> the build shouldn't be using mcs.exe; it isn't installed on my system.
>>>
>>> Pastebin of mcs/mcs make errors here: http://pastebin.com/mxBLYmnH
>>>
>>> Thanks,
>>> Cyd
>>>
>>> On Oct 15, 2016 2:42 PM, "Cyd Haselton"  wrote:
>>>
 I can't ignore the error as it stops the build completely.
 Key note: I do not have a working mcs; I'm using the monolite bootstrap
 method. In this case, mscorlib.dll…along with other files…IS located at
 mcs/class/lib/monolite

 Here are the requested logs:

 autogen.sh: http://pastebin.com/P4LcBWpZ
 make: http://pastebin.com/JvdhWhCC

 Additionally, here's a pastebin of the list of files in the
 ./mcs/class/lib/monolite directory: http://pastebin.com/ZcLLwWHz

 Thanks,
 Cyd

 On Oct 14, 2016 6:17 PM, "Alexander Köplinger" 
 wrote:

> That is just the default message that is compiled into the runtime,
> you can ignore it. The MONO_PATH env variable controls where Mono tries to
> locate the framework assemblies in this case.
> It is weird though that this is set to /class/lib/monolite, no wonder
> it can’t find mscorlib.dll there.
>
> Can you please share the full build log including autogen.sh/configure
> invocations and so on in a gist or pastebin?
>
> Thanks,
> Alex
>
> On 15 Oct 2016, at 01:07, Cyd Haselton  wrote:
>
> So I scrapped everything and downloaded a newer snapshot from the
> mono/sources site.
>
> This time I can't seem to bootstrap the mcs build; the runtime appears
> to be hardcoded to check for the mscorlib.dll file in $PREFIX/lib/mono/4.5
> instead of in the monolite directory.
>
> make[2]: Leaving directory '/data/data/com.termux/files/p
> kg/ps/mono-4.9.0/data' Making all in
> runtime
> make[2]: Entering directory '/data/data/com.termux/files/p
> kg/ps/mono-4.9.0/runtime' if test -w
> /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs; then :; else chmod
> -R +w /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs;
> ficd
> /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs && make
> --no-print-directory -s NO_DIR_CHECK=1 
> PROFILES='binary_reference_assemblies
> net_4_x xbuild_12 xbuild_14  ' CC='gcc -fPIC -fPIE'
> all-profiles
> MONO_PATH=/class/lib/monolite: /data/data/com.termux/files/pk
> g/ps/mono-4.9.0/runtime/mono-wrapper .//class/lib/monolite/basic.ex
> e   The assembly
> mscorlib.dll was not found or could not be loaded.
> It should have been installed in the 
> `/data/data/com.termux/files/usr/lib/mono/4.5/mscorlib.dll'
> directory.
>
> Any thoughts?
>
> On Oct 12, 2016 5:15 PM, "Cyd Haselton"  wrote:
>
>> Hello Alex,
>>
>> I'm not building from git-master or git; I am using monolite.  I
>> think I mentioned this earlier…if not, apologies for leaving out 
>> important
>> info.
>>
>> I've gotten past the SIGSEGV I mentioned earlier by editing threads.c
>> (see https://github.com/mono/mono/commit/1c9e34cce5e53ec5126d546a
>> 3014bc1493425219
>> ).
>>
>>
>> I've run into a 

Re: [Mono-dev] Problem with mcs build

2016-10-18 Thread Cyd Haselton
Ping for any input on pastebin logs (see previous emails) and if
bootstrapping mcs was/is/will be deprecated.

On Oct 16, 2016 2:28 PM, "Cyd Haselton"  wrote:

> Still troubleshooting, though I'm running out of ideas.
>
> Is it possible bootstrapping mcs was deprecated?
>
> On Oct 15, 2016 6:52 PM, "Cyd Haselton"  wrote:
>
>> I blew away the build directory, downloaded the 10/13 tarball from
>> mono/sources (http://download.mono-project.com/sources/mono/nightly/)
>> and started over from scratch.  I got the same error that you can see in
>> the pastebin log; something in the build is expecting mscorlib.dll to be
>> installed at usr/lib/mono/4.5.
>>
>> Just for kicks I created the usr/lib/mono/4.5 directory and softlinked
>> mscorlib.dll to that location. The build progresses, then fails with the
>> dreaded Mono.CSharp.InternalErrorException error.
>>
>> After that error I navigated to mcs/mcs, ran make and got an error that
>> the build 'cannot find ./../mcs/class/lib/mcs.exe.'  Which is odd because
>> the build shouldn't be using mcs.exe; it isn't installed on my system.
>>
>> Pastebin of mcs/mcs make errors here: http://pastebin.com/mxBLYmnH
>>
>> Thanks,
>> Cyd
>>
>> On Oct 15, 2016 2:42 PM, "Cyd Haselton"  wrote:
>>
>>> I can't ignore the error as it stops the build completely.
>>> Key note: I do not have a working mcs; I'm using the monolite bootstrap
>>> method. In this case, mscorlib.dll…along with other files…IS located at
>>> mcs/class/lib/monolite
>>>
>>> Here are the requested logs:
>>>
>>> autogen.sh: http://pastebin.com/P4LcBWpZ
>>> make: http://pastebin.com/JvdhWhCC
>>>
>>> Additionally, here's a pastebin of the list of files in the
>>> ./mcs/class/lib/monolite directory: http://pastebin.com/ZcLLwWHz
>>>
>>> Thanks,
>>> Cyd
>>>
>>> On Oct 14, 2016 6:17 PM, "Alexander Köplinger" 
>>> wrote:
>>>
 That is just the default message that is compiled into the runtime, you
 can ignore it. The MONO_PATH env variable controls where Mono tries to
 locate the framework assemblies in this case.
 It is weird though that this is set to /class/lib/monolite, no wonder
 it can’t find mscorlib.dll there.

 Can you please share the full build log including autogen.sh/configure
 invocations and so on in a gist or pastebin?

 Thanks,
 Alex

 On 15 Oct 2016, at 01:07, Cyd Haselton  wrote:

 So I scrapped everything and downloaded a newer snapshot from the
 mono/sources site.

 This time I can't seem to bootstrap the mcs build; the runtime appears
 to be hardcoded to check for the mscorlib.dll file in $PREFIX/lib/mono/4.5
 instead of in the monolite directory.

 make[2]: Leaving directory '/data/data/com.termux/files/p
 kg/ps/mono-4.9.0/data' Making all in
 runtime
 make[2]: Entering directory '/data/data/com.termux/files/p
 kg/ps/mono-4.9.0/runtime' if test -w
 /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs; then :; else chmod
 -R +w /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs;
 ficd
 /data/data/com.termux/files/pkg/ps/mono-4.9.0/mcs && make
 --no-print-directory -s NO_DIR_CHECK=1 
 PROFILES='binary_reference_assemblies
 net_4_x xbuild_12 xbuild_14  ' CC='gcc -fPIC -fPIE'
 all-profiles
 MONO_PATH=/class/lib/monolite: /data/data/com.termux/files/pk
 g/ps/mono-4.9.0/runtime/mono-wrapper .//class/lib/monolite/basic.ex
 e   The assembly
 mscorlib.dll was not found or could not be loaded.
 It should have been installed in the 
 `/data/data/com.termux/files/usr/lib/mono/4.5/mscorlib.dll'
 directory.

 Any thoughts?

 On Oct 12, 2016 5:15 PM, "Cyd Haselton"  wrote:

> Hello Alex,
>
> I'm not building from git-master or git; I am using monolite.  I think
> I mentioned this earlier…if not, apologies for leaving out important info.
>
> I've gotten past the SIGSEGV I mentioned earlier by editing threads.c
> (see https://github.com/mono/mono/commit/1c9e34cce5e53ec5126d546a
> 3014bc1493425219
> ).
>
>
> I've run into a new error that seems to occur in sgen. I'm going to
> try building without it enabled.
>
> Cyd
>
> On Oct 12, 2016 1:16 PM, "Alexander Köplinger" 
> wrote:
>
>> If you don’t have a working Mono installed on your system for
>> bootstrapping then the recommended way is to use 

Re: [Mono-dev] Problem with mcs build

2016-10-11 Thread Ludovic Henry via Mono-devel-list
Hi Cyd,

Which mono commit are you based on? It seems like the managed 
System.Threading.InternalThread is missing the “last” field.

Thank you,
Ludovic

From: Mono-devel-list <mono-devel-list-boun...@lists.dot.net> on behalf of Cyd 
Haselton <chasel...@gmail.com>
Date: Tuesday, 11 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%2F%2Fpastebin.com%2FncbnBWxh=01%7C01%7Cluhenry%40microsoft.com%7Cc158682791b74d1bb8f808d3f1de56fe%7C72f988bf86f141af91ab2d7cd011db47%7C1=F%2B7H5U0vVuuUafzUWRFv9faFPA8TBkdVSbWLjGPX%2BEk%3D=0>

Any ideas welcome.

On Oct 9, 2016 6:22 PM, "Cyd Haselton" 
<chasel...@gmail.com<mailto:chasel...@gmail.com>> wrote:

Finally got back to this. Added gdb to the mono-wrapper script and got the 
following:

Temporary breakpoint 1, main (argc=24, argv=0x7ff188) at ./main.c:213   
213 mono_build_date = build_date;   
(gdb) stepi 
[New LWP 6866]  

Thread 1 "Main" 
received signal SIGSEGV, Segmentation fault.
0x005593890e48 in mono_field_get_offset (field=0x0) at class.c:9610 
9610return field->offset;

On Sep 23, 2016 8:01 AM, "Cyd Haselton" 
<chasel...@gmail.com<mailto:chasel...@gmail.com>> wrote:

Will do. Termux has a gdb package available.

You don't see anything obvious from the errors/warnings I've already posted?

On Sep 23, 2016 1:48 AM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Ah, that explains a lot.

At this point, your best bet will be to debug the runtime and figure out what 
is breaking for you on your setup.

Miguel.

From: Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Thursday, September 22, 2016 at 8:00 PM
To: Miguel de Icaza <mig...@microsoft.com<mailto:mig...@microsoft.com>>, 
mono-devel 
<mono-devel-l...@lists.ximian.com<mailto:mono-devel-l...@lists.ximian.com>>
Subject: Re: [Mono-dev] Problem with mcs build


It's Android.  Specifically Termux on Android.  The required libraries…with the 
exception of X11…have been installed via Termux's 'apt install' or built 
on-device.

I realize that on-build Android is not supported; I'm just looking for help on 
this and/or previous errors/warnings I've posted.

On Sep 22, 2016 4:57 PM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello Cyd,

I do not recall, what platform is this?

Miguel.

From: Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Thursday, September 22, 2016 at 5:20 PM
To: mono-devel 
<mono-devel-l...@lists.ximian.com<mailto:mono-devel-l...@lists.ximian.com>>
Cc: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>, 
Miguel de Icaza <mig...@microsoft.com<mailto:mig...@microsoft.com>>
Subject: Re: [Mono-dev] Problem with mcs build


Additional info:

Just to see what would happen…and because I've just about given up hope on 
hearing back from anyone on this issue…I navigated to $(topbuilddir)/mcs/mcs 
and ran make.  Results were:

make[1]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.7.0/mcs/mcs' MCS 
[net_4_x] mcs.exe   


=   
Got a SIGSEGV while executing native code. This usually indicates   
a fatal error in the mono runtime or one of the native 
librariesused by your application.  
 
=

On Sep 21, 2016 4:36 PM, "Cyd Haselton" 
<chasel...@gmail.com<mailto:chasel...@gmail.com>> wrote:

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, "Cyd Haselton" 
<chasel...@gmail.com<mailto:chasel...@gmail.com>> wrote:

Pinging again.

Re: [Mono-dev] Problem with mcs build

2016-10-11 Thread Cyd Haselton
Full backtrace log posted here: http://pastebin.com/ncbnBWxh

Any ideas welcome.

On Oct 9, 2016 6:22 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:

> Finally got back to this. Added gdb to the mono-wrapper script and got the
> following:
>
> Temporary breakpoint 1, main (argc=24, argv=0x7ff188) at
> ./main.c:213   213 mono_build_date =
> build_date;   (gdb)
> stepi
> [New LWP 6866]
>
>Thread 1 "Main"
> received signal SIGSEGV, Segmentation fault.
> 0x005593890e48 in mono_field_get_offset (field=0x0) at
> class.c:9610 9610return field->offset;
>
> On Sep 23, 2016 8:01 AM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
>> Will do. Termux has a gdb package available.
>>
>> You don't see anything obvious from the errors/warnings I've already
>> posted?
>>
>> On Sep 23, 2016 1:48 AM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>>
>>> Ah, that explains a lot.
>>>
>>>
>>>
>>> At this point, your best bet will be to debug the runtime and figure out
>>> what is breaking for you on your setup.
>>>
>>>
>>>
>>> Miguel.
>>>
>>>
>>>
>>> *From: *Cyd Haselton <chasel...@gmail.com>
>>> *Date: *Thursday, September 22, 2016 at 8:00 PM
>>> *To: *Miguel de Icaza <mig...@microsoft.com>, mono-devel <
>>> mono-devel-l...@lists.ximian.com>
>>> *Subject: *Re: [Mono-dev] Problem with mcs build
>>>
>>>
>>>
>>> It's Android.  Specifically Termux on Android.  The required
>>> libraries…with the exception of X11…have been installed via Termux's 'apt
>>> install' or built on-device.
>>>
>>> I realize that on-build Android is not supported; I'm just looking for
>>> help on this and/or previous errors/warnings I've posted.
>>>
>>>
>>>
>>> On Sep 22, 2016 4:57 PM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>>>
>>> Hello Cyd,
>>>
>>>
>>>
>>> I do not recall, what platform is this?
>>>
>>>
>>>
>>> Miguel.
>>>
>>>
>>>
>>> *From: *Cyd Haselton <chasel...@gmail.com>
>>> *Date: *Thursday, September 22, 2016 at 5:20 PM
>>> *To: *mono-devel <mono-devel-l...@lists.ximian.com>
>>> *Cc: *Alexander Köplinger <alk...@microsoft.com>, Miguel de Icaza <
>>> mig...@microsoft.com>
>>> *Subject: *Re: [Mono-dev] Problem with mcs build
>>>
>>>
>>>
>>> Additional info:
>>>
>>> Just to see what would happen…and because I've just about given up hope
>>> on hearing back from anyone on this issue…I navigated to
>>> $(topbuilddir)/mcs/mcs and ran make.  Results were:
>>>
>>> make[1]: Entering directory '/data/data/com.termux/files/p
>>> kg/ps/mono-4.7.0/mcs/mcs' MCS [net_4_x]
>>> mcs.exe
>>>
>>>
>>> 
>>> =   Got a SIGSEGV while executing native
>>> code. This usually indicates   a fatal error in
>>> the mono runtime or one of the native libraries
>>> used by your application.
>>>
>>> =
>>>
>>>
>>>
>>> On Sep 21, 2016 4:36 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>>>
>>> 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, "Cyd Haselton" <chasel...@gmail.com> wrote:
>>>
>>> Pinging again. Any ideas as to where I should be looking for the problem?
>>>
>>> FYI, while waiting I dumped the help for the bootstrap compiler for
>>> clues and found this:
>>>
>>> 
>>> -reference:ALIAS=A   Imports metadata using specified extern alias
>>> (short: -r)
>>> -sdk:VERSION Specifies SDK version of referenced
>>> assemblies

Re: [Mono-dev] Problem with mcs build

2016-09-23 Thread Cyd Haselton
Will do. Termux has a gdb package available.

You don't see anything obvious from the errors/warnings I've already posted?

On Sep 23, 2016 1:48 AM, "Miguel de Icaza" <mig...@microsoft.com> wrote:

> Ah, that explains a lot.
>
>
>
> At this point, your best bet will be to debug the runtime and figure out
> what is breaking for you on your setup.
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Thursday, September 22, 2016 at 8:00 PM
> *To: *Miguel de Icaza <mig...@microsoft.com>, mono-devel <
> mono-devel-l...@lists.ximian.com>
> *Subject: *Re: [Mono-dev] Problem with mcs build
>
>
>
> It's Android.  Specifically Termux on Android.  The required
> libraries…with the exception of X11…have been installed via Termux's 'apt
> install' or built on-device.
>
> I realize that on-build Android is not supported; I'm just looking for
> help on this and/or previous errors/warnings I've posted.
>
>
>
> On Sep 22, 2016 4:57 PM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>
> Hello Cyd,
>
>
>
> I do not recall, what platform is this?
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Thursday, September 22, 2016 at 5:20 PM
> *To: *mono-devel <mono-devel-l...@lists.ximian.com>
> *Cc: *Alexander Köplinger <alk...@microsoft.com>, Miguel de Icaza <
> mig...@microsoft.com>
> *Subject: *Re: [Mono-dev] Problem with mcs build
>
>
>
> Additional info:
>
> Just to see what would happen…and because I've just about given up hope on
> hearing back from anyone on this issue…I navigated to
> $(topbuilddir)/mcs/mcs and ran make.  Results were:
>
> make[1]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.7.0/mcs/mcs' MCS [net_4_x]
> mcs.exe
>
>
> 
> =   Got a SIGSEGV while executing native
> code. This usually indicates   a fatal error in
> the mono runtime or one of the native libraries
> used by your application.
> =
>
>
>
> On Sep 21, 2016 4:36 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> 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, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Pinging again. Any ideas as to where I should be looking for the problem?
>
> FYI, while waiting I dumped the help for the bootstrap compiler for clues
> and found this:
>
> 
> -reference:ALIAS=A   Imports metadata using specified extern alias (short:
> -r)
> -sdk:VERSION Specifies SDK version of referenced
> assemblies  VERSION can be
> one of: 2, 4, 4.5 (default) or a custom value
> 
>
> The command line right before the two warnings and build failure is this:
>
> MONO_PATH="./../class/lib/monolite:$MONO_PATH"
> /data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper
> ./../class/lib/monolite/basic.exe /codepage:65001 -sdk:4.5 -r:System.dll
> -r:System.Core.dll -r:System.Xml.dll 
> -d:STATIC,NO_SYMBOL_WRITER,NO_AUTHENTICODE
> -d:MONO_FEATURE_THREAD_ABORT -d:MONO_FEATURE_PROCESS_START  -d:NET_4_0
> -d:NET_4_5 -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699
> -lib:./../class/lib/basic   -target:exe -out:../class/lib/basic/basic.exe
> cs-parser.cs  @mcs.exe.sources
>
> Should the "-r" params include paths to those files?
>
>
>
> On Sep 20, 2016 1:06 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Any thoughts?  Or is this another stale build?
>
>
>
> On Tue, Sep 20, 2016 at 8:47 AM, Cyd Haselton <chasel...@gmail.com> 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 usually due to a missing
> System.Drawing.dll, but it is present in the build tree under
> ./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0 and
> 4.5.
>
> Googling the Unhandled Exception error brings up hits from the Unity
> forums and not much else.
>
>
>
> On Sep 20, 2016 7:13 AM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> While waiting for a response I ran 'make clean' then

Re: [Mono-dev] Problem with mcs build

2016-09-22 Thread Cyd Haselton
It's Android.  Specifically Termux on Android.  The required libraries…with
the exception of X11…have been installed via Termux's 'apt install' or
built on-device.

I realize that on-build Android is not supported; I'm just looking for help
on this and/or previous errors/warnings I've posted.

On Sep 22, 2016 4:57 PM, "Miguel de Icaza" <mig...@microsoft.com> wrote:

> Hello Cyd,
>
>
>
> I do not recall, what platform is this?
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Thursday, September 22, 2016 at 5:20 PM
> *To: *mono-devel <mono-devel-l...@lists.ximian.com>
> *Cc: *Alexander Köplinger <alk...@microsoft.com>, Miguel de Icaza <
> mig...@microsoft.com>
> *Subject: *Re: [Mono-dev] Problem with mcs build
>
>
>
> Additional info:
>
> Just to see what would happen…and because I've just about given up hope on
> hearing back from anyone on this issue…I navigated to
> $(topbuilddir)/mcs/mcs and ran make.  Results were:
>
> make[1]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.7.0/mcs/mcs' MCS [net_4_x]
> mcs.exe
>
>
> 
> =   Got a SIGSEGV while executing native
> code. This usually indicates   a fatal error in
> the mono runtime or one of the native libraries
> used by your application.
> =
>
>
>
> On Sep 21, 2016 4:36 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> 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, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Pinging again. Any ideas as to where I should be looking for the problem?
>
> FYI, while waiting I dumped the help for the bootstrap compiler for clues
> and found this:
>
> 
> -reference:ALIAS=A   Imports metadata using specified extern alias (short:
> -r)
> -sdk:VERSION Specifies SDK version of referenced
> assemblies  VERSION can be
> one of: 2, 4, 4.5 (default) or a custom value
> 
>
> The command line right before the two warnings and build failure is this:
>
> MONO_PATH="./../class/lib/monolite:$MONO_PATH"
> /data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper
> ./../class/lib/monolite/basic.exe /codepage:65001 -sdk:4.5 -r:System.dll
> -r:System.Core.dll -r:System.Xml.dll 
> -d:STATIC,NO_SYMBOL_WRITER,NO_AUTHENTICODE
> -d:MONO_FEATURE_THREAD_ABORT -d:MONO_FEATURE_PROCESS_START  -d:NET_4_0
> -d:NET_4_5 -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699
> -lib:./../class/lib/basic   -target:exe -out:../class/lib/basic/basic.exe
> cs-parser.cs  @mcs.exe.sources
>
> Should the "-r" params include paths to those files?
>
>
>
> On Sep 20, 2016 1:06 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Any thoughts?  Or is this another stale build?
>
>
>
> On Tue, Sep 20, 2016 at 8:47 AM, Cyd Haselton <chasel...@gmail.com> 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 usually due to a missing
> System.Drawing.dll, but it is present in the build tree under
> ./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0 and
> 4.5.
>
> Googling the Unhandled Exception error brings up hits from the Unity
> forums and not much else.
>
>
>
> On Sep 20, 2016 7:13 AM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> While waiting for a response I ran 'make clean' then 'make V=1 2>&1 | tee
> mono_build_log.'
>
> I've posted the results here: http://pastebin.com/s3gHQQdg
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fs3gHQQdg=02%7c01%7cmiguel%40microsoft.com%7ca1b5f222d26545b7167e08d3e32e504e%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636101760471232175=WWsVl5M6DDzgpPJUex%2fNxLd45fheb5qo%2bfK44E%2f0HAw%3d>
>
>
>
> On Sep 19, 2016 6:02 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Should I run make clean and try again? Or is there something wrong with
> the mcs/mcs Makefile?
>
>
>
> On Sep 19, 2016 4:33 PM, "Cyd Haselton" <chasel...@gmail.com> wrote:
>
> Downloaded latest tarball, ran autogen

Re: [Mono-dev] Problem with mcs build

2016-09-21 Thread Cyd Haselton
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, "Cyd Haselton"  wrote:

> Pinging again. Any ideas as to where I should be looking for the problem?
>
> FYI, while waiting I dumped the help for the bootstrap compiler for clues
> and found this:
>
> 
> -reference:ALIAS=A   Imports metadata using specified extern alias (short:
> -r)
> -sdk:VERSION Specifies SDK version of referenced
> assemblies  VERSION can be
> one of: 2, 4, 4.5 (default) or a custom value
> 
>
> The command line right before the two warnings and build failure is this:
>
> MONO_PATH="./../class/lib/monolite:$MONO_PATH"
> /data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper
> ./../class/lib/monolite/basic.exe /codepage:65001 -sdk:4.5 -r:System.dll
> -r:System.Core.dll -r:System.Xml.dll 
> -d:STATIC,NO_SYMBOL_WRITER,NO_AUTHENTICODE
> -d:MONO_FEATURE_THREAD_ABORT -d:MONO_FEATURE_PROCESS_START  -d:NET_4_0
> -d:NET_4_5 -d:MONO -d:BOOTSTRAP_BASIC -nowarn:1699
> -lib:./../class/lib/basic   -target:exe -out:../class/lib/basic/basic.exe
> cs-parser.cs  @mcs.exe.sources
>
> Should the "-r" params include paths to those files?
>
> On Sep 20, 2016 1:06 PM, "Cyd Haselton"  wrote:
>
>> 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 usually due to a missing
>>> System.Drawing.dll, but it is present in the build tree under
>>> ./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0
>>> and 4.5.
>>>
>>> Googling the Unhandled Exception error brings up hits from the Unity
>>> forums and not much else.
>>>
>>> On Sep 20, 2016 7:13 AM, "Cyd Haselton"  wrote:
>>>
 While waiting for a response I ran 'make clean' then 'make V=1 2>&1 |
 tee mono_build_log.'

 I've posted the results here: http://pastebin.com/s3gHQQdg

 On Sep 19, 2016 6:02 PM, "Cyd Haselton"  wrote:

> Should I run make clean and try again? Or is there something wrong
> with  the mcs/mcs Makefile?
>
> On Sep 19, 2016 4:33 PM, "Cyd Haselton"  wrote:
>
>> Downloaded latest tarball, ran autogen.sh. It failed at the start of
>> the mcs build because the mono-wrapper, mono and mcs scripts had 
>> #!/bin/sh
>> instead of the correct path.  Fixed that, re-ran make and got the  error
>> from my first email
>>
>> Pastebin here: http://pastebin.com/gdAcRKN6
>>
>> On Sep 19, 2016 2:23 PM, "Cyd Haselton"  wrote:
>>
>>> Er…I *can't* do that because the instructions say that building
>>> from git assumes mono is installed.
>>>
>>> I'll download the latest tarball…
>>>
>>
>>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-09-21 Thread Cyd Haselton
Pinging again. Any ideas as to where I should be looking for the problem?

FYI, while waiting I dumped the help for the bootstrap compiler for clues
and found this:


-reference:ALIAS=A   Imports metadata using specified extern alias (short:
-r)
-sdk:VERSION Specifies SDK version of referenced
assemblies  VERSION can be one
of: 2, 4, 4.5 (default) or a custom value


The command line right before the two warnings and build failure is this:

MONO_PATH="./../class/lib/monolite:$MONO_PATH"
/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper
./../class/lib/monolite/basic.exe /codepage:65001 -sdk:4.5 -r:System.dll
-r:System.Core.dll -r:System.Xml.dll
-d:STATIC,NO_SYMBOL_WRITER,NO_AUTHENTICODE -d:MONO_FEATURE_THREAD_ABORT
-d:MONO_FEATURE_PROCESS_START  -d:NET_4_0 -d:NET_4_5 -d:MONO
-d:BOOTSTRAP_BASIC -nowarn:1699 -lib:./../class/lib/basic   -target:exe
-out:../class/lib/basic/basic.exe cs-parser.cs  @mcs.exe.sources

Should the "-r" params include paths to those files?

On Sep 20, 2016 1:06 PM, "Cyd Haselton"  wrote:

> 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 usually due to a missing
>> System.Drawing.dll, but it is present in the build tree under
>> ./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0
>> and 4.5.
>>
>> Googling the Unhandled Exception error brings up hits from the Unity
>> forums and not much else.
>>
>> On Sep 20, 2016 7:13 AM, "Cyd Haselton"  wrote:
>>
>>> While waiting for a response I ran 'make clean' then 'make V=1 2>&1 |
>>> tee mono_build_log.'
>>>
>>> I've posted the results here: http://pastebin.com/s3gHQQdg
>>>
>>> On Sep 19, 2016 6:02 PM, "Cyd Haselton"  wrote:
>>>
 Should I run make clean and try again? Or is there something wrong
 with  the mcs/mcs Makefile?

 On Sep 19, 2016 4:33 PM, "Cyd Haselton"  wrote:

> Downloaded latest tarball, ran autogen.sh. It failed at the start of
> the mcs build because the mono-wrapper, mono and mcs scripts had #!/bin/sh
> instead of the correct path.  Fixed that, re-ran make and got the  error
> from my first email
>
> Pastebin here: http://pastebin.com/gdAcRKN6
>
> On Sep 19, 2016 2:23 PM, "Cyd Haselton"  wrote:
>
>> Er…I *can't* do that because the instructions say that building from
>> git assumes mono is installed.
>>
>> I'll download the latest tarball…
>>
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-09-20 Thread Cyd Haselton
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 usually due to a missing
> System.Drawing.dll, but it is present in the build tree under
> ./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0 and
> 4.5.
>
> Googling the Unhandled Exception error brings up hits from the Unity
> forums and not much else.
>
> On Sep 20, 2016 7:13 AM, "Cyd Haselton"  wrote:
>
>> While waiting for a response I ran 'make clean' then 'make V=1 2>&1 | tee
>> mono_build_log.'
>>
>> I've posted the results here: http://pastebin.com/s3gHQQdg
>>
>> On Sep 19, 2016 6:02 PM, "Cyd Haselton"  wrote:
>>
>>> Should I run make clean and try again? Or is there something wrong with
>>> the mcs/mcs Makefile?
>>>
>>> On Sep 19, 2016 4:33 PM, "Cyd Haselton"  wrote:
>>>
 Downloaded latest tarball, ran autogen.sh. It failed at the start of
 the mcs build because the mono-wrapper, mono and mcs scripts had #!/bin/sh
 instead of the correct path.  Fixed that, re-ran make and got the  error
 from my first email

 Pastebin here: http://pastebin.com/gdAcRKN6

 On Sep 19, 2016 2:23 PM, "Cyd Haselton"  wrote:

> Er…I *can't* do that because the instructions say that building from
> git assumes mono is installed.
>
> I'll download the latest tarball…
>

___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-09-20 Thread Cyd Haselton
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 usually due to a missing
System.Drawing.dll, but it is present in the build tree under
./external/binary-reference-assemblies/vX.x, where 'X.x' is  2.0, 4.0 and
4.5.

Googling the Unhandled Exception error brings up hits from the Unity forums
and not much else.

On Sep 20, 2016 7:13 AM, "Cyd Haselton"  wrote:

> While waiting for a response I ran 'make clean' then 'make V=1 2>&1 | tee
> mono_build_log.'
>
> I've posted the results here: http://pastebin.com/s3gHQQdg
>
> On Sep 19, 2016 6:02 PM, "Cyd Haselton"  wrote:
>
>> Should I run make clean and try again? Or is there something wrong with
>> the mcs/mcs Makefile?
>>
>> On Sep 19, 2016 4:33 PM, "Cyd Haselton"  wrote:
>>
>>> Downloaded latest tarball, ran autogen.sh. It failed at the start of the
>>> mcs build because the mono-wrapper, mono and mcs scripts had #!/bin/sh
>>> instead of the correct path.  Fixed that, re-ran make and got the  error
>>> from my first email
>>>
>>> Pastebin here: http://pastebin.com/gdAcRKN6
>>>
>>> On Sep 19, 2016 2:23 PM, "Cyd Haselton"  wrote:
>>>
 Er…I *can't* do that because the instructions say that building from
 git assumes mono is installed.

 I'll download the latest tarball…

>>>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Cyd Haselton
Er…I *can't* do that because the instructions say that building from git
assumes mono is installed.

I'll download the latest tarball…
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Alexander Köplinger via Mono-devel-list
> So…download the latest tarball?  Or run make get-monolite-latest?

If you're building from the tarball then you don't need to run "make 
get-monolite-latest" since the tarball includes a monolite already (which will 
be used if a system Mono/mcs can't be found).

> I didn't build from repo because I don't have a working mcs.  I built from 
> downloaded tarball of sources.

That's exactly the use case monolite was invented for :) If you run "make 
get-monolite-latest" then it'll download a monolite that can be used to 
bootstrap the build without relying on a working mcs.

- Alex

From: Mono-devel-list <mono-devel-list-boun...@lists.dot.net> on behalf of Cyd 
Haselton <chasel...@gmail.com>
Date: Monday 19 September 2016 at 18:15
To: Miguel de Icaza <mig...@microsoft.com>
Cc: "mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
Subject: Re: [Mono-dev] Problem with mcs build


So…download the latest tarball?  Or run make get-monolite-latest?

On Sep 19, 2016 9:27 AM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
It is still stale.

From: Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Monday, September 19, 2016 at 10:04 AM
To: Miguel de Icaza <mig...@microsoft.com<mailto:mig...@microsoft.com>>
Cc: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Problem with mcs build


I didn't build from repo because I don't have a working mcs.  I built from 
downloaded tarball of sources.

On Sep 19, 2016 9:00 AM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello,

You do not have a clean checkout.

Miguel.

From: Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Monday, September 19, 2016 at 8:56 AM
To: Miguel de Icaza <mig...@microsoft.com<mailto:mig...@microsoft.com>>
Cc: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: 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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fPme5tx4W=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=dWJ2EOFGLfi9lx8fx%2b40esvGYQx2h6KVUqL3SMUYJxk%3d>
build log: 
http://pastebin.com/puCMusV7<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fpuCMusV7=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=zZL%2bVUEBkVWT%2f%2bOIyxBxKENz0BxVXmO32jfgev1%2bCWI%3d>

On Sep 18, 2016 8:32 PM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello,

Try “make V=1” at the toplevel to get more data.

You might also want to post the full build logs somewhere (not the list) and 
send a link to it.

Migue.
From: Mono-devel-list 
<mono-devel-list-boun...@lists.dot.net<mailto:mono-devel-list-boun...@lists.dot.net>>
 on behalf of Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Saturday, September 17, 2016 at 6:05 PM
To: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: [Mono-dev] Problem with mcs build


I'm currently building mono on Android using Termux and I keep running into the 
same cryptic error when the mcs build starts.

Making all in runtime   
make[2]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime'
if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :; else 
chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; fi
cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s 
PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  ' 
CC='gcc' all-profiles
make[3]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[4]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[5]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[6]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'

NOTE: I added some echo statements in order to output var values…this is one of 
them

MONO_PATH=.//class/lib/mono

Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Cyd Haselton
So…download the latest tarball?  Or run make get-monolite-latest?

On Sep 19, 2016 9:27 AM, "Miguel de Icaza" <mig...@microsoft.com> wrote:

> It is still stale.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Monday, September 19, 2016 at 10:04 AM
> *To: *Miguel de Icaza <mig...@microsoft.com>
> *Cc: *"mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
> *Subject: *Re: [Mono-dev] Problem with mcs build
>
>
>
> I didn't build from repo because I don't have a working mcs.  I built from
> downloaded tarball of sources.
>
>
>
> On Sep 19, 2016 9:00 AM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>
> Hello,
>
>
>
> You do not have a clean checkout.
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Monday, September 19, 2016 at 8:56 AM
> *To: *Miguel de Icaza <mig...@microsoft.com>
> *Cc: *"mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
> *Subject: *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
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fPme5tx4W=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=dWJ2EOFGLfi9lx8fx%2b40esvGYQx2h6KVUqL3SMUYJxk%3d>
> build log: http://pastebin.com/puCMusV7
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fpuCMusV7=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=zZL%2bVUEBkVWT%2f%2bOIyxBxKENz0BxVXmO32jfgev1%2bCWI%3d>
>
>
>
> On Sep 18, 2016 8:32 PM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>
> Hello,
>
>
>
> Try “make V=1” at the toplevel to get more data.
>
>
>
> You might also want to post the full build logs somewhere (not the list)
> and send a link to it.
>
>
>
> Migue.
>
> *From: *Mono-devel-list <mono-devel-list-boun...@lists.dot.net> on behalf
> of Cyd Haselton <chasel...@gmail.com>
> *Date: *Saturday, September 17, 2016 at 6:05 PM
> *To: *"mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
> *Subject: *[Mono-dev] Problem with mcs build
>
>
>
> I'm currently building mono on Android using Termux and I keep running
> into the same cryptic error when the mcs build starts.
>
> Making all in runtime
> make[2]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime'
> if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :;
> else chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs;
> fi
> cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s
> PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  '
> CC='gcc' all-profiles
> make[3]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[4]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[5]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
>
> NOTE: I added some echo statements in order to output var values…this is
> one of them
>
> MONO_PATH=.//class/lib/monolite: /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime/mono-wrapper --verbose
> .//class/lib/monolite/basic.exe
> .//build/deps/basic-profile-check.exe
>   Bootstrap compiler: Mono C# compiler
> version 4.6.0.0make[6]: Leaving
> directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
>
> NOTE:  the jay executable builds successfully.
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> make[7]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> warning CS8001: SDK path could not be resolved
> warning CS1685: The predefined type 
> `System.Security.Permission

Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Miguel de Icaza via Mono-devel-list
It is still stale.

From: Cyd Haselton <chasel...@gmail.com>
Date: Monday, September 19, 2016 at 10:04 AM
To: Miguel de Icaza <mig...@microsoft.com>
Cc: "mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
Subject: Re: [Mono-dev] Problem with mcs build


I didn't build from repo because I don't have a working mcs.  I built from 
downloaded tarball of sources.

On Sep 19, 2016 9:00 AM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello,

You do not have a clean checkout.

Miguel.

From: Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Monday, September 19, 2016 at 8:56 AM
To: Miguel de Icaza <mig...@microsoft.com<mailto:mig...@microsoft.com>>
Cc: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: 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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fPme5tx4W=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=dWJ2EOFGLfi9lx8fx%2b40esvGYQx2h6KVUqL3SMUYJxk%3d>
build log: 
http://pastebin.com/puCMusV7<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fpuCMusV7=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=zZL%2bVUEBkVWT%2f%2bOIyxBxKENz0BxVXmO32jfgev1%2bCWI%3d>

On Sep 18, 2016 8:32 PM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello,

Try “make V=1” at the toplevel to get more data.

You might also want to post the full build logs somewhere (not the list) and 
send a link to it.

Migue.
From: Mono-devel-list 
<mono-devel-list-boun...@lists.dot.net<mailto:mono-devel-list-boun...@lists.dot.net>>
 on behalf of Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Saturday, September 17, 2016 at 6:05 PM
To: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: [Mono-dev] Problem with mcs build


I'm currently building mono on Android using Termux and I keep running into the 
same cryptic error when the mcs build starts.

Making all in runtime   
make[2]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime'
if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :; else 
chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; fi
cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s 
PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  ' 
CC='gcc' all-profiles
make[3]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[4]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[5]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[6]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'

NOTE: I added some echo statements in order to output var values…this is one of 
them

MONO_PATH=.//class/lib/monolite: 
/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper --verbose 
.//class/lib/monolite/basic.exe   
.//build/deps/basic-profile-check.exe   
Bootstrap compiler: Mono C# compiler version 4.6.0.0
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/build'
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/build'
make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/jay'
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/jay'

NOTE:  the jay executable builds successfully.

make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
make[7]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
warning CS8001: SDK path could not be resolved  
warning CS1685: The predefined type 
`System.Security.Permissions.HostProtectionAttribute' is defined multiple 
times. Using definition from `mscorlib.dll'   
/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/class/lib/monolite/mscorlib.dll
 (Loca

Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Cyd Haselton
I didn't build from repo because I don't have a working mcs.  I built from
downloaded tarball of sources.

On Sep 19, 2016 9:00 AM, "Miguel de Icaza" <mig...@microsoft.com> wrote:

> Hello,
>
>
>
> You do not have a clean checkout.
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton <chasel...@gmail.com>
> *Date: *Monday, September 19, 2016 at 8:56 AM
> *To: *Miguel de Icaza <mig...@microsoft.com>
> *Cc: *"mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
> *Subject: *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
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fPme5tx4W=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=dWJ2EOFGLfi9lx8fx%2b40esvGYQx2h6KVUqL3SMUYJxk%3d>
> build log: http://pastebin.com/puCMusV7
> <https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fpuCMusV7=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=zZL%2bVUEBkVWT%2f%2bOIyxBxKENz0BxVXmO32jfgev1%2bCWI%3d>
>
>
>
> On Sep 18, 2016 8:32 PM, "Miguel de Icaza" <mig...@microsoft.com> wrote:
>
> Hello,
>
>
>
> Try “make V=1” at the toplevel to get more data.
>
>
>
> You might also want to post the full build logs somewhere (not the list)
> and send a link to it.
>
>
>
> Migue.
>
> *From: *Mono-devel-list <mono-devel-list-boun...@lists.dot.net> on behalf
> of Cyd Haselton <chasel...@gmail.com>
> *Date: *Saturday, September 17, 2016 at 6:05 PM
> *To: *"mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
> *Subject: *[Mono-dev] Problem with mcs build
>
>
>
> I'm currently building mono on Android using Termux and I keep running
> into the same cryptic error when the mcs build starts.
>
> Making all in runtime
> make[2]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime'
> if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :;
> else chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs;
> fi
> cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s
> PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  '
> CC='gcc' all-profiles
> make[3]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[4]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[5]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
>
> NOTE: I added some echo statements in order to output var values…this is
> one of them
>
> MONO_PATH=.//class/lib/monolite: /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime/mono-wrapper --verbose
> .//class/lib/monolite/basic.exe
> .//build/deps/basic-profile-check.exe
>   Bootstrap compiler: Mono C# compiler
> version 4.6.0.0make[6]: Leaving
> directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
>
> NOTE:  the jay executable builds successfully.
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> make[7]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> warning CS8001: SDK path could not be resolved
> warning CS1685: The predefined type 
> `System.Security.Permissions.HostProtectionAttribute'
> is defined multiple times. Using definition from
> `mscorlib.dll'   /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/class/lib/monolite/mscorlib.dll (Location of the
> symbol related to previous warning) /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/class/lib/monolite/System.dll (Location of the
> symbol related to previous warning)
>
>
> Here's where it errors out.
>
> make[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe]
> Err

Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Miguel de Icaza via Mono-devel-list
Hello,

You do not have a clean checkout.

Miguel.

From: Cyd Haselton <chasel...@gmail.com>
Date: Monday, September 19, 2016 at 8:56 AM
To: Miguel de Icaza <mig...@microsoft.com>
Cc: "mono-devel-list@lists.dot.net" <mono-devel-list@lists.dot.net>
Subject: 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<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fPme5tx4W=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=dWJ2EOFGLfi9lx8fx%2b40esvGYQx2h6KVUqL3SMUYJxk%3d>
build log: 
http://pastebin.com/puCMusV7<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fpastebin.com%2fpuCMusV7=02%7c01%7cmiguel%40microsoft.com%7c1ac3802f4f30468f8ab408d3e08c6921%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636098866069382476=zZL%2bVUEBkVWT%2f%2bOIyxBxKENz0BxVXmO32jfgev1%2bCWI%3d>

On Sep 18, 2016 8:32 PM, "Miguel de Icaza" 
<mig...@microsoft.com<mailto:mig...@microsoft.com>> wrote:
Hello,

Try “make V=1” at the toplevel to get more data.

You might also want to post the full build logs somewhere (not the list) and 
send a link to it.

Migue.
From: Mono-devel-list 
<mono-devel-list-boun...@lists.dot.net<mailto:mono-devel-list-boun...@lists.dot.net>>
 on behalf of Cyd Haselton <chasel...@gmail.com<mailto:chasel...@gmail.com>>
Date: Saturday, September 17, 2016 at 6:05 PM
To: "mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>" 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: [Mono-dev] Problem with mcs build


I'm currently building mono on Android using Termux and I keep running into the 
same cryptic error when the mcs build starts.

Making all in runtime   
make[2]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime'
if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :; else 
chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; fi
cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s 
PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  ' 
CC='gcc' all-profiles
make[3]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[4]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[5]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[6]: Entering directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'

NOTE: I added some echo statements in order to output var values…this is one of 
them

MONO_PATH=.//class/lib/monolite: 
/data/data/com.termux/files/pkg/ps/mono-4.6.0/runtime/mono-wrapper --verbose 
.//class/lib/monolite/basic.exe   
.//build/deps/basic-profile-check.exe   
Bootstrap compiler: Mono C# compiler version 4.6.0.0
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/build'
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/build'
make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/jay'
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/jay'

NOTE:  the jay executable builds successfully.

make[6]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
make[7]: Entering directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
warning CS8001: SDK path could not be resolved  
warning CS1685: The predefined type 
`System.Security.Permissions.HostProtectionAttribute' is defined multiple 
times. Using definition from `mscorlib.dll'   
/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/class/lib/monolite/mscorlib.dll
 (Location of the symbol related to previous warning) 
/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/class/lib/monolite/System.dll 
(Location of the symbol related to previous warning)

Here's where it errors out.

make[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe]
Error 1
make[7]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
make[6]: *** [../build/rules.make:221: do-all] Error 2
make[6]: Leaving directory 
'/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs/mcs'
make[5]: *** [build/rules.make:248: all-recursive] Error 1
make[5]: Leaving directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
make[4]: *** [Makefile

Re: [Mono-dev] Problem with mcs build

2016-09-19 Thread Cyd Haselton
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"  wrote:

> Hello,
>
>
>
> Try “make V=1” at the toplevel to get more data.
>
>
>
> You might also want to post the full build logs somewhere (not the list)
> and send a link to it.
>
>
>
> Migue.
>
> *From: *Mono-devel-list  on behalf
> of Cyd Haselton 
> *Date: *Saturday, September 17, 2016 at 6:05 PM
> *To: *"mono-devel-list@lists.dot.net" 
> *Subject: *[Mono-dev] Problem with mcs build
>
>
>
> I'm currently building mono on Android using Termux and I keep running
> into the same cryptic error when the mcs build starts.
>
> Making all in runtime
> make[2]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime'
> if test -w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs; then :;
> else chmod -R +w /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs;
> fi
> cd /data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs && make  -s
> PROFILES='binary_reference_assemblies net_4_x xbuild_12 xbuild_14  '
> CC='gcc' all-profiles
> make[3]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[4]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[5]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
>
> NOTE: I added some echo statements in order to output var values…this is
> one of them
>
> MONO_PATH=.//class/lib/monolite: /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime/mono-wrapper --verbose
> .//class/lib/monolite/basic.exe
> .//build/deps/basic-profile-check.exe
>   Bootstrap compiler: Mono C# compiler
> version 4.6.0.0make[6]: Leaving
> directory '/data/data/com.termux/files/pkg/ps/mono-4.6.0/mcs'
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/build'
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/jay'
>
> NOTE:  the jay executable builds successfully.
>
> make[6]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> make[7]: Entering directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> warning CS8001: SDK path could not be resolved
> warning CS1685: The predefined type 
> `System.Security.Permissions.HostProtectionAttribute'
> is defined multiple times. Using definition from
> `mscorlib.dll'   /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/class/lib/monolite/mscorlib.dll (Location of the
> symbol related to previous warning) /data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/class/lib/monolite/System.dll (Location of the
> symbol related to previous warning)
>
>
> Here's where it errors out.
>
> make[7]: *** [../build/executable.make:116: ../class/lib/basic/basic.exe]
> Error 1
> make[7]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> make[6]: *** [../build/rules.make:221: do-all] Error
> 2
> make[6]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs/mcs'
> make[5]: *** [build/rules.make:248: all-recursive] Error
> 1
> make[5]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[4]: *** [Makefile:49: profile-do--basic--all] Error
> 2
> make[4]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[3]: *** [Makefile:45: profiles-do--all] Error
> 2
> make[3]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/mcs'
> make[2]: *** [Makefile:543: all-local] Error 2
> make[2]: Leaving directory '/data/data/com.termux/files/
> pkg/ps/mono-4.6.0/runtime'
> make[1]: *** [Makefile:512: all-recursive] Error
> 1  make[1]: Leaving directory
> '/data/data/com.termux/files/pkg/ps/mono-4.6.0'
> make: *** [Makefile:441: all] Error 2
>
> I've upped the debug level of make, added a --verbose flag to
> mono-wrapper…no additional error output is printed to the console.
>
> Has anyone seen this before?
>
> CJH
>
>
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list