[Mono-dev] Building mono-core

Alexander Köplinger alkpli at microsoft.com
Fri Feb 2 16:36:38 UTC 2018

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 <neale at sinenomine.net<mailto:neale at 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


From: Neale Ferguson <neale at sinenomine.net<mailto:neale at sinenomine.net>>
Date: Friday, February 2, 2018 at 11:01 AM
To: Alexander Köplinger <alkpli at microsoft.com<mailto:alkpli at microsoft.com>>
Cc: Mono-Devel <mono-devel-list at lists.ximian.com<mailto:mono-devel-list at 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?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dot.net/pipermail/mono-devel-list/attachments/20180202/f07adf1f/attachment.html>

More information about the Mono-devel-list mailing list