From: Geoff Levand <geoffrey.levand@am.sony.com>
To: Zitt Zitterkopf <zittware@hotmail.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: Problems compiling kexec-tools
Date: Wed, 13 Jan 2010 09:27:58 -0800 [thread overview]
Message-ID: <4B4E029E.4020404@am.sony.com> (raw)
In-Reply-To: <BAY114-W49E2846C6D653AB15A9A03DD6C0@phx.gbl>
On 01/11/2010 04:01 PM, Zitt Zitterkopf wrote:
> All,
> I'm attempting to compile kexec-tools so I can compile kboot from source.
>
> I've obtained the kexec-tools-2.0.0 source from RPM.
Maybe you could try just using the 2.0.1 sources from here:
http://www.kernel.org/pub/linux/kernel/people/horms/kexec-tools/
> I've done:
> ./configure
> make
>
> which I receive the following errors:
> gcc -lz -g -O2 -static -fno-strict-aliasing -Wall -Wstrict-prototypes -o build/sbin/kexec kexec/kexec.o kexec/ifdown.o kexec/kexec-elf.o kexec/kexec-elf-exec.o kexec/kexec-elf-core.o kexec/kexec-elf-rel.o kexec/kexec-elf-boot.o kexec/kexec-iomem.o kexec/firmware_memmap.o kexec/crashdump.o kexec/crashdump-xen.o kexec/phys_arch.o kexec/proc_iomem.o kexec/virt_to_phys.o kexec/add_segment.o kexec/add_buffer.o kexec/arch_reuse_initrd.o kexec/arch/i386/kexec-x86.o kexec/arch/i386/kexec-x86-common.o kexec/arch/i386/kexec-elf-x86.o kexec/arch/i386/kexec-elf-rel-x86.o kexec/arch/i386/kexec-bzImage.o kexec/arch/i386/kexec-multiboot-x86.o kexec/arch/i386/kexec-beoboot-x86.o kexec/arch/i386/kexec-nbi.o kexec/arch/i386/x86-linux-setup.o kexec/arch/i386/crashdump-x86.o kexec/purgatory.o libutil.a
> kexec/kexec.o: In function `slurp_decompress_file':
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:485: undefined reference to `gzopen'
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:501: undefined reference to `gzread'
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:506: undefined reference to `gzerror'
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:515: undefined reference to `gzclose'
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:517: undefined reference to `gzerror'
> /home/moblin/rpmbuild/BUILD/kexec-tools-2.0.0/kexec/kexec.c:487: undefined reference to `gzerror'
> collect2: ld returned 1 exit status
> make: *** [build/sbin/kexec] Error 1
>
> I've installed zlib:
> zlib-1.2.3-29.4.moblin2.i586.rpm
> zlib-devel-1.2.3-29.4.moblin2.i586.rpm
> so I'm unsure what I've done wrong.
You could try passing the verbose flags and see what
headers and libs get used during the build. Maybe
you'll find some problem there. I think those would
be something like:
gcc -v -Wl,--verbose ...
Or maybe just use:
ld --verbose ...
BTW, have you looked at the petitboot bootloader? For
the most part it is a better choice than kboot.
It provides essentially all the functionality that
kboot does, plus more, it is easier to build, and it
is a currently maintained project.
The petitboot package can be built for x86. That is
how much of its development is done, but OpenWRT does
not yet support an x86 build of petitboot (that
would create a grub second stage image). My plan is
to add x86 PC support next. I don't think it is very
difficult to do, I just have not had time to do it.
You can see some screen shots of petitboot built for
the PS3 here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/ps3-petitboot/
My petitboot development repo is here:
http://git.kernel.org/?p=linux/kernel/git/geoff/petitboot-dev.git
-Geoff
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2010-01-13 17:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 0:01 Problems compiling kexec-tools Zitt Zitterkopf
2010-01-12 0:39 ` Simon Horman
2010-01-12 16:33 ` Zitt Zitterkopf
2010-01-13 17:27 ` Geoff Levand [this message]
2010-01-15 18:47 ` Zitt Zitterkopf
2010-01-15 19:47 ` Geoff Levand
2010-01-16 10:46 ` Andrea Adami
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B4E029E.4020404@am.sony.com \
--to=geoffrey.levand@am.sony.com \
--cc=kexec@lists.infradead.org \
--cc=zittware@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.