* [ECOS] Error trying to exec 'cc1plus'
@ 2009-04-05 5:22 Paul D. DeRocco
2009-04-06 7:46 ` Ross Younger
0 siblings, 1 reply; 2+ messages in thread
From: Paul D. DeRocco @ 2009-04-05 5:22 UTC (permalink / raw)
To: eCos Discuss
I installed eCos 3.0 in a fresh directory (/opt/ecos3) under Cygwin, and
installed the arm-eabi tools in the default location. I can run the compiler
under the name gcc, because there is a version under that name in
/opt/ecos3/gnutools/arm-eabi/arm-eabi/bin
but it complains that it can't find cc1plus.exe. I can also run the compiler
under its explicit name arm-eabi-gcc, which is found in
/opt/ecos3/gnutools/arm-eabi/bin
and it works fine. The cc1plus executable is contained in
/opt/ecos3/gnutools/arm-eabi/libexec/gcc/arm-eabi/4.3.2
The problem appears to be that the programs search path built into the
compiler includes the string
../libexec/gcc/arm-eabi/4.3.2
which works when appended to the arm-eabi-gcc location but not when appended
to the gcc location.
So my question is: why are we given versions of the commands under short
names, if they don't work? Is there some reason the commands with the short
names aren't just put into the same directory as the versions with the full
names?
--
Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix.netcom.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [ECOS] Error trying to exec 'cc1plus'
2009-04-05 5:22 [ECOS] Error trying to exec 'cc1plus' Paul D. DeRocco
@ 2009-04-06 7:46 ` Ross Younger
0 siblings, 0 replies; 2+ messages in thread
From: Ross Younger @ 2009-04-06 7:46 UTC (permalink / raw)
To: eCos Discuss
Paul D. DeRocco wrote:
> [bin/arm-eabi-gcc vs. arm-eabi/bin/gcc]
> So my question is: why are we given versions of the commands under short
> names, if they don't work? Is there some reason the commands with the short
> names aren't just put into the same directory as the versions with the full
> names?
You should always invoke a cross-compiler via its full name. The toolchain
provides the short-named versions for its own internal use.
As a general rule you should only add the directory containing the
full-named tools to your PATH - and this is what ecosenv.sh does - because
on a typical machine the short-named tools would conflict with the
host-native compiler and other tools in /usr/bin.
Ross
--
eCosCentric Ltd, Barnwell House, Barnwell Drive, Cambridge CB5 8UU, UK
Registered in England no. 4422071. www.ecoscentric.com
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-04-05 10:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-04-05 5:22 [ECOS] Error trying to exec 'cc1plus' Paul D. DeRocco
2009-04-06 7:46 ` Ross Younger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).