unionfs crosscompile problem

    unionfs.inc puts buildsystem flags into the target CFLAGS:


    Code
    CFLAGS = "${BUILD_OPTIMIZATION}"


    This doesn't work if BUILD_OPTIMIZATION contains architecture specific stuff, as in my case:


    Code
    BUILD_OPTIMIZATION = "-march=nocona -O2 -pipe"


    results in


    Zitat


    Assembler messages:
    Warning: A different -march was already specified, is now nocona
    Warning: A different -march was already specified, is now mips32
    cc1: error: unrecognized command line option "-march=nocona"


    Simply removing CFLAGS = "${BUILD_OPTIMIZATION}" works, but I'm wondering what the purpose of this construction was.

    Nobody?
    Seems like I'm the only one using BUILD_OPTIMIZATION...


    I've tried to contact the unionfs OE maintainer, but so far no reaction.


    Could this issue be fixed in the dreambox OE branch?


    (fix is simple, remove the CFLAGS = "${BUILD_OPTIMIZATION}" line from unionfs.inc)


    When you are compiling for dm7025, the architecture is mips32.
    The "nocona" architecture seems to be some kind of 64-bit intel processor.
    Just remove the "-march=nocona". As the compiler says, the "mips32" is already set.

    Zitat

    Originally posted by tero_
    When you are compiling for dm7025, the architecture is mips32.
    The "nocona" architecture seems to be some kind of 64-bit intel processor.
    Just remove the "-march=nocona". As the compiler says, the "mips32" is already set.


    I have -march=nocona in my native cflags, in order to produce faster cross-tools.
    That's what BUILD_OPTIMIZATION is for.


    The problem is that unionfs draws BUILD_OPTIMIZATION into the target cflags.
    I'm convinced that should never happen.