Re: DotNet Core on FreeBSD

2017-09-19 Thread Aaron Havens
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://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"  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%2Fgithub.com%
> 2FEcho-8-ERA=02%7C01%7CTomas.Weinfurt%40microsoft.com%
> 7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636412200126651288=WqH7%2BN%
> 2BatYCU4BYs5409sZMMHWJPILJnLjGm7m7v988%3D=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=02%7C01%7CTomas.Weinfurt%40microsoft.com%
> 7C24a4afb4b47f4a7a1d5208d4fd862dab%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636412200126651288=kNqxYsg0HzoF3f3HqGsp3dm1NKsNax
> 9W3lWuntDt7kE%3D=0
> To unsubscribe, send any mail to "freebsd-mono-unsubscribe@
> 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=02%7C01%7CTomas.Weinfurt%40microsoft.com%
> 7C5364f3a7997f4f5b328708d4fd88f28e%7C72f988bf86f141af91ab2d7cd011
> db47%7C1%7C0%7C636412212015989639=WuwkCpreZpGlwnMGKWQ6kdxBGYKxQA
> yHrx6IV9MbgKA%3D=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"
>
___
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"

Funny

2017-09-19 Thread Russell Haley

___
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 Source Build Questions

2017-09-19 Thread Tomas Weinfurt via freebsd-mono
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=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694=us2YL%2F%2BjZg2xtSCtzDCrhRwGH3EqoTwPK8MWcazmNEo%3D=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=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694=nmUCgZjM2kCcFAeFciTqw0mXOOAUO0qaIrJD0ODTSGM%3D=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=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694=uIeCnyr%2FTLSr%2FphUMAPJJ0AF3iKxzBMHD6YpOYBRSTw%3D=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=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694=nmUCgZjM2kCcFAeFciTqw0mXOOAUO0qaIrJD0ODTSGM%3D=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=02%7C01%7CTomas.Weinfurt%40microsoft.com%7C3b720d481d9b4e70aceb08d4ffe57ac2%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636414808455309694=uIeCnyr%2FTLSr%2FphUMAPJJ0AF3iKxzBMHD6YpOYBRSTw%3D=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.csproj:
/storage/russellh/Git/coreclr/dir.targets could not import

Re: DotNet Core Source Build Questions

2017-09-19 Thread Russell Haley
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
-- Performing Test HAVE_CLOCK_MONOTONIC - Success
-- Performing Test HAVE_CLOCK_REALTIME
-- Performing Test HAVE_CLOCK_REALTIME - Success
-- Looking for mach_absolute_time
-- Looking for mach_absolute_time - not found
-- Looking for mach_timebase_info
-- Looking for mach_timebase_info - not found
-- Looking for futimes
-- Looking for futimes - found
-- Looking for futimens
-- Looking for futimens - found
-- Performing Test BIND_ADDRLEN_UNSIGNED
-- Performing Test BIND_ADDRLEN_UNSIGNED - Success
-- Performing Test IPV6MR_INTERFACE_UNSIGNED
-- Performing Test IPV6MR_INTERFACE_UNSIGNED - Success
-- Performing Test INOTIFY_RM_WATCH_WD_UNSIGNED
-- Performing Test 

Re: DotNet Core Source Build Questions

2017-09-19 Thread Russell Haley
Comment inline.

On Tue, Sep 19, 2017 at 10:18 PM, 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
#Here is the problem. The pal_networking.cpp file has a definition for
in_pktinfo. It didn't get hit because the following test succeeded and
it should have failed:

> -- 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
> -- Performing Test HAVE_CLOCK_MONOTONIC - Success
> -- Performing Test HAVE_CLOCK_REALTIME
> -- Performing Test HAVE_CLOCK_REALTIME - Success
> -- Looking for mach_absolute_time
> -- 

DotNet Core Source Build Questions

2017-09-19 Thread Russell Haley
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://discourse.trueos.org/t/executing-64-bit-linux-binaries/703/2

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://dotnetcli.azureedge.net/dotnet/Sdk/2.0.0-preview1-005977/dotnet-dev-linux-x64.2.0.0-preview1-005977.tar.gz'
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://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
/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://dotnetcli.azureedge.net/dotnet/Sdk/2.0.0-preview1-005977/dotnet-dev-linux-x64.2.0.0-preview1-005977.tar.gz'
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://dotnet.myget.org/F/dotnet-buildtools/api/v3/index.json
/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.csproj:
/storage/russellh/Git/coreclr/dir.targets could not import
"$(ToolsDir)/Build.Common.targets" (System.Private.CoreLib)x

A quick search showed something about wrong framework version. I
wonder if I should ping off the Xamarina/Mono team?

Russ
___
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"