On Wed, 11 Jun 2003, Neil Griffiths wrote:

> gcc: installation problem, cannot exec `cc1': No such file or directory

If your environment is properly installed, you should not get this error.
Try using the DevKit-Advance-R5-Beta-3.lnk to start a shell and see if it
works.

> Okay, I've had this issue before with R4, I know it was an environment
> variable. Taking a look at the FAQ, I can see it's GCC_EXEC_PREFIX. I
> updated this to point at the new R5 like so:
>
> GCC_EXEC_PREFIX=/cygdrive/c/devkitadv-r5-beta-3/lib/gcc-lib/

DKA5 does not use cygwin, so you can just use a normal DOS path instead of
the cygdrive path.

> It exists as
> "C:\devkitadv-r5-beta-3\lib\gcc-lib\arm-agb-elf\3.2.2\cc1.exe" on my
> hard drive, I've installed all of the relevant files - I can only
> assume that either I'm overlooking something or there's an issue with
> this beta version.

Something this basic would not be a problem with the software itself, you
are definitely doing something wrong. From what you have given, I would
guess it may have something to do with having the MS tools in your path.
But, since you did not say if you were using a makefile or exactly what
command line fails, I can't say.

cmd-rc.bat and user.bat can be used as models on how to setup a basic
command line. If they work then figure out the difference. If you have
added all those paths to your system path (using the control panel), I
would clean it up so it only has the basic paths and use batch files to
setup shells for different purposes. That way, an MS Studio cmd
environment will not interfere with the GNU one.

There may even be other variables in your environment which are confusing
gcc. I think that -print-search-dirs will print out where gcc is looking
for executables, that will give you a clue as to what is going on.

Please execute gcc -print-search-dirs, clean up the output (add line
breaks between paths), and send it to me (personally, I don't think anyone
else cares).