Skip to contentSkip to conversation

Updating include/asm symlink when $ARCH changes

DISCUSSION Martin Michlmayr 3 participants 3 messages Sep 27, 2007

lore
Share & tools
lore
#0 lore raw

I cross compile arm and mips kernels from the same kernel tree. When I build a kernel the first time with a fresh kernel tree, the include/asm symlink is set properly. However, when I compile for a different $ARCH, the include/asm is not changed and the build fails.

Would it be possible for the build system to update the include/asm symlink when it doesn't correspond to the architecture you're currently trying to build for?

Signature · 2 lines
Martin Michlmayr
http://www.cyrius.com/
#1 lore raw
Quoted 1 line · Martin Michlmayr

I cross compile arm and mips kernels from the same kernel tree.

You can use O= feature and skip this issue completely.

make ARCH=mips O=../build/mips ...
make ARCH=arm O=../build/arm ...

Quoted 8 lines

When
I build a kernel the first time with a fresh kernel tree, the include/asm symlink is set properly. However, when I compile for a different $ARCH, the include/asm is not changed and the build fails.

Would it be possible for the build system to update the include/asm symlink when it doesn't correspond to the architecture you're currently trying to build for?

#2 lore raw
In reply to Martin Michlmayr
Quoted 8 lines · Martin Michlmayr

I cross compile arm and mips kernels from the same kernel tree. When I build a kernel the first time with a fresh kernel tree, the include/asm symlink is set properly. However, when I compile for a different $ARCH, the include/asm is not changed and the build fails.

Would it be possible for the build system to update the include/asm symlink when it doesn't correspond to the architecture you're currently trying to build for?

You are not the first to ask for this - suprise. Alexey point out a good solution but I have added to my tod list to do something a bit more intelligent when ARCH changes.

The patches I have seen so far has been lacking fundamental functionality and on top of this I hope to find a nice way to preserve CROSSCOMPILE since that often change too.

Sam