Re: Help Wanted - Work with MSFT and help finish the port of .NET Core to FreeBSD
If anybody wants to help, it would be great to look at https://github.com/dotnet/coreclr/issues/18481 There is guy working on getting PowerShell working on FreeBSD. (#18067) We got to point where we have semi-working SDK and I'm looking at msbuild problem related to named pipes. Aside from that, this round looks somewhat promising. I made some progress on updating source-build as well as with some caveats it is possible to run Linux SDK under Linux64 emulation. Tomas On 11/8/17, 11:00 PM, "owner-freebsd-m...@freebsd.org on behalf of Russell Haley" wrote: On Wed, Nov 8, 2017 at 10:15 AM, David Naylor wrote: > On Wednesday, 27 September 2017 22:02:43 Russell Haley wrote: >> +1 >> I threw some comments on the open issues. > > Hi > > I hope the porting of .NET Core has been progressing. I must apologise, I > have dropped the ball on updating mono. This will come with a working version > of msbuild which I am sure would be helpful in the porting process. > > I'm slowly picking up the mono porting work on my side, and hope to get > something committed in the next few weeks. > > Do you perhaps have an update on your side? > > Regards > > David Hi David, Tomas has been working dilligently over the last couple of weeks, but I have been in limbo with no computer and no time until a few days ago. The changes Tomas is making have been integrated into the head repos and I am attempting to build from that using the instructions provided on the dotnetcore wiki. Nothing I am doing is unique. Anyone can pull corefx and coreclr repos and follow along in the instructions. https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2Fcorefx%2Fwiki%2FBuilding-.NET-Core--2.x-on-FreeBSD&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7Cd776769e3f7f4b1a217208d5273f819f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636458076071078070&sdata=Pae7%2FT4%2Btt0usthZbTp%2FLiYZgtOocSpNtubcI9BGRsE%3D&reserved=0 I was able to get everything to build on Windows last night, and have the SDK (corefx) built on FreeBSD. The runtime (coreclr) is failing in some sections of the test code. I forwarded my errors but have not gotten back to them yet. I am currently fighting with virtualbox to try and get shared folders working. It looks like I need to rebuild my guest additions from ports. Nothing for free my friend. XD I sincerely would like to help again with the Mono build but finding time will be difficult. I'd like to unburden you from the Mono 5 port so you can play on DNC! As soon as I have confirmed Tomas' build and finish a step in an unrelated project (https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Freviews.freebsd.org%2FD12921&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7Cd776769e3f7f4b1a217208d5273f819f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636458076071078070&sdata=aWUNTWvWHi9CZNi7df%2FWL8JF3u4Msu5hT3TDJsNJNs4%3D&reserved=0), I will get back to your port (unless someone else can step in). Glad to here from you, Russ ___ freebsd-mono@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-mono&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7Cd776769e3f7f4b1a217208d5273f819f%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636458076071078070&sdata=Dz08LJGCyo8kdCT68415TyXk4hmu4Hnj8S%2B%2BLltvzAY%3D&reserved=0 To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org" ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: DotNet Core 2.0 - Status Update
Yes, your assessment seems right David. This is similar to building compiler. You need something to compile it with. C# compiler Roslyn is written in c#. To break the loop, you have set of reference bits – previous version, mono or something else. We will still probably need precompiled assemblies in order to run Roslyn and other tools. I’ve been trying to hack up “previous” version for FreeBSD so at least people can build and start working on fixes. Fact that code builds does not mean it is ready. I can build and run “hello world” but running msbuild kills runtime. Many tests are failing in corefx. (don’t know about coreclr and other repos yet) I think there is long way before we can call it ready for preview. The build from beginning is not specific to FreeBSD. To add to the list: - Build the managed parts on FreeBSD with Linux/OSX/Windows version (theoretical only) There may be more than one answer. It may be handy if previous version exists – for people who want to just hack on single repo and fix a bug. Building everything from scratch can be complicated and tedious. But I think the path should exist and be scriptable. Tomas On 9/27/17, 12:15 PM, "David Naylor" wrote: On Sunday, 24 September 2017 23:36:32 Russell Haley wrote: > Hey, > > *This is my understanding of what's going on and I am looking for > Tomas or Karel to correct or clarify. > > I've continued poking around on the build to little effect so far. > Tomas has said there is an update to the official repository coming > soon that runs for the most part on his 11-release instance. (I'm sure > he will elaborate at some point). > > Progress for Users: > The ability to produce binaries that will allow people to compile and > run applications is still a little ways out but there is a "first > candidate" coming for the curious. > > For "the curious": > There are multiple repositories for DotNet Core but two main "halves" > to any runtime: the native parts and the managed code parts. Right > now, the native pieces build for Tomas. The managed code parts however > require there to be an existing copy of the .Net Framework to build > dotnet core 2.0. Because that doesn't exist on FreeBSD (and never > will), there are currently three solutions: > > - Build the managed parts on Windows > - Build the managed parts on Linux > - Build the managed parts on FreeBSD with mono (theoretical only) > > >From what I understand, this bootstrap conundrum will always exist for > > FreeBSD (except using a prior port to bootstrap the next one?). What I > think needs to happen is we need to create a first version of the port > that imports the managed code from a Windows or Linux repository. This > would become a boot strap port that could be replaced once the DotNet > Core team at Microsoft figure out a more permanent solution. Or not, > and we always have a bootstrap package. :P > > The alternative is to work towards getting the managed parts to build > in Mono and making mono a prerequisite to build. This would be a > FreeBSD only solution, but could get some traction from the Mono team > (now at Microsoft) and would be good for the FreeBSD mono port. We could do what Mono does to bootstrap the managed code (i.e. monolite): 1) Have a machine running a prior version of dotnet (say 2.0) 2) Use existing dotnet (2.0) to compile managed code for new dotnet (say 2.1) 3) Tarball the managed code and make available through FreeBSD's public distfiles infrastructure 4) Update port's version of dotnet native code to new version (2.1) 5) Use the tarball in step (3) to compile managed code in ports for new version (2.1) This is mostly the same as your first suggestion, except we compile the managed code from a prior version for dotnet instead of using a different OS. I would, personally, prefer directly compiling the managed code with mono as a backup (say, if someone wants to bootstrap the process themselves). ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
2.0 bootsrap
I made another step towards getting build working on FreeBSD: https://github.com/wfurt/blob + dotnet new; dotnet restore; dotnet run -> works on FreebSD. - I still have some issue using that dotnet cli for a full build. Running unit tests on FreeBSD still needs some work. Hopefully that should be resolved shortly and outcome from unit test can paint clearer map of the gap. I have few PRs to push my private changes to master. At this point, I’m looking for help with specific issues. For example: GetExePath in corefx/System.Diagnostics.Process I have simple hack using readlink(“/proc/curproc/file”) I think better implantation should not depend on mounted /proc Also, I only fix only one function msbuild was failing on. This may not be interesting for normal apps, but I think it is important for various tools to work properly. I’m also looking for takers for file watchers. There has been some chatter in the past. We may always throw – not-supported-by-platform but somebody may have insight if the landscape improved since last year. Whoever is working on whatever: please tag everything with os-freebsd. That will make it easier for everybody to track what is going on. Tomas ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: DotNet Core on FreeBSD
I have not tried as small, but the native parts do not need much.
The build has option (-numproc) to limit parallelism and that should help if
you run into troubles.
Also, watch for limit on open file descriptors.
Tomas
On 9/20/17, 2:39 PM, "owner-freebsd-m...@freebsd.org on behalf of Carsten
Larsen" wrote:
This all sounds very interesting !
Given the new build instructions on github I will also give it try.
What are the requirements in terms of memory for the build process to
complete? Would a VPS with 512Mb be enough?
Kind regards
Carsten
On 20-09-2017 03:35 Aaron Havens wrote:
> I am going through the Building instructions and updating anything I find.
> Let me know if I add something that should be left out or should do it
> differently.
>
> Aaron
>
> On Mon, Sep 18, 2017 at 10:11 PM, Tomas Weinfurt via freebsd-mono <
> freebsd-mono@freebsd.org> wrote:
>
>> First draft is posted here:
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdotnet%2F&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7Cfe32f86c6e024ee71f6108d500710a0a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636415407870960109&sdata=6UXyqkEidTTQQJI6FqPIvCMRiot29zXFMWyduTn6jV4%3D&reserved=0
>> corefx/wiki/Building-.NET-Core--2.x-on-FreeBSD
>> Probably incomplete.
>> It would be good if anybody can take a look, try and improve.
>> This is essentially equivalent of what has been done for 1.x.
>> My next step is to have cross-OS tests and get them running on FreeBSD
>> host.
>>
>> Tomas
>>
>> On 9/16/17, 9:59 PM, "owner-freebsd-m...@freebsd.org on behalf of Tomas
>> Weinfurt via freebsd-mono" > freebsd-mono@freebsd.org> wrote:
>>
>> I’ll get WIKI started with instructions on github. I just did not
get
>> to it yet.
>> At least the runtime can be built without windows now. (using Linux
>> instead)
>> I still have some work left to cross-target for FreeBSD on Linux so
>> one can build proper managed assemblies.
>> Attempts to use Linux binaries for bootstrap failed so far because
>> Linux emulation is lacking mincore() support.
>>
>> Tomas
>>
>>
>> On 9/16/17, 9:40 PM, "owner-freebsd-m...@freebsd.org on behalf of
>> Russell Haley" > russ.ha...@gmail.com> wrote:
>>
>> Hey Guys,
>>
>> Tomas has shared a binary with me and warned it's pretty rough.
I'm
>> not getting very far with it. I'll share the same link if
someone
>> is
>> interested but it's probably best to wait until Tomas offers
>> something
>> more functional and some instructions.
>>
>> Is it possible for someone to start a FreeBSD wiki page for
DotNet
>> Core? Tomas and Karel want to keep the progress tracked via
their
>> tools (Github accounts etc), but I think a wiki page would be
good
>> for status updates and the like?
>>
>> Russ
>>
>>
>> On Fri, Sep 15, 2017 at 8:46 PM, Robert Alegrid <
>> eraleg...@hotmail.com> wrote:
>> > On Thursday, 14 September 2017 4:24 PM, Russell Haley wrote:
>> >> If you'd like to participate/join the fun, please set up a
>> GitHub account and
>> >> send a 'me too' email with the username or email address.
>> >> I'll send an invite for the FreeBSD-DotNet to that account.
I'm
>> not so sure
>> >> anymore about using GitHub for FreeBSD stuff, but it's a good
>> place to
>> >> congregate.
>> > I'd like to pitch in. Never participated in an open-source
>> project before so I
>> > don't know how much help I could be.
>> >
>> > E-mail is the same as this message (eraleg...@hotmail.com)
>> > GH Account is
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.safelinks&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7Cfe32f86c6e024ee71f6108d500710a0a%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636415407870960109&sdata=SjJjylJEmh59rdcN9e%2BHeO8PibDKj9v0sxm%2FTNbHY3g%3D&reserved=0.
>> protection.outlook.com/?url=https%3A%2F%2Fgithub.com%
>> 2FEcho-8-ERA
Re: DotNet Core Source Build Questions
It is fixed in my branch. I updated docs to use ./src/Native/build-native.sh directly. That should avoid problems with getting tools. Tomas On 9/19/17, 10:18 PM, "owner-freebsd-m...@freebsd.org on behalf of Russell Haley" wrote: On Tue, Sep 19, 2017 at 10:11 PM, Tomas Weinfurt wrote: > I’ll take a look. Once you on path where it tries to install Tools it is bad. > Please try src/Native/build-native.sh directly. Okay, that started things in the right direction: russellh@prescott:/storage/russellh/Git/corefx/src/Native% ./build-native.sh Setting up directories for build WARNING: Can not determine runtime id for current distro. Checking pre-requisites... Commencing build of corefx native components for FreeBSD.x64.Debug Invoking cmake with arguments: "/storage/russellh/Git/corefx/src/Native/Unix" DEBUG -DFEATURE_DISTRO_AGNOSTIC_SSL=0 -DCMAKE_STATIC_LIB_LINK=0 -- The C compiler identification is Clang 4.0.0 -- The CXX compiler identification is Clang 4.0.0 -- Check for working C compiler: /usr/bin/clang -- Check for working C compiler: /usr/bin/clang -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/clang++ -- Check for working CXX compiler: /usr/bin/clang++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done -- Looking for include file linux/in.h -- Looking for include file linux/in.h - not found -- Performing Test HAVE_IN_PKTINFO -- Performing Test HAVE_IN_PKTINFO - Success -- Performing Test HAVE_IP_MREQN -- Performing Test HAVE_IP_MREQN - Success -- Performing Test HAVE_FLOCK64 -- Performing Test HAVE_FLOCK64 - Failed -- Looking for lseek64 -- Looking for lseek64 - not found -- Looking for mmap64 -- Looking for mmap64 - not found -- Looking for ftruncate64 -- Looking for ftruncate64 - not found -- Looking for posix_fadvise64 -- Looking for posix_fadvise64 - not found -- Looking for stat64 -- Looking for stat64 - not found -- Looking for pipe2 -- Looking for pipe2 - found -- Looking for getmntinfo -- Looking for getmntinfo - found -- Looking for strcpy_s -- Looking for strcpy_s - not found -- Looking for strlcpy -- Looking for strlcpy - found -- Looking for posix_fadvise -- Looking for posix_fadvise - found -- Looking for ioctl -- Looking for ioctl - found -- Looking for sched_getaffinity -- Looking for sched_getaffinity - not found -- Looking for sched_setaffinity -- Looking for sched_setaffinity - not found -- Looking for TIOCGWINSZ -- Looking for TIOCGWINSZ - found -- Looking for tcgetattr -- Looking for tcgetattr - found -- Looking for tcsetattr -- Looking for tcsetattr - found -- Looking for ECHO -- Looking for ECHO - found -- Looking for ICANON -- Looking for ICANON - found -- Looking for TCSANOW -- Looking for TCSANOW - found -- Performing Test HAVE_STAT_BIRTHTIME -- Performing Test HAVE_STAT_BIRTHTIME - Success -- Performing Test HAVE_DIRENT_NAME_LEN -- Performing Test HAVE_DIRENT_NAME_LEN - Success -- Performing Test HAVE_STATFS_FSTYPENAME -- Performing Test HAVE_STATFS_FSTYPENAME - Success -- Performing Test HAVE_STATVFS_FSTYPENAME -- Performing Test HAVE_STATVFS_FSTYPENAME - Failed -- Check size of struct statfs -- Check size of struct statfs - done -- Performing Test HAVE_GNU_STRERROR_R -- Performing Test HAVE_GNU_STRERROR_R - Failed -- Performing Test HAVE_READDIR_R -- Performing Test HAVE_READDIR_R - Success -- Performing Test KEVENT_HAS_VOID_UDATA -- Performing Test KEVENT_HAS_VOID_UDATA - Success -- Performing Test HAVE_FDS_BITS -- Performing Test HAVE_FDS_BITS - Success -- Performing Test HAVE_PRIVATE_FDS_BITS -- Performing Test HAVE_PRIVATE_FDS_BITS - Success -- Performing Test HAVE_SENDFILE_4 -- Performing Test HAVE_SENDFILE_4 - Failed -- Performing Test HAVE_SENDFILE_6 -- Performing Test HAVE_SENDFILE_6 - Failed -- Looking for fcopyfile -- Looking for fcopyfile - not found -- Looking for epoll_create1 -- Looking for epoll_create1 - not found -- Looking for accept4 -- Looking for accept4 - found -- Looking for kqueue -- Looking for kqueue - found -- Performing Test HAVE_GETHOSTBYADDR_R -- Performing Test HAVE_GETHOSTBYADDR_R - Success -- Performing Test HAVE_GETHOSTBYNAME_R -- Performing Test HAVE_GETHOSTBYNAME_R - Success -- Performing Test HAVE_GETNAMEINFO_SIGNED_FLAGS -- Performing Test HAVE_GETNAMEINFO_SIGNED_FLAGS - Success -- Performing Test HAVE_CLOCK_MONOTONIC --
Re: DotNet Core Source Build Questions
I’ll take a look. Once you on path where it tries to install Tools it is bad. Please try src/Native/build-native.sh directly. Tomas On 9/19/17, 10:07 PM, "Russell Haley" wrote: Hey Tomas, coreclr native parts built first time for me. I am trying to build the dotnet fx native parts and I'm still stalled out on Linux emulation errors. I have a question in the TrueOS forums and will poke around: https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdiscourse.trueos.org%2Ft%2Fexecuting-64-bit-linux-binaries%2F703%2F2&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694&sdata=us2YL%2F%2BjZg2xtSCtzDCrhRwGH3EqoTwPK8MWcazmNEo%3D&reserved=0 Here is my build output: russellh@prescott:/storage/russellh/Git/corefx% ./build.sh native -clang=clang3.9 Unsupported OS 'FreeBSD' detected. Downloading linux-x64 tools. Installing dotnet cli... Restoring BuildTools version 2.0.0-prerelease-01931-01... ELF interpreter /lib64/ld-linux-x86-64.so.2 not found, error 2 /storage/russellh/Git/corefx/init-tools.sh: line 142: 39789 Abort trap $__DOTNET_CMD restore "$__INIT_TOOLS_RESTORE_PROJECT" --no-cache --packages $__PACKAGES_DIR --source $__BUILDTOOLS_SOURCE /p:BuildToolsPackageVersion=$__BUILD_TOOLS_PACKAGE_VERSION >> $__init_tools_log ERROR: Could not restore build tools correctly. Please check the detailed log that follows. Running: /storage/russellh/Git/corefx/init-tools.sh Installing 'https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdotnetcli.azureedge.net%2Fdotnet%2FSdk%2F2.0.0-preview1-005977%2Fdotnet-dev-linux-x64.2.0.0-preview1-005977.tar.gz&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694&sdata=nmUCgZjM2kCcFAeFciTqw0mXOOAUO0qaIrJD0ODTSGM%3D&reserved=0' to '/storage/russellh/Git/corefx/Tools/dotnetcli/dotnet.tar' Running: /storage/russellh/Git/corefx/Tools/dotnetcli/dotnet restore "/storage/russellh/Git/corefx/init-tools.msbuild" --no-cache --packages /storage/russellh/Git/corefx/packages --source https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdotnet.myget.org%2FF%2Fdotnet-buildtools%2Fapi%2Fv3%2Findex.json&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694&sdata=uIeCnyr%2FTLSr%2FphUMAPJJ0AF3iKxzBMHD6YpOYBRSTw%3D&reserved=0 /p:BuildToolsPackageVersion=2.0.0-prerelease-01931-01 Initializing BuildTools... chmod: /storage/russellh/Git/corefx/packages/microsoft.dotnet.buildtools/2.0.0-prerelease-01931-01/lib/init-tools.sh: No such file or directory /storage/russellh/Git/corefx/init-tools.sh: line 121: /storage/russellh/Git/corefx/packages/microsoft.dotnet.buildtools/2.0.0-prerelease-01931-01/lib/init-tools.sh: No such file or directory ERROR: An error occurred when trying to initialize the tools. Please check the detailed log that follows. Running: /storage/russellh/Git/corefx/init-tools.sh Installing 'https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdotnetcli.azureedge.net%2Fdotnet%2FSdk%2F2.0.0-preview1-005977%2Fdotnet-dev-linux-x64.2.0.0-preview1-005977.tar.gz&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694&sdata=nmUCgZjM2kCcFAeFciTqw0mXOOAUO0qaIrJD0ODTSGM%3D&reserved=0' to '/storage/russellh/Git/corefx/Tools/dotnetcli/dotnet.tar' Running: /storage/russellh/Git/corefx/Tools/dotnetcli/dotnet restore "/storage/russellh/Git/corefx/init-tools.msbuild" --no-cache --packages /storage/russellh/Git/corefx/packages --source https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdotnet.myget.org%2FF%2Fdotnet-buildtools%2Fapi%2Fv3%2Findex.json&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694&sdata=uIeCnyr%2FTLSr%2FphUMAPJJ0AF3iKxzBMHD6YpOYBRSTw%3D&reserved=0 /p:BuildToolsPackageVersion=2.0.0-prerelease-01931-01 Running: /storage/russellh/Git/corefx/packages/microsoft.dotnet.buildtools/2.0.0-prerelease-01931-01/lib/init-tools.sh /storage/russellh/Git/corefx /storage/russellh/Git/corefx/Tools/dotnetcli/dotnet /storage/russellh/Git/corefx/Tools russellh@prescott:/storage/russellh/Git/corefx% I tried building the mscorelib in monodevelop (and also tried xbuild) but got the following error: Error: /storage/russellh/Git/coreclr/src/mscorlib/System.Private.CoreLib.csproj: /storage/russellh/Git/coreclr/dir.targets: Project file could not be imported, it was being imported by /storage/russellh/Git/coreclr/src/mscorlib/System.Private.CoreLib
Re: DotNet Core on FreeBSD
>Sweet! I love the "Thar be Dragons!" warning. :) Daemons & Dragons! (https://en.wikipedia.org/wiki/BSD_Daemon) I resisted urge to put there note on cake eaters. > This also links to the original core 1.x FreeBSD build guide. I lost >this one a while back and could never find it. :( There is another great link here: https://github.com/dotnet/corefx/issues/1626 way down there is checklist of missing parts. We should try to reconstruct it for 2.0. For example, Filesystem.watchers is still missing. The API surface increased quite a bit in 2.0 – so as the gap. My current thinking is to fork the build to add FreeBSD flavor and throw “PlatformNotSupported” and then finding somebody to work on implementation. >Tomas, from reading through your instructions, there seems to be two > obstacles and they are both managed code? > - corelib - dotnet/coreclr/src/mscorelib seems to be the corelib you >are talking about? > - corefx - managed code > >If that's true, then we should definitely give mono a shot at bringing > those up. I'm downloading the dotnet/coreclr now. And yes, that is mscorelib. I did ask around and Mono used to be supported for building. It was claimed unstable and removed from build. You will need to get compilation as well as msbuild working right. For now, I’m going to ignore building part, and I’ll focus on getting coreCLR & coreFX working well. On the side, I’ll try to shepherd changes to cli & msbuild so they can properly recognize FreeBSD as a platform. Tomas ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: DotNet Core on FreeBSD
First draft is posted here: https://github.com/dotnet/corefx/wiki/Building-.NET-Core--2.x-on-FreeBSD Probably incomplete. It would be good if anybody can take a look, try and improve. This is essentially equivalent of what has been done for 1.x. My next step is to have cross-OS tests and get them running on FreeBSD host. Tomas On 9/16/17, 9:59 PM, "owner-freebsd-m...@freebsd.org on behalf of Tomas Weinfurt via freebsd-mono" wrote: I’ll get WIKI started with instructions on github. I just did not get to it yet. At least the runtime can be built without windows now. (using Linux instead) I still have some work left to cross-target for FreeBSD on Linux so one can build proper managed assemblies. Attempts to use Linux binaries for bootstrap failed so far because Linux emulation is lacking mincore() support. Tomas On 9/16/17, 9:40 PM, "owner-freebsd-m...@freebsd.org on behalf of Russell Haley" wrote: Hey Guys, Tomas has shared a binary with me and warned it's pretty rough. I'm not getting very far with it. I'll share the same link if someone is interested but it's probably best to wait until Tomas offers something more functional and some instructions. Is it possible for someone to start a FreeBSD wiki page for DotNet Core? Tomas and Karel want to keep the progress tracked via their tools (Github accounts etc), but I think a wiki page would be good for status updates and the like? Russ On Fri, Sep 15, 2017 at 8:46 PM, Robert Alegrid wrote: > On Thursday, 14 September 2017 4:24 PM, Russell Haley wrote: >> If you'd like to participate/join the fun, please set up a GitHub account and >> send a 'me too' email with the username or email address. >> I'll send an invite for the FreeBSD-DotNet to that account. I'm not so sure >> anymore about using GitHub for FreeBSD stuff, but it's a good place to >> congregate. > I'd like to pitch in. Never participated in an open-source project before so I > don't know how much help I could be. > > E-mail is the same as this message (eraleg...@hotmail.com) > GH Account is https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FEcho-8-ERA&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636412200126651288&sdata=WqH7%2BN%2BatYCU4BYs5409sZMMHWJPILJnLjGm7m7v988%3D&reserved=0 > > Regards, > Robert Alegrid ___ freebsd-mono@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-mono&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636412200126651288&sdata=kNqxYsg0HzoF3f3HqGsp3dm1NKsNax9W3lWuntDt7kE%3D&reserved=0 To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org" ___ freebsd-mono@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-mono&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C5364f3a7997f4f5b328708d4fd88f28e%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636412212015989639&sdata=WuwkCpreZpGlwnMGKWQ6kdxBGYKxQAyHrx6IV9MbgKA%3D&reserved=0 To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org" ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: DotNet Core on FreeBSD
I’ll get WIKI started with instructions on github. I just did not get to it yet. At least the runtime can be built without windows now. (using Linux instead) I still have some work left to cross-target for FreeBSD on Linux so one can build proper managed assemblies. Attempts to use Linux binaries for bootstrap failed so far because Linux emulation is lacking mincore() support. Tomas On 9/16/17, 9:40 PM, "owner-freebsd-m...@freebsd.org on behalf of Russell Haley" wrote: Hey Guys, Tomas has shared a binary with me and warned it's pretty rough. I'm not getting very far with it. I'll share the same link if someone is interested but it's probably best to wait until Tomas offers something more functional and some instructions. Is it possible for someone to start a FreeBSD wiki page for DotNet Core? Tomas and Karel want to keep the progress tracked via their tools (Github accounts etc), but I think a wiki page would be good for status updates and the like? Russ On Fri, Sep 15, 2017 at 8:46 PM, Robert Alegrid wrote: > On Thursday, 14 September 2017 4:24 PM, Russell Haley wrote: >> If you'd like to participate/join the fun, please set up a GitHub account and >> send a 'me too' email with the username or email address. >> I'll send an invite for the FreeBSD-DotNet to that account. I'm not so sure >> anymore about using GitHub for FreeBSD stuff, but it's a good place to >> congregate. > I'd like to pitch in. Never participated in an open-source project before so I > don't know how much help I could be. > > E-mail is the same as this message (eraleg...@hotmail.com) > GH Account is https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FEcho-8-ERA&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636412200126651288&sdata=WqH7%2BN%2BatYCU4BYs5409sZMMHWJPILJnLjGm7m7v988%3D&reserved=0 > > Regards, > Robert Alegrid ___ freebsd-mono@freebsd.org mailing list https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.freebsd.org%2Fmailman%2Flistinfo%2Ffreebsd-mono&data=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636412200126651288&sdata=kNqxYsg0HzoF3f3HqGsp3dm1NKsNax9W3lWuntDt7kE%3D&reserved=0 To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org" ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
Re: DotNet Core on FreeBSD
The .NET Core does not have UI. The intention is to provide platform for tools and server apps. 2.0 added quite a bit API surface. ReadHat now has package for their systems. That may bring attention of some *NIX folks. Tomas On 9/14/17, 12:21 AM, "Romain Tartière" wrote: Hi all, On Thu, Sep 14, 2017 at 09:05:08AM +0200, Mathieu Prevot wrote: > I'm in. Can't engage formally as I'm quite loaded with work, but I'm rather > familiar with the .NET ecosystem. My knowledge of .NET is really limited, but maybe I could help with problems related to FreeBSD, so please count me in ;-) I am @smortex on GitHub. Regards, Romain -- Romain Tartière http://people.FreeBSD.org/~romain/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =non-HTML= PGP/GPG encrypted/signed e-mail much appreciated) ___ freebsd-mono@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-mono To unsubscribe, send any mail to "freebsd-mono-unsubscr...@freebsd.org"
