-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dev-dotnet/buildtools-1.0.27-r1 build failed #378
Comments
see also dotnet/sdk#987 (comment) differences i found in logs:
|
It's look like mono only search gac for /usr/lib but Newtonsoft.Json install in /usr/lib64 (profile 17.1?)
help me compile buildtools |
I've had to do the same for System.Collections.Immutable after linking for Newtonsoft.Json, and I'm getting new errors (posting here in case it's related, otherwise I can open a new issue): lots of these:
and
this is now coming from and a few others. Does anyone have an idea what I'm doing wrong? |
You making a mistake of assuming that someone else should do the world better for you. Dotnet in gentoo is not working, and will not be in the near future (2019-2020). Because no one dedicate himself to resolve all problems. Debian is in much better position, because it have more people in team. |
That may or may not be the case, but, speaking from a position of having chosen Ubuntu on my work machine (dual-boot) because I expected .net support to be better: the only thing that's better is msbuild (and there's a nice script in /usr/bin for easy invocation). Ubuntu takes away my freedoms. Gentoo does not. I used Debian or a derivative (Ubuntu, Linux Mint) for over 16 years before switching to Gentoo because those distros force me to use systemd and pulseaudio, two over-complex, fragile systems which, if I don't need them, I don't want on my system. I had to use PA for bluetooth headphones on my laptop when I initially installed Gentoo there, but that's just because I couldn't get the alternative to work, and at least it was a choice I could make based on my environment and requirements, not a choice made for me. I don't think it's a mistake to think that someone else would do a better job than me; however, I'm starting to think that I should learn a lot more, step up and try to help, instead of just asking questions. |
for this particular bug, i propose to check your profile. Probably it is 17.1 (see #398 ). In this version of profile the directories layout was changed and mono became more broken than before. |
For anyone who is interested, I had to make the following symlinks:
I'm not sure if some of these have to be made "along the way" as the errors were coming out of three packages originally:
(dev-util/msbuild brought in the first two afaik) In addition, the patch mentioned at #426 is also required. I've bundled the above symlinks and patch creation into a shell script (gentoo-msbuild-helper.txt)
As far as I can tell, the links should be for libraries which are already installed, so this script should work well after the first failed attempt to install One of the links (Microsoft.Build/15.3.0.0__0738eb9f132ed756) is not required to build, but is required at runtime when invoking @ArsenShnurkov I agree that the source of much of this (barring the patch) is probably due to the new lib layout in profile 17.1, so
(updated with safer helper script: I realise that the destination dirs may exist once this is fixed upstream, so |
Thanks, that worked and saved me some time, was building a script to do just that when found yours, thanks a ton! |
I'm a new user trying to install msbuild and I encountered this same error (among the others). @Riey's solution got me past this error, but why is this issue closed if it's still happening? Edit: I actually needed all of the symlinks than @fluffynuts posted, and the patch. So none of this is actually fixed. |
I'm also still getting this error. Using the solution from @Riey got it to build. EDIT: I also had to do @fluffynuts solution to get msbuild to merge. |
issue still continues. and now neither of the solutions work |
buildlog.zip
The text was updated successfully, but these errors were encountered: