linux-kernel - Re: Updating include/asm symlink when $ARCH changes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 27 Sep 2007 13:30:19 +0200
From:	Sam Ravnborg <sam@...nborg.org>
To:	Martin Michlmayr <tbm@...ius.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Updating include/asm symlink when $ARCH changes

On Thu, Sep 27, 2007 at 11:25:21AM +0200, Martin Michlmayr wrote:
> 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/