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>] [day] [month] [year] [list]
Date:	Tue, 8 Apr 2008 15:10:33 +0200
From:	"Simon Braunschmidt" <sbraunschmidt.linuxlists@...glemail.com>
To:	linux-kernel@...r.kernel.org, arthur.mielimonka@...eca.com
Subject: Fwd: [kbuild, arch/arm] - kernel images do not reflect changed .config >> RESOLVED

resolved, was due to usage of a (very old version) of a c compiler
cache (cachecc1)

2008/4/4, Simon Braunschmidt <sbraunschmidt.linuxlists@...glemail.com>:
> Hi
>
> Problem:
> After changing anything in the .config, updated objects get only into
> arch/arm/boot/Image but not into the other targets.
>
> Steps to reproduce:
> -checkout clean 2.6.24
> -change in Makefile:
> ARCH=arm
> CROSS_COMPILE=arm-none-linux-gnueabi- (codesourcery toolchain to
> support armv7 (cortex a8))
> then:
> #make integrator_defconfig (I tried integrator_defconfig and
> omap_osk_5912_defconfig)
> #make uImage
> #ls -la arch/arm/boot
> #ls -la arch/arm/boot/compressed
> -note the size of :
> boot/Image
> boot/zImage
> boot/uImage
> compressed/vmlinux
> compressed/piggy.gz
> compressed/piggy.o
>
> -now change the .config, for example deactivate FP emulator and
> binformat support
> -save your .config
> #make distclean
> -restore your .config
> #make uImage
>
> only boot/Image and compressed/piggy.gz will have changed, even after
> distclean. Weird.
>
> Is this already fixed? I'm sorry I cannot check easily since i'm not
> allowed to use git in my corporate environment. *duck*
>
> Regards, Gruessla
>
> Simon Braunschmidt
>
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ