Gcc Specs File: How to Get The Installation Path

CreateProcess: No such file or directory

Its specifically told that you need to reboot after you set the environmental variables in windows for migwin.

exec: gcc: executable file not found in %PATH% when trying go build

gcc (the GNU Compiler Collection) provides a C compiler. On Windows, install TDM-GCC. The github.com/miekg/pkcs11 package uses cgo. Cgo enables the creation of Go packages that call C code.

How to get gcc's search path for Ada specs

gnat ls -v will give you the default search paths.

If you want to install your own Ada library, you should place a project file (.gpr) in the "Project Search Path", which will tell gnat where to find the ada and ali files and the library.

Normally, you will place the ada files in /usr/[local/]include/myadalib and the ali files in /usr/[local/]lib/myadalib and maybe link the .so file into /usr/[local/]lib, but you can put them anywhere you want. The important thing is to place the project file (myadalib.gpr) in the project search path.

You can even adjust the project search path by setting the ADA_PROJECT_PATH environment variable.

how to install gcc on windows 7 machine?

EDIT Since not so recently by now, MinGW-w64 has "absorbed" one of the toolchain building projects. The downloads can be found here. The installer should work, and allow you to pick a version that you need.

Note the Qt SDK comes with the same toolchain. So if you are developing in Qt and using the SDK, just use the toolchain it comes with.

Another alternative that has up to date toolchains comes from... harhar... a Microsoft developer, none other than STL (Stephan T. Lavavej, isn't that a spot-on name for the maintainer of MSVC++ Standard Library!). You can find it here. It includes Boost.

Another option which is highly useful if you care for prebuilt dependencies is MSYS2, which provides a Unix shell (a Cygwin fork modified to work better with Windows pathnames and such), also provides a GCC. It usually lags a bit behind, but that is compensated for by its good package management system and stability. They also provide a functional Clang with libc++ if you care for such thing.

I leave the below for reference, but I strongly suggest against using MinGW.org, due to limitations detailed below. TDM-GCC (the MinGW-w64 version) provides some hacks that you may find useful in your specific situation, although I recommend using vanilla GCC at all times for maximum compatibility.

---

GCC for Windows is provided by two projects currently. They both provide a very own implementation of the Windows SDK (headers and libraries) which is necessary because GCC does not work with Visual Studio files.

1. The older mingw.org, which @Mat already pointed you to. They provide only a 32-bit compiler. See here for the downloads you need:

   • Binutils is the linker and resource compiler etc.
   • GCC is the compiler, and is split in core and language packages
   • GDB is the debugger.
   • runtime library is required only for mingw.org
   • You might need to download mingw32-make seperately.
   • For support, you can try (don't expect friendly replies) mingw-users@lists.sourceforge.net

   Alternatively, download mingw-get and use that.

2. The newer mingw-w64, which as the name predicts, also provides a 64-bit variant, and in the future hopefully some ARM support. I use it and built toolchains with their CRT. Personal and auto builds are found under "Toolchains targetting Win32/64" here. They also provide Linux to Windows cross-compilers. I suggest you try a personal build first, they are more complete. Try mine (rubenvb) for GCC 4.6 to 4.8, or use sezero's for GCC 4.4 and 4.5. Both of us provide 32-bit and 64-bit native toolchains. These packages include everything listed above. I currently recommend the "MinGW-Builds" builds, as these are currently sanctioned as "official builds", and come with an installer (see above).

   For support, send an email to mingw-w64-public@lists.sourceforge.net or post on the forum via sourceforge.net.

Both projects have their files listed on sourceforge, and all you have to do is either run the installer (in case of mingw.org) or download a suitable zipped package and extract it (in the case of mingw-w64).

There are a lot of "non-official" toolchain builders, one of the most popular is TDM-GCC. They may use patches that break binary compatibility with official/unpatched toolchains, so be careful using them. It's best to use the official releases.

How do I change GCC's default search directory for crti.o?

You can use an absolute path in the *startfile: and *endfile: sections in the specs file, instead of the default relative paths. This will override GCC's choice of the default location.

gcc without full path: error trying to exec 'cc1': execvp: No such file or directory

I solved this problem with simple solution.

export PATH

After this command, compile with relative path will be succeed.

---

Roads to found this:

• I test if add PATH to libexec can compile.

$ PATH=${PATH}:/usr/libexec/gcc/i686-test-linux/8.3.0/ -> Successful

According to strace log, I think gcc does not use $PATH to search cc1/cc1plus. Why?

• I test if PATH to /usr/bin can compile. (by mistake)

$ PATH=${PATH}:/usr/bin -> Successful

• Why this success? I think PATH already contains "/usr/bin"

$ echo ${PATH}
/sbin:/usr/sbin:/bin:/usr/bin

• I test if passed $PATH simply.

$ PATH=${PATH} gcc -> Successful

• What the difference between $ gcc and $ PATH=$PATH gcc???

$ set
HOME='/'
HOSTNAME='TEST0'
IFS='
'
LINENO=''
OLDPWD='/'
OPTIND='1'
PATH='/sbin:/usr/sbin:/bin:/usr/bin'
PPID='2701'
PS1='\w \$ '
PS2='> '
PS4='+ '
PWD='/'
SHLVL='8'
TERM='linux'

$ export
export HOME='/'
export OLDPWD='/'
export PWD='/'
export SHLVL='8'
export TERM='linux'

Oh, PATH is not exported as environment variables. only existed as shell variables...

---

Related Topics