linux-kernel - Re: [PATCH] kbuild: don't use a symlink for update-po-config

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:	Sun, 18 Dec 2011 22:05:18 +0100
From:	Michal Marek <mmarek@...e.cz>
To:	Peter Foley <pefoley2@...izon.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Kbuild Mailing List <linux-kbuild@...r.kernel.org>
Subject: Re: [PATCH] kbuild: don't use a symlink for update-po-config

On Sun, Dec 18, 2011 at 09:57:25PM +0100, Michal Marek wrote:
> On Sat, Oct 22, 2011 at 11:19:22AM -0400, Peter Foley wrote:
> > This patch changes update-po-config to not create a symlink in arch/um 
> > because this fails with make O= builds.
> > It also improves the V=0 output. 
> > 
> >   GEN     /usr/src/lto/work/Makefile
> >   GEN config
> > ln: failed to create symbolic link `arch/um/Kconfig': No such file or directory
> > make[3]: *** [update-po-config] Error 1
> > make[2]: *** [update-po-config] Error 2
> > make[1]: *** [sub-make] Error 2
> > make: *** [all] Error 2
> > 
> > Signed-off-by: Peter Foley <pefoley2@...izon.net>
> > ---
> >  scripts/kconfig/Makefile |   11 +++++------
> >  1 files changed, 5 insertions(+), 6 deletions(-)
> 
> Applied to kbuild.git#kconfig, thanks.

After appying this, I noticed that UML changed once more in 3.2, so this
fix is not sufficient. So I'll instead apply a fix from Paul Bolle to
the rc-fixes branch and send it to Linus for 3.2. Please send a patch
that only fixes the alignment issue in make output.

Thanks,
Michal
--
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/