powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

Morris Walton-2
I download the tools & ecos using the ecos-install.tcl script, source
the tools using the ecosenv.sh, and get the subject error when trying
make.  The server is:

uname -a:
 Linux a.b.corp 2.6.9-5.0.5.EL #1 Fri Apr 8 14:21:35 EDT 2005 i686 i686
i386 GNU/Linux

I don't see the cpp0 around anywhere.  I "up2date"'d my cpp packages,
but that didn't help.

Thanks,

Morris


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Reply | Threaded
Open this post in threaded view
|

Re: powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

Andrew Lunn-2
On Wed, Nov 02, 2005 at 10:48:10AM -0500, Morris Walton wrote:

> I download the tools & ecos using the ecos-install.tcl script, source
> the tools using the ecosenv.sh, and get the subject error when trying
> make.  The server is:
>
> uname -a:
> Linux a.b.corp 2.6.9-5.0.5.EL #1 Fri Apr 8 14:21:35 EDT 2005 i686 i686
> i386 GNU/Linux
>
> I don't see the cpp0 around anywhere.  I "up2date"'d my cpp packages,
> but that didn't help.

It is the powerpc cpp it is looking for, not the native cpp.

My guess would be you have installed the toolchain in the wrong
place. It should be in /opt/ecos/gnutools/powerpc-eabi. gcc normaly
has its install path hardcoded in the binary. So it will be looking
for
/opt/ecos/gnutools/powerpc-eabi/lib/gcc-lib/powerpc-eabi/3.2.1/cpp0

If you have installed the toolchain somewhere else it won't be able to
find this.

        Andrew
       

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Reply | Threaded
Open this post in threaded view
|

Re: powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

Morris Walton-2


Thanks,

It appears to be installed in the right place:

/opt/ecos/gnutools/powerpc-eabi/lib/gcc-lib/powerpc-eabi/3.2.1/cpp0

here is my g++ -v output (is this right?):

[x@server]$ powerpc-eabi-g++ -v
Reading specs from
/opt/ecos/gnutools/powerpc-eabi/bin/../lib/gcc-lib/powerpc-eabi/3.2.1/specs
Configured with:
/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/source/gcc-3.2.1/configure
--target=powerpc-eabi
--prefix=/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi
--enable-languages=c,c++ --with-gnu-as --with-gnu-ld --with-newlib
--with-gxx-include-dir=/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi/powerpc-eabi/include
Thread model: single
gcc version 3.2.1

Should I have seen the path in there?



Andrew Lunn wrote:

>On Wed, Nov 02, 2005 at 10:48:10AM -0500, Morris Walton wrote:
>  
>
>>I download the tools & ecos using the ecos-install.tcl script, source
>>the tools using the ecosenv.sh, and get the subject error when trying
>>make.  The server is:
>>
>>uname -a:
>>Linux a.b.corp 2.6.9-5.0.5.EL #1 Fri Apr 8 14:21:35 EDT 2005 i686 i686
>>i386 GNU/Linux
>>
>>I don't see the cpp0 around anywhere.  I "up2date"'d my cpp packages,
>>but that didn't help.
>>    
>>
>
>It is the powerpc cpp it is looking for, not the native cpp.
>
>My guess would be you have installed the toolchain in the wrong
>place. It should be in /opt/ecos/gnutools/powerpc-eabi. gcc normaly
>has its install path hardcoded in the binary. So it will be looking
>for
>/opt/ecos/gnutools/powerpc-eabi/lib/gcc-lib/powerpc-eabi/3.2.1/cpp0
>
>If you have installed the toolchain somewhere else it won't be able to
>find this.
>
>        Andrew
>      
>
>  
>


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Reply | Threaded
Open this post in threaded view
|

Re: powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

Andrew Lunn-2
In reply to this post by Andrew Lunn-2
On Wed, Nov 02, 2005 at 03:47:31PM -0500, Morris Walton wrote:

> Thanks,
>
> It appears to be installed in the right place:
>
> /opt/ecos/gnutools/powerpc-eabi/lib/gcc-lib/powerpc-eabi/3.2.1/cpp0
>
> here is my g++ -v output (is this right?):
>
> [x@server]$ powerpc-eabi-g++ -v
> Reading specs from
> /opt/ecos/gnutools/powerpc-eabi/bin/../lib/gcc-lib/powerpc-eabi/3.2.1/specs
> Configured with:
> /home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/source/gcc-3.2.1/configure
> --target=powerpc-eabi
> --prefix=/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi

This is your problem. Like i said, the location the toolchain lives is
hardcoded into the binary. In this case, the hard coded value is:

/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi

If you move the toolchain to there, i expect it will work.

But this is probably not what you wanted. When you built the toolchain
it looks like you got the --prefix option to configure wrong. I
suggest you try configure and build the toolchain again with

--prefix=/opt/ecos/gnutools/powerpc-eabi

        Andrew

--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

Reply | Threaded
Open this post in threaded view
|

Re: powerpc-eabi-g++: installation problem, cannot exec `cpp0': No such file or directory

Bart Veer
>>>>> "Andrew" == Andrew Lunn <[hidden email]> writes:

    Andrew> On Wed, Nov 02, 2005 at 03:47:31PM -0500, Morris Walton wrote:
    >> Thanks,
    >>
    >> It appears to be installed in the right place:
    >>
    >> /opt/ecos/gnutools/powerpc-eabi/lib/gcc-lib/powerpc-eabi/3.2.1/cpp0
    >>
    >> here is my g++ -v output (is this right?):
    >>
    >> [x@server]$ powerpc-eabi-g++ -v
    >> Reading specs from
    >> /opt/ecos/gnutools/powerpc-eabi/bin/../lib/gcc-lib/powerpc-eabi/3.2.1/specs
    >> Configured with:
    >> /home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/source/gcc-3.2.1/configure
    >> --target=powerpc-eabi
    >> --prefix=/home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi

    Andrew> This is your problem. Like i said, the location the
    Andrew> toolchain lives is hardcoded into the binary. In this
    Andrew> case, the hard coded value is:

    Andrew> /home/demonweb/tools/ecos-gnutools-v1.4/r2/powerpc-eabi/x86_linux_lsb1_3/tar_bz2/opt/ecos/gnutools/powerpc-eabi

    Andrew> If you move the toolchain to there, i expect it will work.

    Andrew> But this is probably not what you wanted. When you built
    Andrew> the toolchain it looks like you got the --prefix option to
    Andrew> configure wrong. I suggest you try configure and build the
    Andrew> toolchain again with

    Andrew> --prefix=/opt/ecos/gnutools/powerpc-eabi

That used to be true, but it is no longer necessary to install the
toolchain in the same place as --prefix. The compiler driver figures
out its own location and then uses relative paths, as well as absolute
paths like the prefix.

I suggest checking the access rights on cpp0 to make sure you haven't
lost the execute bit somehow. If that does not work you can try
running strace on a powerpc-eabi-g++ invocation to see what it is
actually trying to do.

Bart

--
Bart Veer                       eCos Configuration Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss