pre-egcs 1.1 status for *-rtems
Jeffrey A Law
law@cygnus.com
Mon Jul 13 21:58:00 GMT 1998
In message < Pine.BSF.3.96.980713072427.278A-100000@vespucci.advicom.net >you w:
> > You're working from a single source tree right, with some recent
> > version of gas? If so, I would have expected both of those to be
> > defined to "1".
>
> Yes I nearly always do single tree builds. I am working with binutils
> 2.9.1. Depending on what I am doing, I have been switching between newlib
> 1.8.0 and 1.8.1.
OK.
> Below my signature. :) It is just at the limits of what I would be
> willing to send to the list.
The list easily handled that attachment. 17kbytes easily fits under
the 40kbyte limit :-)
It looks like the configure script doesn't think you're in a single
source tree build environment:
+ echo -n checking assembler alignment features...
checking assembler alignment features... + echo configure:5147: checking assembl
er alignment features
+ gcc_cv_as=
+ gcc_cv_as_alignment_features=
+ [ -x as ]
+ [ -f ../src/gcc/../gas/configure.in ]
+ [ xi686-pc-linux-gnu = xi386-pc-rtems ]
+ [ x != x ]
+ echo
If you look at gcc/configure.in:
if [[ -x as$host_exeext ]]; then
# Build using assembler in the current directory.
gcc_cv_as=./as$host_exeext
elif [[ -f $srcdir/../gas/configure.in ]]; then
[ ... parse gas source files for version info ... ]
elif [[ x$host = x$target ]]; then
# Native build.
gcc_cv_as=as$host_exeext
fi
If you're in the gcc object directory, does "../src/gcc/../gas/configure.in"
exist?
jeff
More information about the Gcc
mailing list