similar to: SYSLINUX 2.12-pre1 released: initial libcom32 release

Peter- Can you please clarify the license of libcom32, from the samples directory in syslinux? I am attempting to create .c32 files that are not encumbered by the GPL, but the conio.c file states that is is covered by the GPL. So far, I have resisted linking with libcom32.a, but is it really your intent to license the library code under GPL, and not something more like the LGPL?

I get a link error when trying to call malloc from libcom32. I tried to simplify the case by adding the malloc to the sample hello.c in the modules directory, but I still get the following error: ld -m elf_i386 -T ../lib/com32.ld -o hello.elf hello.o ../libutil/libutil_com.a ../lib/libcom32.a /usr/lib64/gcc-lib/x86_64-suse-linux/3.3.3/32/libgcc.a ../lib/libcom32.a(malloc.o)(.text+0x13): In

Probably have already seen this, but since I didn't see in the email archives: thune:/usr/src/syslinux/syslinux-2.12-pre1# make install make -C sample com32 all make[1]: Entering directory `/usr/src/syslinux/syslinux-2.12-pre1/sample' make[1]: *** No rule to make target `com32'. Stop. make[1]: Leaving directory `/usr/src/syslinux/syslinux-2.12-pre1/sample' make: *** [installer]

Thank you for your answer. I need to correct some information from my previous post: booting from `/` did not work either. I just assumed it did based on previous experience. But with that successful build on development branch, it did not either. > I would suggest trying first the official binaries that are already > included in the official distribution archive (6.03-pre1). Let me

I'll start off by saying that I'm very new to com32, but I'm having difficulty linking the libcom32.a library into an executable. I'm using syslinux-3.11, I copied the libcom32.a library into my directory and here's the output of my attmept: #ld com32io.o dtimenu.o syslnx.o tui.o --library-path=./ -lcom32 .//libcom32.a(entry.o)(.init+0x42): In function `_start':

I will not push half-finished features into production. I will not push half-finished features into production. I will not push half-finished features into production. I have pushed out syslinux-3.07-pre1; this should have a fix for the chainloading problem. It actually turned out to be multiple problems, some of which makes me believe chain.c32 probably hasn't worked since 2.12 or so.

I'm not seeing how to set this path option? Here is what I get using vesamenu.c32 as an example when moved to a directory outside of the build. The current syslinux 4.06 has all the files in the same directory which is at the root of the cd. ldd vesamenu.c32 linux-gate.so.1 => (0xb77c5000) ../../com32/libutil/libutil_com.c32 => not found ../../com32/lib/libcom32.c32 => not found

Hello all, We're having the following issue: when in UEFI mode, any output/errors from a lua script is invisible! This occurs even just running 'lua -v'. It runs and returns to a (visible) 'boot:' prompt, but there is simply no output visible from lua! (It does do a linefeed, but no visible text appears.) Has anyone encountered this? And/or know of a solution? For

Okay, if one installs syslinux, the declaration for 'detect_cpu' is in com32/include/cpuid.h, but the actual function code isn't available in libcom32.a. It's only available as source down in the com32/modules/ directory, and not actually installed anywhere. Shouldn't 'detect_cpu' be included in libcom32.a? -- Dr. William R. Somsky, Linux Mgr somsky at

On 06.03.2016 18:23, poma wrote: > On 06.03.2016 16:47, poma wrote: >> ... >>> nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ >>> -DHEXDATE="0x56dc3c62" \ >>> -Di386 \ >>> -I/tmp/syslinux-6.04-pre1/core/ \ >>> -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm >>>

... > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ > -I/tmp/syslinux-6.04-pre1/core/ \ > -l ldlinux.lsr -o ldlinux.o -MP -MD ./.ldlinux.o.d /tmp/syslinux-6.04-pre1/core/ldlinux.asm > nasm -f elf -Ox -g -F dwarf -DDATE_STR="''" \ > -DHEXDATE="0x56dc3c62" \ > -Di386 \ >

On Thu, Nov 15, 2018 at 1:10 PM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > Here are some comments and questions for you. > Thanks. I've have my scripts to a better state, including installing/using qemu to uefi and legacy boot the usb stick for testing. It mostly works for me, but the "wget a tarball of binaries" step isn't going to sit well with

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 When I tried to use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu have different background color than that in 3.20. 1. use the menu.c32 from SYSLINUX 3.30-pre1, the simple menu is: http://lfod.nchc.org.tw/stick/syslinux/syslinux_menu_3.30_pre1.jpg 2. use the menu.c32 from SYSLINUX 3.20, the simple menu is:

Issue Statement: PXE booting from BIOS systems works fine on both 6.03 and 6.04-pre1. New clients only support (u)EFI which results in the inability to load remote kernel or initrd. Tested with both Syslinux 6.03 and 6.04-pre1. So far unable to boot any (u)EFI clients unless both initrd and kernel are on PXE server. Using packet captures I see that the URI request for the remote file on the repo

On Fri, 2012-06-29 at 07:42 -0700, syslinux-bot for H. Peter Anvin wrote: > elflink: fix dependency problem in cmenu/Makefile > > Instead of adding library dependencies implicitly, make them explicit > and use --as-needed to avoid bogus DT_NEEDED entries from being > generated. This is fine, but... > diff --git a/com32/cmenu/Makefile b/com32/cmenu/Makefile > index

Hi there, i just build a new ipxelinux.0 with an EMBED=../../syslinux-5/core/pxelinux.0. i'm trying to load up my vesamenu.c32 menu from http:. and offcorse i want this as optimal as possible, with the least needed GET requests. OLD situation with v4: PXE ROM -> ipxelinux.0 (tftp) -> menu.php (http) -> vesamenu.c32 (http) NEW situation with v5: PXE ROM -> ipxelinux.0 (tftp)

This version fixes the install bug from -pre1, and adds console driver capable of parsing ANSI escape codes for libcom32. The ANSI parser is pretty large (almost 3K of code) and pretty dumb (slightly more intelligent than DOS' ANSI.SYS), but has the nice property that it should make it reasonably easy to write screen-oriented applications which will work both on the serial console (where

After so much time and improvements, I'm glad to see and publicize a pre-release, 6.04-pre1 in https://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/6.04/ Personally, I've already been working testing the pre-release as-is and my tests have been positive so far. I appreciate feedback like that from Gabriele Balducci and testing "make bios installer". Yes, there are a

Hello! I've been attempting to add EFI support to a linux live distro (slax), it's built on a syslinux bootloader. I can get EFI to work using menu.c32 on syslinux 6.03; however ideally we'd like the VESA menu as well. When we use the vesamenu.c32 and libcom32.c32 from 6.03 we end up with a blank screen and the machine seems to hang. I've tried adding MENU RESOLUTION based on

On Mon, Dec 3, 2018 at 10:02 AM Ady Ady via Syslinux <syslinux at zytor.com> wrote: > > > Now it is just dd, mkfs and copy in the files we need. > > One less thing to worry about keeping versions consistent. > > > > > > I just noticed those 2 files that were added by > > > > syslinux -i boot.img > > > > (right?) > > > >