Alexandre Oliva wrote:
>
> On May 11, 2001, Ralf Corsepius <[EMAIL PROTECTED]> wrote:
>
> > Are you thinking about something in analogy to AC_CHECK_TOOL
> > ($target-cpp or similar?). At least the gnu toolchain does not have
> > such a beast, but it might be worth checking for in the cross
> > compilation case.
>
> > BTW: Why isn't 'cpp' on this list?
>
> There should be a $target-cpp installed with GCC 2.95 or newer.
Are you sure?
# ls /opt/cygwin/bin/*cpp*
/opt/cygwin/bin/cpp
# /opt/cygwin/bin/cpp --version
gcc-2.95.2-9
# ls /opt/rtems/bin/*cpp*
/opt/rtems/bin/cpp
# /opt/rtems/bin/cpp --version
2.95.2
# /opt/rtems/bin/*gcc*
/opt/rtems/bin/arm-rtems-gcc
/opt/rtems/bin/mips-rtems-gcc
/opt/rtems/bin/h8300-rtems-gcc
/opt/rtems/bin/powerpc-rtems-gcc
/opt/rtems/bin/i386-rtems-gcc
/opt/rtems/bin/sh-rtemself-gcc
/opt/rtems/bin/i960-rtems-gcc
/opt/rtems/bin/sh-rtems-gcc
/opt/rtems/bin/m68k-rtems-gcc
/opt/rtems/bin/sparc-rtems-gcc
/opt/rtems/bin/mips64orion-rtems-gcc
AFAIS, with gcc-2.95.2 there is a single ${bindir}/cpp, which is
supposed to be shared between different architectures.
IMHO, this actually might be considered a in gcc-2.95.2, so this
might have been changed since 2.95.2 - I haven't checked later
versions of gcc yet.
> So we
> should probably test for it, to catch cross-compiling cases. But
> then, gcc -E works too, so perhaps this is not necessary.
Fully agreed. When working with gcc-crosses, from my experience, the
only reliable way to get CPP working is to apply gcc -E.
Ralf
--
Ralf Corsepius
Forschungsinstitut fuer Anwendungsorientierte Wissensverarbeitung
(FAW)
Helmholtzstr. 16, 89081 Ulm, Germany Tel: +49/731/501-8690
mailto:[EMAIL PROTECTED] FAX: +49/731/501-999
http://www.faw.uni-ulm.de
