Describe the bug
upgrading from 0.2.15 to 0.3.2 got this error
To Reproduce
Steps to reproduce the behavior:
cd RTL
sudo su
git reset —hard HEAD
git clean -f -d
git pull
npm install
RTL upgraded and is accessible via webpage
however install ended up with errors below
should i just ignore it?
Expected behavior
ok, no errors
Actual behavior
Building: /usr/bin/node /home/admin/RTL/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= gyp info it worked if it ends with ok gyp verb cli [ '/usr/bin/node', gyp verb cli '/home/admin/RTL/node_modules/node-gyp/bin/node-gyp.js', gyp verb cli 'rebuild', gyp verb cli '--verbose', gyp verb cli '--libsass_ext=', gyp verb cli '--libsass_cflags=', gyp verb cli '--libsass_ldflags=', gyp verb cli '--libsass_library=' ] gyp info using node-gyp@3.8.0 gyp info using node@11.15.0 | linux | arm gyp verb command rebuild [] gyp verb command clean [] gyp verb clean removing "build" directory gyp verb command configure [] gyp verb check python checking for Python executable "python2" in the PATH gyp verb whichsucceeded python2 /usr/bin/python2 gyp verb check python version/usr/bin/python2 -c «import sys; print «2.7.13
gyp verb check python version .%s.%s» % sys.version_info[:3];»` returned: %j
gyp verb get node dir no —target version specified, falling back to host node version: 11.15.0
gyp verb command install [ ‘11.15.0’ ]
gyp verb install input version string «11.15.0»
gyp verb install installing version: 11.15.0
gyp verb install —ensure was passed, so won’t reinstall if already installed
gyp WARN EACCES user «root» does not have permission to access the dev dir «/root/.node-gyp/11.15.0»
gyp WARN EACCES attempting to reinstall using temporary dev dir «/home/admin/RTL/node_modules/node-sass/.node-gyp»
gyp verb tmpdir == cwd automatically will remove dev files after to save disk space
gyp verb command install [ ‘—node_gyp_internal_noretry’, ‘11.15.0’ ]
gyp verb install input version string «11.15.0»
gyp verb install installing version: 11.15.0
gyp verb install —ensure was passed, so won’t reinstall if already installed
gyp verb install version not already installed, continuing with install 11.15.0
gyp verb ensuring nodedir is created /home/admin/RTL/node_modules/node-sass/.node-gyp/11.15.0
gyp WARN install got an error, rolling back install
gyp verb command remove [ ‘11.15.0’ ]
gyp verb remove using node-gyp dir: /home/admin/RTL/node_modules/node-sass/.node-gyp
gyp verb remove removing target version: 11.15.0
gyp verb remove removing development files for version: 11.15.0
gyp WARN install got an error, rolling back install
gyp verb command remove [ ‘11.15.0’ ]
gyp verb remove using node-gyp dir: /home/admin/RTL/node_modules/node-sass/.node-gyp
gyp verb remove removing target version: 11.15.0
gyp verb remove removing development files for version: 11.15.0
gyp ERR! configure error
gyp ERR! stack Error: EACCES: permission denied, mkdir ‘/home/admin/RTL/node_modules/node-sass/.node-gyp’
gyp ERR! System Linux 4.14.98-v7+
gyp ERR! command «/usr/bin/node» «/home/admin/RTL/node_modules/node-gyp/bin/node-gyp.js» «rebuild» «—verbose» «—libsass_ext=» «—libsass_cflags=» «—libsass_ldflags=» «—libsass_library=»
gyp ERR! cwd /home/admin/RTL/node_modules/node-sass
gyp ERR! node -v v11.15.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN angular-user-idle@2.0.0 requires a peer of @angular/common@^6.0.0-rc.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN angular-user-idle@2.0.0 requires a peer of @angular/core@^6.0.0-rc.0 || ^6.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN codelyzer@4.3.0 requires a peer of @angular/compiler@>=2.3.1 <7.0.0 || >6.0.0-beta <7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN codelyzer@4.3.0 requires a peer of @angular/core@>=2.3.1 <7.0.0 || >6.0.0-beta <7.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»linux»,»arch»:»arm»})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.12.0 postinstall: node scripts/build.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.12.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-05-13T18_11_26_044Z-debug.log`
Screenshots
If applicable, add screenshots to help explain your problem.
Your environment
Raspiblitz 1.1 on rpi 3b+
lnd 0.6.0
bitcoin 0.17.0
Additional context
Add any other context about the problem here.
The “error command gcc failed with exit status 1” error is a very common error that is mainly related to the GCC compilation and required libraries. This error text is longer than this. The remaining part expresses the specific application name or libraries. In this tutorial, we examine how to find the error cause and solve it by installing required libraries or packages. Also, we provide some common solutions which can solve the problem in most cases.
As stated previously the error is mainly related when we try to install 3rd party library generally related with Python the compilation process starts. The gcc is used for compilation and the compilation process requires some development libraries. If these development libraries are not installed or not found the gcc returns error. Error looks like below.
Running greenlet-0.3.4/setup.py -q bdist_egg --dist-dir /tmp/easy_install-_httHYm/greuulet-0.3.4/egg-dist-tmp-t9_gbW In file included from greenlet.c:5:0: greenlet.h:9:20: fatal error: Python.h: No such file or directory compilation terminated. error: Setup script exited with error: command 'gcc' failed with exit status 1`
The error cause is located in the 4th line. The “fatal error: Python.h: No such file or directory” expression explain what is the cause. It simply says that the Python development library or packages are not install or found.
Install Up-to-Date GCC
The GCC is used to compile given source code. If he GCC is not uptodate or even not installed the compilation ends with error. So first step is updating or installing the GCC.
Ubuntu, Debian, Mint, Kali:
sudo apt update gccCentOS, RHEL, Fedora:
sudo dnf update gccMacOSX:
brew install gccInstall Build Essentials
The build essentials are libraries and packages used to build source code. They are essential to build most of the packages. By installing this package the error can be solved.
Ubuntu, Debian, Mint, Kali:
sudo apt install build-essentialCentOS, RHEL, Fedora:
sudo dnf install build-essentialInstall Python Development Packages
The most prolific reason for the “error command gcc failed with exit status 1” is the absence of the Python development library or package. The Python development library or package is named “python-devel” or “python-dev” in most of the distributions. According to your python version select the proper python development library installation command from below.
Ubuntu, Debian, Mint, Kali:
sudo apt install python-dev
sudo apt install python3-devCentOS, RHEL, Fedora:
sudo dnf install python-devel
sudo dnf install python3-develInstall libffi, libxslt and openssl Development Packages
Other popular libraries are libffi, libxslt and openssl. They generally required by Python tools and libraries for compilation. So you can install these libraries with the following commands.
Ubuntu, Debian, Mint, Kali:
sudo apt install libxslt-dev libffi-dev libssl-devCentOS, RHEL, Fedora:
sudo dnf install libxslt-devel libffi-devel openssl-develThe error message ‘error command GCC failed with exit status 1’ mainly occurs while installing Python-related third-party libraries for starting the compilation process. This error message mostly occurs in Linux or macOS systems while working with ‘Terminal.’ So, Windows users don’t face such problems because all of their work is GUI-based.
This is a GCC compiler and required libraries error. However, the above picture doesn’t represent the complete error message as its remaining part contains the specific library or application name in which it occurs.
Reasons for the Occurrence of this Error Message
According to the research we have conducted on this error message, these are the most common reasons for it.
- GCC is a compiler used in Python for compiling programs. This compiler requires some additional development libraries and when the compiler can’t find the required libraries, it gives an error message. This is the most common reason for the occurrence of this error message.
- If you’ve faced this error message while installing the Python library software and configuring the PIP source, then the ‘OpenSSL-devel’ might be the cause of this error message.
- Sometimes users face this error message because of applying Windows binaries to a Linux system. This results in an incompatibility between the module and the library you’re trying to install on your machine. So, it’s better to double-check the requirements before searching for any solutions.
To be noted:
The solution to this error message varies from use case to use case because it occurs in several cases. Therefore, before trying any solution, read the use case mentioned in the explanation of every solution. Because this way, it’ll be easier to relate to your use case and solve this error message.
How to Solve the ‘Error Command GCC Failed with Exit Status 1’ Issue?
As mentioned, this error message has different forms. So, read the solutions carefully and apply them only, if you meet their use case. Otherwise, the solution won’t work for you.
1. While Installing ‘Eventlet’
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
Apply this solution, if you meet the following criteria:
- If you’re facing a ‘Python.h’ fatal directory error while installing ‘Eventlet’ or any other library.
Occurrence of ‘error command ‘GCC’ failed with exit status 1′ and facing a ‘Python.h’ fatal directory
OR
- If you’re facing the error message: ‘error command ‘GCC’ failed with exit status 1 CentOS’ while installing the ‘Eventlet’ library on the system to have the ‘Herd’ for software deployment. In this case, the terminal displays the following error message:
Occurrence of ‘error command ‘GCC’ failed with exit status 1′ during installing ‘Eventlet’
OR
- If you’re facing this error message while trying to install some library with the pip command. In this case, people got an error like ‘#include <ffi.h>’ and the compilation terminated by the ‘error: command ‘GCC’ failed with exit status 1.’
OR
- If you’re running the command: ‘docker build –tag python-docker-dev’ and you’ve faced the error message: ‘error command ‘GCC’ failed with exit status 1 docker.‘
If your situation meets one of the above-mentioned use cases, then try the following solution.
Actual Method
Note: After every command, you’ll hit the ‘Enter’ key to execute the typed commands.
- The first step is to ‘update the version of the GCC compiler’ to the latest version because if you skip this, then you might get errors while executing the main commands. So, type the following commands in the ‘Terminal’ window.
Command for Debian, Kali, Mint and UBUNTU:
sudo apt update gcc
Command for CentOS, Fedora and RHEL:
sudo dnf update gcc
Command for MacOS X:
brew install gcc
- Now, you’ll install the ‘Build Essentails’ because these are essential for building the source code of libraries and packages. So, type the following commands in the ‘Terminal’ window.
Command for Debian, Kali, Mint and UBUNTU:
sudo apt install build-essential
Command for CentOS, Fedora and RHEL:
sudo dnf install build-essential
- After successful installation of ‘Build Essentials,’ you’ll install the ‘Python Development Packages’ by running the following commands in the ‘Terminal’ window.
Command for Debian, Kali, Mint and UBUNTU:
sudo apt install python-dev sudo apt install python3-dev (for Python 3 users)
Command for CentOS, Fedora and RHEL:
sudo dnf install python-devel sudo dnf install python3-devel (for Python 3 users)
Note: In the above command, if you’re using an older Python version, just mention that version number after ‘python,’ like ‘python2.6-dev’
- After running all the commands, if you still get an error that’s talking about installing libevent, then you’ll have to install ‘libevent’ with ‘eventlet.’ So, type the following commands.
Command for Debian, Kali, Mint and UBUNTU:
sudo apt-get install libevent-dev
Note: You can also use ‘sudo apt install libevent-dev’ in the above command.
Command for CentOS, Fedora and RHEL:
sudo dnf install libevent-devel
Hopefully, this solution will prove useful for you because it has solved the same error message for other users as well.
But if you’re still receiving the same error message on ‘Red Hat Enterprise Linux RPM software package,’ then try the next solution.
2. For ‘Red Hat Enterprise Linux RPM software package’ Users
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
The use cases for this solution are the same as the above solution. So, if you meet the ‘use cases for ‘Solution # 1,‘ then try the following solution.
Actual Method
If you’re a ‘Red Hat Enterprise Linux RPM software package’ user and the commands of solution # 1 didn’t fix the error message ‘error command ‘GCC’ failed with exit status 1’ for you, then try the following commands in your ‘Terminal’ window.
Note: After every command, you’ll hit the ‘Enter’ key to execute the typed command
For Python 2.7 Users:
If you’re using the 2.7 version of Python, then run the following commands.
sudo yum -y install gcc gcc-c++ kernel-devel
Note: If the above command doesn’t work, then try it by excluding ‘kernel’
sudo yum -y install python-devel
Note: If you want to install the ‘Development Packages,’ then include ‘libxslt-devel libffi-devel OpenSSL-devel’ after the above command. So, your command will be ‘sudo yum -y install python-devel libxslt-devel libffi-devel OpenSSL-devel’
pip install cryptography
Note: In the above command, the ‘cryptography’ is the name of the ‘python package.’ So, you can replace it with your own python package’s name
For Python 3.4 Users:
If you’re using the 3.4 version of Python, then run the following commands.
sudo apt-get install python3-dev pip install ‘your python packet’
Note: In the above command, the ‘your python packet’ will be the name of your own Python package.
3. During Pygame Installation on a macOS system
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
Apply this solution, if you meet the following criteria:
- If you’ve faced the error command ‘GCC’ failed with exit status 1 pygame while installing the ‘Pygame’ on a MacOS system running Catalina and you have reported this error message as: error command ‘GCC’ failed with exit status 1 mac Catalina.’ The error for this case is:
[email protected] ~ % sudo installer -pkg /Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.15.2.pkg -target / installer: Error - the package path specified was invalid: '/Library/Developer/CommandLineTools/Packages/macOS_SDK_headers_for_macOS_10.15.2.pkg'.
If your situation meets the criteria mentioned above, then try the following solution.
Actual Method
If you’ve faced the same error message on a macOS system while installing the Pygame, then use this method because it has helped the other users as well.
>> xcode-select --install xcode-select: error: command line tools are already installed, use "Software Update" to install updates >> env LDFLAGS="-I/usr/local/opt/openssl/include -L/usr/local/opt/openssl/lib" pip install psycopg2==2.8.4 Collecting psycopg2==2.8.4 Using cached psycopg2-2.8.4.tar.gz (377 kB) Installing collected packages: psycopg2 Attempting uninstall: psycopg2 Found existing installation: psycopg2 2.7.7 Uninstalling psycopg2-2.7.7: Successfully uninstalled psycopg2-2.7.7 Running setup.py install for psycopg2 ... done Successfully installed psycopg2-2.8.4
Note: If the above didn’t work, then use ‘install psycopg2-binary’
4. When trying to Build ‘MySQLdb’ on MacOS X Mountain Lion
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
Apply this solution, if you meet the following criteria:
- If you have faced the same error message while trying to build ‘MySQLdb’ on a MacOS system running Mountain Lion. In this case, your error message will look like this:
running build running build_py copying MySQLdb/release.py -> build/lib.macosx-10.6-intel-2.7/MySQLdb running build_ext building '_mysql' extension gcc-4.2 -fno-strict-aliasing -fno-common -dynamic -g -O2 -DNDEBUG -g -O3 -Dversion_info=(1,2,3,'final',0) -D__version__=1.2.3 -I/usr/local/mysql/include -I/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c _mysql.c -o build/temp.macosx-10.6-intel-2.7/_mysql.o -Os -g -fno-common -fno-strict-aliasing -arch x86_64 unable to execute gcc-4.2: No such file or directory error: command 'gcc-4.2' failed with exit status 1
If your situation meets the criteria mentioned above, then try the following solution.
Actual Method
If you’ve faced the ‘error: command ‘gcc-4.2’ failed with exit status 1’ while trying to build ‘MySQLdb’ on Mac OSX running Mountain Lion, then you can use the following command
sudo ln -s /usr/bin/gcc /usr/bin/gcc-4.2
5. While Installing the ‘python-sane’ Module
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
Apply this solution, if you meet the following criteria:
- If you’ve faced the same error code while trying to install the ‘python-sane’ module. In this case, the users have reported the following error message:
If your situation meets the criteria mentioned above, then try the following solution.
Actual Method
If you’ve faced this error message while installing the ‘python-sane’ module, then you can add the ‘libsane-dev’ to your group but exclude the ‘libsane-extras’ package.
6. When Installing ‘psycopg2’
Here, we’ll first mention the use cases, then we’ll move to the actual method to solve the error message under discussion.
Use Cases
Apply this solution, if you meet the following criteria.
- If you’ve faced the above error with psycopg2 in your Mac. In this case, the error message looks like this:
Occurrence of ‘error command ‘GCC’ failed with exit status 1′ during installing ‘psycopg2’ on MacOS Mojave
If your situation meets the criteria mentioned above, then try the following solution.
Actual Method
If you’re installing ‘psycopg2’ and you’ve received the error message: ‘error: command ‘/usr/bin/clang’ failed with exit status 1,’ then you can try the following commands in your code.
brew reinstall openssl export LIBRARY_PATH=$LIBRARY_PATH:/usr/local/opt/openssl/lib/
|
188 / 187 / 46 Регистрация: 24.03.2011 Сообщений: 670 |
|
|
1 |
|
|
09.09.2016, 23:59. Показов 2952. Ответов 8
Приветствую. Использую Android Studio. Раньше работало; теперь после переустановки системы не хочет собираться даже пустой проект (пустой — в смысле с выбранным по-умолчанию пустым Activity). Ничего не изменял, не удалял и т.п. Никто не в курсе, в чем может быть дело? В логе такая штука: Кликните здесь для просмотра всего текста
Gradle sync started PS
0 |
repareDebugUnitTestDependencies, :app:generateDebugAndroidTestSources]|
Модератор 3352 / 2127 / 349 Регистрация: 13.01.2012 Сообщений: 8,290 |
|
|
10.09.2016, 07:53 |
2 |
|
monolit, какой номер API задаёте при создании проекта и какие скачены в SDK?
0 |
|
188 / 187 / 46 Регистрация: 24.03.2011 Сообщений: 670 |
|
|
10.09.2016, 14:27 [ТС] |
3 |
|
Пробовал разные, и скачивал их тоже (19, к примеру). Сперва грешил на отсутствие нужного, но после загрузки части из них ничего особо не поменялось…
0 |
|
Модератор 3352 / 2127 / 349 Регистрация: 13.01.2012 Сообщений: 8,290 |
|
|
10.09.2016, 15:35 |
4 |
|
monolit, AS-причуды, подождем счастливцев которые с ней работали, мне тоже интересно знать в чем причина загона — видел аналогичное на одной из машин — без красноты были только проекты для которых при создании выбирался андроид 7-й аппараты для которого я даже не знаю есть в природе или нет
0 |
|
34 / 34 / 21 Регистрация: 01.11.2013 Сообщений: 319 |
|
|
10.09.2016, 15:54 |
5 |
|
Еще проект не видит `R` monolit, у меня решается выполнением ‘Build -> cleanProject’
0 |
|
2882 / 2294 / 769 Регистрация: 12.05.2014 Сообщений: 7,978 |
|
|
10.09.2016, 17:37 |
6 |
|
это руки
0 |
|
Модератор 3352 / 2127 / 349 Регистрация: 13.01.2012 Сообщений: 8,290 |
|
|
10.09.2016, 18:20 |
7 |
|
Паблито, не не , не знаю как в этом случае но в том случае что видел я это были может и руки но скорее всего руки гугла) — абсолютно чистый проект создавался весь в крови если выбиралось API отличное от самого распоследнего
0 |
|
188 / 187 / 46 Регистрация: 24.03.2011 Сообщений: 670 |
|
|
10.09.2016, 20:09 [ТС] |
8 |
|
Ни clean, ни что-то еще не помогало. Вспомнив траблы с Эклипсом, переустановил AS. И все заработало) Уж не знаю, в чем было дело — устанавливал почти также, как в прошлый раз, разве что папку с sdk изменил (нет, пробелов там не было, и не на русском языке)… Спасибо всем за участие.
1 |
|
3 / 3 / 1 Регистрация: 07.05.2014 Сообщений: 20 |
|
|
26.05.2018, 22:48 |
9 |
|
В моем случае слетела директория Java JDK, и Gradle банально не мог собрать приложение.
0 |
- Remove From My Forums
-
Question
-
Hi All,
We currently create a BUILD pipeline but getting the the error that mention
Error: D:a1sgradlew.bat failed with return code: 1May I ask need how to solve it?
##[section]Starting: gradlew build ============================================================================== Task : Gradle Description : Build using a Gradle wrapper script Version : 2.149.1 Author : Microsoft Corporation Help : [More Information](https://go.microsoft.com/fwlink/?LinkID=613720) ============================================================================== SYSTEMVSSCONNECTION exists true [command]C:Windowssystem32cmd.exe /D /S /C "D:a1sgradlew.bat build" 'android' is not recognized as an internal or external command, operable program or batch file. Downloading https://services.gradle.org/distributions/gradle-5.1.1-all.zip ............................................................................................................................ Unzipping C:javagradleuserwrapperdistsgradle-5.1.1-all97z1ksx6lirer3kbvdnh7jtjggradle-5.1.1-all.zip to C:javagradleuserwrapperdistsgradle-5.1.1-all97z1ksx6lirer3kbvdnh7jtjg Welcome to Gradle 5.1.1! Here are the highlights of this release: - Control which dependencies can be retrieved from which repositories - Production-ready configuration avoidance APIs For more details see https://docs.gradle.org/5.1.1/release-notes.html Starting a Gradle Daemon (subsequent builds will be faster) > Configure project :app File C:UsersVssAdministrator.androidrepositories.cfg could not be loaded. Checking the license for package Android SDK Build-Tools 28.0.3 in C:javaandroidsdkandroid-sdklicenses Warning: License for package Android SDK Build-Tools 28.0.3 not accepted. Checking the license for package Android SDK Platform 28 in C:javaandroidsdkandroid-sdklicenses Warning: License for package Android SDK Platform 28 not accepted. FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':app'. > Failed to install the following Android SDK packages as some licences have not been accepted. build-tools;28.0.3 Android SDK Build-Tools 28.0.3 platforms;android-28 Android SDK Platform 28 To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager. Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html Using Android SDK: C:javaandroidsdkandroid-sdk * Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 2m 38s Error: D:a1sgradlew.bat failed with return code: 1 at ChildProcess.<anonymous> (D:a_tasksGradle_8d8eebd8-2b94-4c97-85af-839254cc6da42.149.1node_modulesvsts-task-libtoolrunner.js:639:25) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at maybeClose (internal/child_process.js:886:16) at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) No test result files matching D:a1s**TEST-*.xml were found, so publishing JUnit test results is being skipped. ##[error]Error: D:a1sgradlew.bat failed with return code: 1 ##[section]Finishing: gradlew buildThanks for the help.
I’m NOOB developer
-
Moved by
Friday, April 26, 2019 1:38 PM
Not a C# question
-
Moved by
I’m a beginner trying to learn Rust and I’m having this error when I try to compile the «Hello, World!» program. I’m using Linux Mint 19.3 Cinnamon and my computer is a AMD FX(tm)-8150 Eight-Core Processor × 4, 16 Gb RAM, Radeon RX 480. When I try to compile I get this error:
Compiling hello-rust v0.1.0 (/home/anderson/Documents/RustProjects/hello-rust) Running rustc --crate-name hello_rust --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=f5d98f7f530d8660 -C extra-filename=-f5d98f7f530d8660 --out-dir /home/anderson/Documents/RustProjects/hello-rust/target/debug/deps -C incremental=/home/anderson/Documents/RustProjects/hello-rust/target/debug/incremental -L dependency=/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps error: linking with cc failed: exit code: 1 | = note: «cc» «-Wl,—as-needed» «-Wl,-z,noexecstack» «-m64» «-L» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.1aelypo19v5seji.rcgu.o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.27c9sdkflbseeeny.rcgu.o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.2dzl24l4vecrofzp.rcgu.o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.2uns1w1zpao4myhy.rcgu.o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.49c6gu8u4gmo03yp.rcgu.o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.bqxerc3uzhzrm50.rcgu.o» «-o» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps/hello_rust-f5d98f7f530d8660.49vi15hdj4va6uqw.rcgu.o» «-Wl,—gc-sections» «-pie» «-Wl,-zrelro» «-Wl,-znow» «-nodefaultlibs» «-L» «/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps» «-L» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib» «-Wl,—start-group» «-Wl,-Bstatic» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libstd-8bb11f807a7b6b4c.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libpanic_unwind-ca8087507780d964.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libhashbrown-259c92b387c1c166.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_alloc-16e0a2fbbb8e14b3.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libbacktrace-8a1651b8e23d2aaf.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libbacktrace_sys-23bdd98b0574083e.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_demangle-855a92055ec33e2e.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libunwind-24c70dd44fbacdfb.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcfg_if-b326273841bae587.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-ac3c1f0e16507051.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/liballoc-a5729542b65954aa.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/librustc_std_workspace_core-09bd1119ab1cad7d.rlib» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcore-9a787681bfbeaf61.rlib» «-Wl,—end-group» «/home/anderson/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/rustlib/x86_64-unknown-linux-gnu/lib/libcompiler_builtins-5a0398ee67f74664.rlib» «-Wl,-Bdynamic» «-ldl» «-lrt» «-lpthread» «-lgcc_s» «-lc» «-lm» «-lrt» «-lpthread» «-lutil» «-ldl» «-lutil» = note: /usr/bin/ld: cannot find Scrt1.o: No such file or directory /usr/bin/ld: cannot find crti.o: No such file or directory collect2: error: ld returned 1 exit status
error: aborting due to previous error
error: could not compile hello-rust.
Caused by: process didn’t exit successfully: rustc --crate-name hello_rust --edition=2018 src/main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -Cembed-bitcode=no -C debuginfo=2 -C metadata=f5d98f7f530d8660 -C extra-filename=-f5d98f7f530d8660 --out-dir /home/anderson/Documents/RustProjects/hello-rust/target/debug/deps -C incremental=/home/anderson/Documents/RustProjects/hello-rust/target/debug/incremental -L dependency=/home/anderson/Documents/RustProjects/hello-rust/target/debug/deps (exit code: 1)
Does anyone knows what is happening and how to solve this problem?