Re: [Mono-dev] Building mono-core

2018-02-04 Thread Marek Safar via Mono-devel-list
Unfortunately, it’s still the case. It’s on their todo list but it has not been 
yet done.

Marek
From: Alexander Köplinger <alk...@microsoft.com>
Date: Friday, 2 February 2018 at 14:35
To: Neale Ferguson <ne...@sinenomine.net>
Cc: Marek Safar <mas...@microsoft.com>, Mono Devel Mailing List 
<mono-devel-list@lists.dot.net>
Subject: Re: [Mono-dev] Building mono-core

Hmm, the question is if the System.Reflection.Metadata.dll wasn't updated in 
Roslyn yet or there's some other issue. Marek might now more about it.


On 2 Feb 2018, at 20:17, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

Did. Still throwing the “Not little endian” exception.


If I remember correctly the issue was fixed in System.Reflection.Metadata.dll 
but Roslyn still needed to pick up the fixed version. That might have happened 
in the meantime, best to just try :)


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


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
I guess the question is "whose System.Reflection.Metadata is used, when, by 
whom?" i.e. where does the fix exist and not exist?


Sent from Outlook<http://aka.ms/weboutlook>


From: Neale Ferguson <ne...@sinenomine.net>
Sent: 02 February 2018 14:17
To: Alexander Köplinger; Jo Shields
Cc: Mono Devel Mailing List
Subject: Re: [Mono-dev] Building mono-core

Did. Still throwing the “Not little endian” exception.


If I remember correctly the issue was fixed in System.Reflection.Metadata.dll 
but Roslyn still needed to pick up the fixed version. That might have happened 
in the meantime, best to just try :)
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Hmm, the question is if the System.Reflection.Metadata.dll wasn't updated in 
Roslyn yet or there's some other issue. Marek might now more about it.


On 2 Feb 2018, at 20:17, Neale Ferguson 
> wrote:

Did. Still throwing the “Not little endian” exception.


If I remember correctly the issue was fixed in System.Reflection.Metadata.dll 
but Roslyn still needed to pick up the fixed version. That might have happened 
in the meantime, best to just try :)

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


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Neale Ferguson
Did. Still throwing the “Not little endian” exception.


If I remember correctly the issue was fixed in System.Reflection.Metadata.dll 
but Roslyn still needed to pick up the fixed version. That might have happened 
in the meantime, best to just try :)
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
If I remember correctly the issue was fixed in System.Reflection.Metadata.dll 
but Roslyn still needed to pick up the fixed version. That might have happened 
in the meantime, best to just try :)

On 2 Feb 2018, at 19:03, Jo Shields 
<joshi...@microsoft.com<mailto:joshi...@microsoft.com>> wrote:

Looks like corefx owns it. I don't see an open issue on GH about it though? Am 
I looking in the wrong place, Alex?

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Sent: Friday, February 2, 2018 12:49:45 PM
To: Jo Shields; Alexander Köplinger
Cc: Mono Devel Mailing List
Subject: Re: [Mono-dev] Building mono-core

I assume System.Reflection.Metadata.dll is still housed at Microsoft and the 
big-endian fix for it that enables Roslyn to run is still to surface?

From: Jo Shields <joshi...@microsoft.com<mailto:joshi...@microsoft.com>>
Date: Friday, February 2, 2018 at 12:42 PM
To: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>, 
Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

Relevant pull request: 
https://github.com/mono/mono/pull/5251<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmono%2Fmono%2Fpull%2F5251=02%7C01%7Cjoshield%40microsoft.com%7C8e22021ef645417fd25708d56a655966%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531905905226490=WgIbcwiKnd4qI1TzIN6H9qnGohIQHVKio3Ty0SqtDjo%3D=0>

Mono is now the canonical home of Roslyn, and MSbuild uses the Mono-provided 
binaries, not its own.

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


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
Looks like corefx owns it. I don't see an open issue on GH about it though? Am 
I looking in the wrong place, Alex?

Get Outlook for iOS<https://aka.ms/o0ukef>

From: Neale Ferguson <ne...@sinenomine.net>
Sent: Friday, February 2, 2018 12:49:45 PM
To: Jo Shields; Alexander Köplinger
Cc: Mono Devel Mailing List
Subject: Re: [Mono-dev] Building mono-core

I assume System.Reflection.Metadata.dll is still housed at Microsoft and the 
big-endian fix for it that enables Roslyn to run is still to surface?

From: Jo Shields <joshi...@microsoft.com<mailto:joshi...@microsoft.com>>
Date: Friday, February 2, 2018 at 12:42 PM
To: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>, 
Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

Relevant pull request: 
https://github.com/mono/mono/pull/5251<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmono%2Fmono%2Fpull%2F5251=02%7C01%7Cjoshield%40microsoft.com%7C8e22021ef645417fd25708d56a655966%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531905905226490=WgIbcwiKnd4qI1TzIN6H9qnGohIQHVKio3Ty0SqtDjo%3D=0>

Mono is now the canonical home of Roslyn, and MSbuild uses the Mono-provided 
binaries, not its own.
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
http://lists.dot.net/mailman/listinfo/mono-devel-list


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Jo Shields via Mono-devel-list
Relevant pull request: https://github.com/mono/mono/pull/5251

Mono is now the canonical home of Roslyn, and MSbuild uses the Mono-provided 
binaries, not its own.



Sent from Outlook<http://aka.ms/weboutlook>


From: Alexander Köplinger
Sent: 02 February 2018 12:06
To: Neale Ferguson
Cc: Mono Devel Mailing List; Jo Shields
Subject: Re: [Mono-dev] Building mono-core

Hm, that's a packaging question for Jo (added on CC).


On 2 Feb 2018, at 18:03, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

What’s the proposed fix for msbuild living in –devel and msbuild? Will msbuild 
contain all the Roslyn stuff that can be removed from -devel?

From: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Date: Friday, February 2, 2018 at 11:43 AM
To: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

Ahh, sorry, you're talking about the mono-core.spec :D

Yes, replacing .pdb there should work. I guess we can take that improvement as 
well?


On 2 Feb 2018, at 17:41, Alexander Köplinger via Mono-devel-list 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>> wrote:

Which %files entry are you talking about?


On 2 Feb 2018, at 17:39, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

I got rid of the pdbs from the %files sections and rebuilt so the logs have 
been overwritten. I just replaced the %files entries that had .exe* with 
.* as that would work for exe/exe.so/pdb/mdb.

From: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Date: Friday, February 2, 2018 at 11:36 AM
To: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

This is the PR template that was inherited from the upstream repo, I just 
changed the copy in our fork :)

For the PDBs: they are only generated by Roslyn csc which I think isn't the 
default on s390x. However, we shouldn't _require_ them anywhere, it should 
fallback to picking the .mdb's from mcs.
Could you please post a full build log?

- Alex


On 2 Feb 2018, at 17:29, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

I cloned mono/boringssl, created a branch, made my changes, committed and 
pushed them. When I went to generate a PR:

Please do not send pull requests to the BoringSSL repository.

We do, however, take contributions gladly.

See 
https://boringssl.googlesource.com/boringssl/+/master/CONTRIBUTING.md<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fboringssl.googlesource.com%2Fboringssl%2F%2B%2Fmaster%2FCONTRIBUTING.md=02%7C01%7Calkpli%40microsoft.com%7Ccf319b8103724694a3c608d56a5b819f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531863611649124=M94cyKQ6N3qb7xJ8XS%2FLFrVe5gmMgCtztHDKO4EKoBA%3D=0>

Thanks!

From: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Date: Friday, February 2, 2018 at 11:01 AM
To: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Cc: Mono-Devel 
<mono-devel-l...@lists.ximian.com<mailto:mono-devel-l...@lists.ximian.com>>
Subject: Re: [Mono-dev] Building mono-core


Hey Neale, would you mind opening a pull request on GitHub with the BTLS 
changes for s390x?
- Will do. I’ll checkout the latest copy and reapply

Could you please list which pdb's it complains about?
- All of them. No pdb files are created for the s390x build. What are they and 
how are the created?


___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net<mailto:Mono-devel-list@lists.dot.net>
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-devel-list=02%7C01%7Calkpli%40microsoft.com%7C567cbcd1c9c6445403b108d56a5bd6d4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531865043986428=BNnIEDEN9CBA%2B0u6728E2pNoU17%2B13mF38%2BKOJ0bL0s%3D=0


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


Re: [Mono-dev] Building mono-core

2018-02-02 Thread Alexander Köplinger via Mono-devel-list
Hm, that's a packaging question for Jo (added on CC).


On 2 Feb 2018, at 18:03, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

What’s the proposed fix for msbuild living in –devel and msbuild? Will msbuild 
contain all the Roslyn stuff that can be removed from -devel?

From: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Date: Friday, February 2, 2018 at 11:43 AM
To: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

Ahh, sorry, you're talking about the mono-core.spec :D

Yes, replacing .pdb there should work. I guess we can take that improvement as 
well?


On 2 Feb 2018, at 17:41, Alexander Köplinger via Mono-devel-list 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>> wrote:

Which %files entry are you talking about?


On 2 Feb 2018, at 17:39, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

I got rid of the pdbs from the %files sections and rebuilt so the logs have 
been overwritten. I just replaced the %files entries that had .exe* with 
.* as that would work for exe/exe.so/pdb/mdb.

From: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Date: Friday, February 2, 2018 at 11:36 AM
To: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Cc: Mono Devel Mailing List 
<mono-devel-list@lists.dot.net<mailto:mono-devel-list@lists.dot.net>>
Subject: Re: [Mono-dev] Building mono-core

This is the PR template that was inherited from the upstream repo, I just 
changed the copy in our fork :)

For the PDBs: they are only generated by Roslyn csc which I think isn't the 
default on s390x. However, we shouldn't _require_ them anywhere, it should 
fallback to picking the .mdb's from mcs.
Could you please post a full build log?

- Alex


On 2 Feb 2018, at 17:29, Neale Ferguson 
<ne...@sinenomine.net<mailto:ne...@sinenomine.net>> wrote:

I cloned mono/boringssl, created a branch, made my changes, committed and 
pushed them. When I went to generate a PR:

Please do not send pull requests to the BoringSSL repository.

We do, however, take contributions gladly.

See 
https://boringssl.googlesource.com/boringssl/+/master/CONTRIBUTING.md<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fboringssl.googlesource.com%2Fboringssl%2F%2B%2Fmaster%2FCONTRIBUTING.md=02%7C01%7Calkpli%40microsoft.com%7Ccf319b8103724694a3c608d56a5b819f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531863611649124=M94cyKQ6N3qb7xJ8XS%2FLFrVe5gmMgCtztHDKO4EKoBA%3D=0>

Thanks!

From: Neale Ferguson <ne...@sinenomine.net<mailto:ne...@sinenomine.net>>
Date: Friday, February 2, 2018 at 11:01 AM
To: Alexander Köplinger <alk...@microsoft.com<mailto:alk...@microsoft.com>>
Cc: Mono-Devel 
<mono-devel-l...@lists.ximian.com<mailto:mono-devel-l...@lists.ximian.com>>
Subject: Re: [Mono-dev] Building mono-core


Hey Neale, would you mind opening a pull request on GitHub with the BTLS 
changes for s390x?
- Will do. I’ll checkout the latest copy and reapply

Could you please list which pdb's it complains about?
- All of them. No pdb files are created for the s390x build. What are they and 
how are the created?


___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net<mailto:Mono-devel-list@lists.dot.net>
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-devel-list=02%7C01%7Calkpli%40microsoft.com%7C567cbcd1c9c6445403b108d56a5bd6d4%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531865043986428=BNnIEDEN9CBA%2B0u6728E2pNoU17%2B13mF38%2BKOJ0bL0s%3D=0


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


Re: [Mono-dev] Building mono-core

2018-02-01 Thread Alexander Köplinger via Mono-devel-list
Hey Neale, would you mind opening a pull request on GitHub with the BTLS 
changes for s390x?

Could you please list which pdb's it complains about?

- Alex

On 1 Feb 2018, at 21:44, Neale Ferguson 
> wrote:

Hi,
 I found the 5.8 src rpm (thanks Rick). I attempted a build and failed as 
%files specified several *.pdb files that didn’t get built as well as Btls 
which need to be narch’d until I push my boringssl changes (attached if you are 
interested). Do I just exclude the pdb files or should they have been created?

Neale
___
Mono-devel-list mailing list
Mono-devel-list@lists.dot.net
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.dot.net%2Fmailman%2Flistinfo%2Fmono-devel-list=02%7C01%7Calkpli%40microsoft.com%7C610dc093fbc64bc2c02e08d569b4952f%7Cee3303d7fb734b0c8589bcd847f1c277%7C1%7C0%7C636531146681680559=i%2F%2BvWDlihuRzezu%2F30qCsFRFqb4BPZi7PZfgprkQtyw%3D=0

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