I just installed UTM on my M1 Macbook and am running ubuntu-20.04.4 as a Virtual Machine. I've been trying to build and run a code given for an assignment, as requested by the course professor.
An issue rose when I got 'make: g++: Command not found'. I therefore installed Developer tools through the command 'apt-get install build-essential'.
This is where I need help. The tools were installed, but running the 'make' command gave a different error 'g++: error: unrecognized command line error: -m64'.
Note: All the necessary files to build and run the code are provided (e.g: Makefile and Cpp file). I really just have to build and run to see the program output.
Related
I am using ubuntu in windows by WSL. I have installed gnu gcc and various required files required to develop a basic Operating System.
Actually I have installed from this link.
But whenever I try to run command 'i386-elf-gcc', it shows command not found. Interestingly if I run export PATH="$PATH:/usr/local/i386elfgcc/bin" this command from that terminal and rerun 'i386-elf-gcc' it works correctly. This happens every time I try to run the command in a new terminal.
I need to get rid of this problem. What can I do?
I am following this tutorial. I already have .fastq files. I want to install ea-utils.
My setup is Ubuntu 18.04 bionic, via Oracle VM Virtual Box.
In terminal, I entered the command:
>>>sudo apt install ea-utils
E: Unable to locate package ea-utils
First, I installed latest Ubuntu updates via. Software Updater.
Then,
>>>sudo apt-get update
E: Some index files failed to download. They have been ignored, or old ones used instead.
Still throwing an error:
>>>sudo apt-get install ea-utils
Second command said: E: Unable to locate package ea-utils.
You cannot install it using Git-Bash. Git-Bash is not a Linux environment (apt-get is a Linux utility that can be used in a Linux environment). Git-Bash is a subset of the MSYS (or MSYS2, not sure) collection of open source tools compiled for Windows
What you can try is
build your own version of ea-utils for Windows. build guide - I will elaborate if required
check if there are any precompiled binaries for it
Expanding on building/compiling your own binaries of programs
Normally a program is written in a programming language (e.g C/C++, Java) that humans can read. These are plain text files.
That is compiled into something computers can read
This compiled file is executable on the platform which it is compiled for - ends in .exe for Windows
This executable file is distributed as a 'precompiled binary' that is copied into (usually) C:\Program Files by the installation procedure
But things change in the world of open source software
You are given the original files of code written in a programming language
You use a compiler combined with other libraries to compile it into an executable file
MinGW is a collection of tools, including the C/C++ compiler for Windows
GSL is a library that provides some other code that ea-utils depends on for the compilation of the binaries
General instructions for building
(Sorry I cannot test these. I do not use Windows any more)
Install MinGW - accepting the defaults should work fine
Install GSL - try the link that says Setup (again, accept defaults)
Unzip the file you downloaded earlier from ea-utils' GitHub
Open command prompt
cd into the unzipped folder
(based on instructions on their wiki) make
make test
Since your updated question is based on using Ubuntu 18.04 in a VM and you there is still an error, I suggest trying
sudo apt-get update
sudo apt-get install ea-utils
Commonly, software in the Linux word is distributed as "packages" - e.g ea-utils. The first command contacts Ubuntu's repositories (they serve the packages) and generates a list of all the available packages.
That should fix the error of ea-utils not being found.
Following the constant errors being thrown,
Download the .deb file 64-bit version or 32-bit version according to the virtual machine you are running. Open it inside the virtual machine, and follow the onscreen instructions.
When I follow the instructions to get Doppl going, and I run the dopplBuild Gradle task, I get an error message about j2objc returning error code 127. What is going on?
One cause of this is not having a JDK available for command-line use on your development machine. While Android Studio can use its own JDK copy, that does not make javac and related tools available from the command line. The j2objc tool in the Doppl toolchain needs these tools available from the command line.
The simplest solution is to download and install a JDK, following whatever the normal practice is for doing so on your development machine's OS, such as downloading JDK 8 from Oracle's site and installing it. If javac runs successfully from the command line, then try running dopplBuild again and see if you get past the "error code 127" result.
I am having issues compiling this project on zephyr.js, the instructions on their GitHub are for Linux however they do have an environment setup for Windows as well which I have completed to the letter.
When I run the compilation using the makefile I get:
CMake C:/IntelSWTools/ISSM_2016/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc is not a full path to an existing compiler tool.
I am using the msys terminal with MinGW and I have installed CMake separately and configured it... but why is it throwing this error? I have checked, and the file is actually there. If I type C:/IntelSWTools/ISSM_2016/tools/compiler/gcc-ia/5.2.1/bin/i586-intel-elfiamcu-gcc. into the terminal, it also executes the compiler successfully.
Any ideas?
(Before anyone tells me to try on Linux, for now, it is a requirement to use Windows for this project)
I'm trying to run the configure.py for PyQt5 from git bash, but it errors out, giving me a Fatal Error U1077. Some other people have encountered this problem, and I've been trying some of the stuff that other people have been saying, but I'm kind of new to this and it's pretty confusing.
The important section is "fatal error U1077: '.\cl.EXE' : return code '0x000135' " but I don't really know what that means.
Here are the complete steps to configure and install PyQt5 from source, you will need first to run command :
python configure.py
At this step, you did not install PyQt5, you only configured it (basically its installation dir, etc...), Do not specify your qmake path.
Next step is to source your environment variables by running in terminal :
"C:\Qt\Qt5.x.x\5.x\msvc2015\bin\qtenv2.bat"
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat"
Replace the x by your version of Qt. Keep the double quotes, windows does not like spaces ...
Be careful to specify your Visual Studio installation. In windows, "make" is substituted by "nmake" !
the second command will change your path to Visual Studio, just stay in the same terminal and return to your PyQt5 path.
Then you run :
nmake
nmake install
You may encounter an error when you compile QtNfc. Then use :
python configure.py --disable QtNfc
and re-compile everything.
Hope this will helps.
You don't need Git Bash to install PyQt5 on Windows you can use the Windows command prompt. Here is a step by step guide to install PyQt5 using Qt5.5 on Windows (if you are interested in a newer version you just need to adapt the paths):
Download and install Qt5.5.1 + Mingw32
Download and uncompress SIP
Download and uncompress PyQt5.5.1
Bring up command prompt window, navigate to the uncompressed SIP directory, and type the following:
> PATH=C:\Qt\5.5\mingw492_32\bin;C:\Qt\Tools\mingw492_32\bin;%PATH%
> python configure.py -p win32-g++
> mingw32-make
> mingw32-make install
Using the same command prompt window, navigate to the uncompressed PyQt5 directory, and type the following:
> python configure.py --spec win32-g++ --disable QtPositioning --no-qsci-api --no-designer-plugin --no-qml-plugin --confirm-license
> mingw32-make
> mingw32-make install
NOTE #1: that disabling QtPositioning is not really necessary, but sometime the compiler complains that it's not able to locate the qgeolocation.h header, so leave it disabled unless you really need it.
NOTE #2: To date, I was not able to compile the 5.7 version of PyQt5, not the 5.6 version (for some unexplainable errors that I couldn't solve). This is why I wrote this little installation tutorial using PyQt5.5.