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
Error installing dotnet core on AWS Linux using dotnet.bootstrap.py #800
Comments
Can you try with this patch: https://gist.github.com/omajid/90ebbd58cc54473d2a295c261451c166 ? |
Thanks. That fixed the original error. But now I get the following: ERROR LOG START******* CMake Error at /usr/share/cmake/Modules/CMakeTestCCompiler.cmake:61 (message): It fails with the following output: Change Dir: /home/ec2-user/dotnet/amzn.2017.03-x64-dotnet/src/coreclr/bin/obj/Linux.x64.Release/CMakeFiles/CMakeTmp Run Build Command:/usr/bin/gmake "cmTryCompileExec1621937052/fast" /usr/bin/gmake -f CMakeFiles/cmTryCompileExec1621937052.dir/build.make gmake[1]: Entering directory /usr/bin/cmake -E cmake_progress_report Building C object /usr/bin/clang -Wall -std=c11 -o Linking C executable cmTryCompileExec1621937052 /usr/bin/cmake -E cmake_link_script /usr/bin/clang -Wall -std=c11 /usr/bin/ld: cannot find crt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory /usr/bin/ld: cannot find crtbegin.o: No such file or directory /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s /usr/bin/ld: cannot find -lc /usr/bin/ld: cannot find -lgcc /usr/bin/ld: cannot find -lgcc_s /usr/bin/ld: cannot find crtend.o: No such file or directory /usr/bin/ld: cannot find crtn.o: No such file or directory clang: error: linker command failed with exit code 1 (use -v to see gmake[1]: Leaving directory gmake[1]: *** [cmTryCompileExec1621937052] Error 1 gmake: *** [cmTryCompileExec1621937052/fast] Error 2 -- Configuring incomplete, errors occurred! Here is the clang version on that instance: clang.x86_64 0:3.6.2-1.12.amzn1 Thanks, |
We're trying to move away from dotnet.bootstrap.py and it's note really maintained anymore. The preferred approach is https://github.com/dotnet/source-build. Can you give that a try and see if it works for you? |
Please file an issue @ https://github.com/dotnet/source-build if it doesn't work for your case. We're deprecating dotnet.bootstrap.py. See: #1063 |
General
When trying to install: https://github.com/dotnet/core/blob/master/tools/dotnet-bootstrap/dotnet.bootstrap.py on AWS Linux instance with OS: Amazon Linux AMI release 2017.03 (AMI ID: amzn-ami-hvm-2017.03.1.20170623-x86_64-gp2 (ami-327f5352)), I am getting the following:
** ROVER FORCED SETTINGS CHANGE: DEV MODE 'ON'
** ROVER will skip all git commands.
** ROVER requires the deletion of the directory '/home/ec2-user/dotnet_setup/amzn.2017.03-x64-dotnet' to reset the dev-mode trigger.
** ROVER Building: ['coreclr', 'corefx', 'core-setup', 'libuv']
** ROVER Patching? True
** ROVER Staging in amzn.2017.03-x64-dotnet
** ROVER RID: amzn.2017.03-x64
** ROVER CAUGHT AN UNEXPECTED EXCEPTION: "SemanticVersion instance has no attribute 'find'" of type: <type 'exceptions.AttributeError'>
File "./dotnet.bootstrap.py", line 545, in
SpawnPatchTarget(RoverSettings._binDirectory, RoverSettings.PayloadPath)
File "./dotnet.bootstrap.py", line 342, in SpawnPatchTarget
RoverSettings.SetPatchTargetPath(path.join(RoverSettings._ScriptDirectory, destination_folder))
File "./dotnet.bootstrap.py", line 261, in SetPatchTargetPath
RoverSettings.PatchTarget_Shared = path.join(shared_containerFolder, RoverSettings.SelectGreatestPrecendenceDirectory(shared_containerFolder))
File "./dotnet.bootstrap.py", line 248, in SelectGreatestPrecendenceDirectory
maxVersion = RoverSettings.MaxPrecedence(dirName, maxVersion)
File "./dotnet.bootstrap.py", line 234, in MaxPrecedence
versionB = SemanticVersion(versionStrB)
File "./dotnet.bootstrap.py", line 156, in init
self.VersionTuple = self.GetVersionTuple(versionStr)
File "./dotnet.bootstrap.py", line 141, in GetVersionTuple
middleIndex = versionStr.find('-')
** ROVER None
The text was updated successfully, but these errors were encountered: