REFIX is the target filesystem tree. I
used the same make install command for the native gcc
that I compiled.
Thanks,
Jeff Stevens
--- Kai Ruottu <[EMAIL PROTECTED]> wrote:
> Jeff Stevens wrote:
>
> > .../gcc-3.4.4/configure
> > --build=`../gcc-3.4.4/config.guess`
> &
ve-gcc/gcc'
make[1]: *** [stmp-multilib] Error 2
make[1]: Leaving directory
`/opt/recorder/build-tools/build-native-gcc/gcc'
make: *** [install-gcc] Error 2
How do I install the native compiler?
Thanks,
Jeff Stevens
--- Clemens Koller <[EMAIL PROTECTED]> wrote:
> Hello, Jef
Yes I added the cross-compiler to the path and created
a separate build directory (ppc_gcc).
Thanks,
Jeff Stevens
--- Dave Korn <[EMAIL PROTECTED]> wrote:
> Dave Korn wrote:
> > Jeff Stevens wrote:
> >> Is there a HowTo out there on how to cross
> compile
x
--prefix=/opt/luan2/toolchain/bin --enable-shared
--enable-threads --enable-languages=c
I'm obviously missing something, but can't seem to
find anything on the internet that explains
cross-compiling gcc for another target.
Thanks,
Jeff Stevens
_
s to complete without any issues.
It seems that gcc is having issues with the following
line in gen-as-const.awk:
printf "asm (\"@@@name@@@%s@@@value@@@%%0@@@end@@@\" :
: \"i\" (%s));\n", name, $0;
Is my configure line incorrect, or have I maybe
incorrectly configu
