New trunk/filo branch

[Vincent Legoll]

Hello,

I was trying to use the new trunk/filo branch, but encountered problems,
it needs a cross compiler to work:

with native x86_64 gcc -m32, I got:

printf.c:(.text+0x344): undefined reference to `__umoddi3'
printf.c:(.text+0x379): undefined reference to `__udivdi3'

those functions are not present in the libgcc.a associated with that compiler...

Whereas with CC=i686-pc-linux-gnu-gcc it works fine.

Then I saw the build.sh script, tried it and it didn't work, I fixed
it with the attached patch,
but this is still not good wrt the crosscompiler issue...

I don't think it is good practice to mess with MAKEFLAGS that way, so
I removed it and
used plain shell variables. I removed the duplicated "-m32" too.

[Stefan Reinauer]

Vincent Legoll wrote:
> Hello,
>
> I was trying to use the new trunk/filo branch, but encountered problems,
> it needs a cross compiler to work:
>
> with native x86_64 gcc -m32, I got:
>
> printf.c:(.text+0x344): undefined reference to `__umoddi3'
> printf.c:(.text+0x379): undefined reference to `__udivdi3'
>
> those functions are not present in the libgcc.a associated with that compiler...

Your native gcc probably lacks a 32bit libgcc installation. You should
upgrade to a fixed compiler.

Which distribution and gcc version are you using?
> Then I saw the build.sh script, tried it and it didn't work, I fixed
> it with the attached patch,
> but this is still not good wrt the crosscompiler issue...

Your patch breaks building on about every Linux x86 64bit platform.
> I don't think it is good practice to mess with MAKEFLAGS that way, so
> I removed it and
> used plain shell variables.

Why would you say it is not good practice?
> I removed the duplicated "-m32" too.

Where did you see a duplicate -m32?