On Tue, May 13, 2014 at 11:54 AM, Gene Cumm <gene.cumm at gmail.com> wrote:> Did you check README or doc/distrib.txt?I've read all files in doc folder as well as done some google search..>> What are the dependencies besides python? >> Could using python be avoided while building extlinux? > > Do you plan on having any COM32 modules in your boot system? Due to the > setup that the root Makefile does, it may be necessary to prune parts of the > Makefile temporarily. I presume you're already using "make bios" as the > prefix to all make commands you execute?I don't know if I need any COM32 modules: I'm building "make bios ..", partitioning disk as gpt and plan to boot a single linux distro: PROMPT 1 TIMEOUT 50 DEFAULT xxx LABEL xxx LINUX /boot/vmlinuz-3.12.19 APPEND root=PARTUUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ rootfstype=ext4 rootdelay=1 I might add some options in text menu, but that's more less all of what I need. Regards, Alexey
> On Tue, May 13, 2014 at 11:54 AM, Gene Cumm <gene.cumm at gmail.com> wrote: > > Did you check README or doc/distrib.txt? > > I've read all files in doc folder as well as done some google search.. > > >> What are the dependencies besides python? > >> Could using python be avoided while building extlinux? > > > > Do you plan on having any COM32 modules in your boot system? Due to the > > setup that the root Makefile does, it may be necessary to prune parts of the > > Makefile temporarily. I presume you're already using "make bios" as the > > prefix to all make commands you execute? > > I don't know if I need any COM32 modules: I'm building "make bios ..", > partitioning disk as gpt and plan to boot a single linux distro: > PROMPT 1 > TIMEOUT 50 > DEFAULT xxx > LABEL xxx > LINUX /boot/vmlinuz-3.12.19 > APPEND root=PARTUUID=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx \ > rootfstype=ext4 rootdelay=1 > > I might add some options in text menu, but that's more less all of what I need. > > Regards, > AlexeyI wonder why the already built-in binaries are not enough / adequate. Or, in other words, I am curious about why do you need to build your own binary files, instead of using the files that are already there in the official archives in kernel.org. Regards, Ady.
On Tue, May 13, 2014 at 7:51 PM, Ady <ady-sf at hotmail.com> wrote:> > I wonder why the already built-in binaries are not enough / adequate. > Or, in other words, I am curious about why do you need to build your > own binary files, instead of using the files that are already there > in the official archives in kernel.org.I don't believe it can be used as is: bash# file syslinux syslinux: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=0xe82a9430ce7456cfea7bcc877fa694740296c2a8, stripped bash# ./syslinux bash: ./syslinux: No such file or directory I have a minimal 64-bit system, where 32-bit libraries are not present. Second, I'd rather use git instead of kernel.org due to the following statement published earlier in one of the threads:> H. Peter Anvin <hpa at zytor.com> 5:30 AM (15 hours ago) > to ??, syslinux > > Please work on the current git, rather than 6.02... 6.02 has a number of > known problems.If you could explain a solution for both, I would gladly use binary provided. Regards, Alexey