y 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 simp
ly, 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
0 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
essing 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
occurre
/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"
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"
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, 20
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 erro
s not resolved and if it or something else is
causing the build fail?
On Oct 20, 2016 6:55 AM, "Cyd Haselton" wrote:
> 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 bui
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 previo
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
tion 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 1
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
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, Cy
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-mon
our
> 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&qu
essing 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:
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
>
>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 bui
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,
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 1
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, "Mare
rap 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
>> boo
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?
>
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
'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 c
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.
>
>
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 leavin
g then the recommended way is to use monolite if you build from
> git master: https://github.com/mono/mono#if-you-dont-have-a-
> working-mono-installation
>
> - Alex
>
> On 12 Oct 2016, at 20:02, Cyd Haselton wrote:
>
> Hello Ludovic,
>
> Would the missing 'last'
Hello Ludovic,
Would the missing 'last' field cause the SIGSEGV?
Cyd
On Oct 12, 2016 12:18 PM, "Cyd Haselton" wrote:
>
> Full output of './mono/mini/mono -V' here: http://pastebin.com/xZw3qhVD
>
>
> On Oct 12, 2016 12:12 PM, "Cyd Haselt
Full output of './mono/mini/mono -V' here: http://pastebin.com/xZw3qhVD
On Oct 12, 2016 12:12 PM, "Cyd Haselton" wrote:
> Since I don't have a working mcs installed, I'm using the snapshots
> available from the download site here: http://download.mono-project
7.0.593/4e441ec
On Oct 11, 2016 10:06 AM, "Ludovic Henry" wrote:
> 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
>
>
Full backtrace log posted here: http://pastebin.com/ncbnBWxh
Any ideas welcome.
On Oct 9, 2016 6:22 PM, "Cyd Haselton" wrote:
> Finally got back to this. Added gdb to the mono-wrapper script and got the
> following:
>
> Temporary breakpoint 1, main (argc=24, argv=0x7ff
]
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" wrote:
> Will do. Termux h
he runtime and figure out
> what is breaking for you on your setup.
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton
> *Date: *Thursday, September 22, 2016 at 8:00 PM
> *To: *Miguel de Icaza , mono-devel <
> mono-devel-l...@lists.ximian.com>
> *Subject: *Re:
warnings I've posted.
On Sep 22, 2016 4:57 PM, "Miguel de Icaza" wrote:
> Hello Cyd,
>
>
>
> I do not recall, what platform is this?
>
>
>
> Miguel.
>
>
>
> *From: *Cyd Haselton
> *Date: *Thursday, September 22, 2016 at 5:20 PM
> *To
our
application.
=
On Sep 21, 2016 4:36 PM, "Cyd Haselton" 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 bu
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 usi
: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
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 usua
, 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
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 ther
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 scrip
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
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
So…download the latest tarball? Or run make get-monolite-latest?
On Sep 19, 2016 9:27 AM, "Miguel de Icaza" wrote:
> It is still stale.
>
>
>
> *From: *Cyd Haselton
> *Date: *Monday, September 19, 2016 at 10:04 AM
> *To: *Miguel de Icaza
> *Cc: *"mon
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" wrote:
> Hello,
>
>
>
> You do not have a clean checkout.
>
>
>
> Miguel.
>
>
>
> *Fro
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
>
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
49 matches
Mail list logo
