Am Sonntag, 3. April 2005 17:24 schrieb Peter Barada:
> >When trying to figure out the origin of the problem, I have realized so
> > far, that it is obviously stems from a problem during my local configure
> > process: The xgcc I'm just building tries to pipe the asm result through
> > my "host-as"
>When trying to figure out the origin of the problem, I have realized so far,
>that it is obviously stems from a problem during my local configure process:
>The xgcc I'm just building tries to pipe the asm result through my "host-as"
>instead of the "target-as". I will myself have to look for w
When trying to figure out the origin of the problem, I have realized so far,
that it is obviously stems from a problem during my local configure process:
The xgcc I'm just building tries to pipe the asm result through my "host-as"
instead of the "target-as". I will myself have to look for why co
Björn Haase <[EMAIL PROTECTED]> writes:
> -c ../../gcc/gcc/config/avr/libgcc.S -c libgcc/./_mulqi3.s
^^^
Is this "-c" a typo? It surely doesn't come from mklibgcc.in.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
SuSE Linux Products GmbH, Maxfe
Hi,
when checking out the gcc tree this morning for a clean rebuild and regular
testsuite run, I observed that bootstrap failed. It seems that it is related
to some preprocessor issue:
1.) Problem occures when assembling the libgcc library. First failing
operation is
/home/bmh/gnucvs/head/bui
