linux-kernel - Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Dec 2006 21:31:23 +0100 (CET)
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	Mark Glines <mark@...nes.org>
cc:	linuxppc-dev@...abs.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.20-rc2: forgot how to make a zImage on powerpc?

On Mon, 25 Dec 2006, Mark Glines wrote:

> Mark Glines wrote:
> > Hmm.  I'm trying to build 2.6.20-rc2 on a little powerpc box with
> > arch/powerpc/configs/linkstation_defconfig, and I get:
> ...
> >   MODPOST vmlinux
> > ln: accessing `arch/powerpc/boot/zImage': No such file or directory
> > make[1]: *** [arch/powerpc/boot/zImage] Error 1
> > make: *** [zImage] Error 2
> > 
> > So, uh, are we forgetting to go into the right subdirectory to make the
> > actual zImage, or what?  If I'm just doing something wrong, I'd love to know
> > what it is.
> > 
> > I'll follow up here on lkml if I diagnose this further.  Thanks,
> 
> 
> Followup:  Yeah, it looks like it just doesn't know which format of zImage to
> produce for linkstation.
> 
> I'm not sure what image should be used by default.  I guess it depends on the
> bootloader.  Maybe default to uImage, as uBoot seems to be fairly common on
> these devices?

Yes, uImage is the format used on linkstation. Is there a way to cleanly 
specify this in the kernel sources apart from a comment in Kconfig?

Thanks
Guennadi
---
Guennadi Liakhovetski
-
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/