On Sat, 2006-11-18 at 09:53 +0000, Pedro Alves wrote:
> Did you ever get to analise this more? Look at the path, and understand why 
> the i386 as is being called?
> Looks like something is trying to call the native (i386) as, but it ends up 
> picking that script on the way.
> I guess building with CFLAGS=-v would help pin this down.

Yes I did, that's how I came up with the workaround. And I've looked
around the net and found confirmation for it.

BTW it's not the i386 as that gets called, it's the other way around:
the src/build-cegcc/gcc/gcc/as script gets generated somehow in the gcc
configuration steps, and contains :
        #!/bin/sh
        exec /opt/cegcc/bin/arm-wince-cegcc-as "$@"

which causes it to call the new binutils cross-assembler, where it
should call the native i386 assembler instead.

It happens to do that because . is in my path before system directories;
this may be why you don't see it :
        sh-3.00$ findpath as
        as :./as  /usr/bin/as   
        sh-3.00$ pwd

(findpath is a script of my own that does something similar to
"whereis".)

> In the meantime, with a comment, that change is ok for trunk.

Thanks, done.

        Danny
-- 
Danny Backx ; danny.backx - at - scarlet.be ; http://danny.backx.info

Attachment: signature.asc
Description: This is a digitally signed message part

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cegcc-devel mailing list
Cegcc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/cegcc-devel

Reply via email to