Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

can't build on a mac

See original GitHub issue

Steps to reproduce

be on a mac, in a new folder run

dotnet new classlib
dotnet restore
dotnet build

Expected behavior

it to work

Actual behavior

Microsoft (R) Build Engine version 15.1.548.43366
Copyright (C) Microsoft Corporation. All rights reserved.

/usr/local/share/dotnet/sdk/1.0.1/Roslyn/Microsoft.CSharp.Core.targets(71,5): error MSB6006: "/usr/local/share/dotnet/sdk/1.0.1/Roslyn/RunCsc.sh" exited with code 134. [/Users/me/projects/myproject/myproject.csproj]

Build FAILED.

/usr/local/share/dotnet/sdk/1.0.1/Roslyn/Microsoft.CSharp.Core.targets(71,5): error MSB6006: "/usr/local/share/dotnet/sdk/1.0.1/Roslyn/RunCsc.sh" exited with code 134. [/Users/my/projects/myproject/myproject.csproj]
    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:01.48

Environment data

dotnet --info output:

.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.1

cc @knownasilya and @guidos who are also having this problem

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

dasMullicommented, Apr 12, 2017

On Mac /usr/bin/bash wouldn’t work, it had to be /bin/bash (at least on my 10.12.4). IIRC, some linux distros do ship bash in /usr/bin (but usually have a symlink in /bin). This is one of the reasons using env to resolve bash is considered more portable as it determines which one the environment prefers based on the $PATH. See http://stackoverflow.com/questions/21612980/why-is-usr-bin-env-bash-superior-to-bin-bash

In this case, an installation of bash was registered to replace the system bash so I’d expect all scripts to follow that. It only doesn’t work because this installation has become broken. I don’t think any effort should be made to work around broken installations that trade off portability.

0reactions

calvinmetcalfcommented, Apr 14, 2017

Ok that’s fine, the only thing is just that as it turns out, my #!/usr/bin/env bash has been broken for a long time time and I run a lot of bash scripts and this his the first one where it came up so I don’t know how common it actually is in practice