similar to: Compiling extlinux statically

On Sat, Aug 8, 2015 at 10:32 AM, Adam Baxter via Syslinux <syslinux at zytor.com> wrote: > Hi, > I'm trying to build extlinux statically, but no matter what CFLAGS or > OPTFLAGS I set in the Makefiles I get bios/extlinux/extlinux: ELF 64-bit > LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared > libs), for GNU/Linux 2.6.24, >

I gave extlinux a whirl, 1. installed debian onto a usb hard drive from laptop (onto /dev/sda1) did *not* install grub or lilo. 2. set up extlinux on /dev/sda # mount /dev/sda1 /mnt/t1 [root at harpo syslinux-3.00]# cd /mnt/t1/ [root at harpo t1]# ls boot/ config-2.6.8-1-386 initrd.img-2.6.8-1-386 System.map-2.6.8-1-386 vmlinuz-2.6.8-1-386 [root at harpo t1]# mkdir boot/extlinux [root

Hello, I was trying to build R from source on Windows XP. I installed software which are mentioned from the follow web page http://www.murdoch-sutherland.com/Rtools/ (Last accessed on Nov. 13th, 2006) . Unfortunately, I got error messages whenever I run 'make all recommended' without modifying 'MkRules' file. I have removed software and reinstalled them several times but I still

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

Dear R People: I am trying to build R-2.5.0 from source on a Windows machinee. I downloaded the tools and such, and started things off. I received some odd errors messages, looked on the R Search and found a similar problem. The suggestion was to re-load "ld.exe". I downloaded and installed everything again. Same problem. I am including my output.

On May 13, 2014 4:04 PM, "Ady" <ady-sf at hotmail.com> wrote: > > 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. > > I don't believe it can be used as is: > > bash# file syslinux > > syslinux: ELF 32-bit LSB executable, Intel 80386, version

Hello syslinux, Merry Christmas! These patches will make extlinux work with umounted ext2/3/4 filesystem, for example: $ extlinux -i /dev/sdXN or $ extlinux -i file_block Also it can work with something like: $ extlinux /dev/sdXN --reset-adv or $ extlinux file_block --reset-adv We don't use a new option (I planed to use "-d" but it is already in use), it will check whether the

From: Gene Cumm <gene.cumm at gmail.com> Fix duplicate spotless target in com32/libutil/Makefile. Signed-off-by: Gene Cumm <gene.cumm at gmail.com> --- diff --git a/com32/libutil/Makefile b/com32/libutil/Makefile index 31754a9..02789ca 100644 --- a/com32/libutil/Makefile +++ b/com32/libutil/Makefile @@ -56,8 +56,6 @@ clean: tidy spotless: clean rm -f *.lss *.a *.c32 *.com

From: Matt Fleming <matt.fleming at linux.intel.com> This series includes a patch (PATCH 1/6) that I sent previously but I thought it was worth sending it again since the rest of the series depends on it, and it also gives a bit of context. These cleanups make it simpler to do the big switchover to ELF modules on the elflink branch because the libraries in $LIBS are now contained in one

If there is anything that you think should have been in Syslinux 4.04 which isn't there please holler now. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

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

Hi, hpa wrote: > On PowerPC (I think) "unsigned char" is the default. In any case it seems a good idea to interpret the character more explicitely. To my experience, one signdness change causes a little tree of consequential signedness changes or questionable cast operations. How about the following instead ? if ((c >= 0 && c <= ' ') || c == '\x7f')

Bryan O'Sullivan wrote: > Update of /home/cvs/klibc/klibc/klibc/arch/i386 > In directory terminus.zytor.com:/tmp/cvs-serv27981/klibc/arch/i386 > > Modified Files: > MCONFIG > Log Message: > Bring sanity to OPTFLAGS. Turn off -fomit-frame-pointer, which is worse > than useless, and use new names for other directives. > This unfortunately breaks older compilers.

--- ../multipath-tools-0.2.8.1/klibc/klibc/arch/i386/MCONFIG 2004-07-20 10:51:42.000000000 +0200 +++ klibc/klibc/arch/i386/MCONFIG 2004-07-27 17:10:12.000000000 +0200 @@ -13,7 +13,7 @@ # them to be cdecl # REGPARM = -mregparm=3 -DREGPARM -gcc_major := $(shell $(CC) -v 2>&1 | awk '/gcc version/{print int($$3)}') +gcc_major := $(shell unset LANG;$(CC) -v 2>&1 | awk

On 02.07.2015 23:12, Thomas Schmitt wrote: > Hi, > > hpa wrote: >> On PowerPC (I think) "unsigned char" is the default. > > In any case it seems a good idea to interpret the character > more explicitely. To my experience, one signdness change causes > a little tree of consequential signedness changes or questionable > cast operations. > How about the

On Fri, 6 Feb 2015, Ady wrote: > ... > But if we are talking about Chromebooks with SeaBIOS, are we talking > about booting kernels in CSM mode? Or in UEFI mode? > > Other than Chromebooks with (stock) SeaBIOS, is this new reported > behavior also seen under other cases / hardware / firmware / kernels > (versions)? Hi Ady, With a clone of the git repo on kernel.org I run

The *.shared targets require -shared on powerpc, and -R leads to linker errors. This patch makes the -R an arch define. ia64 at least requires -R. --- ash/Makefile +++ ash/Makefile 2003/11/27 15:04:02 @@ -36,7 +36,7 @@ $(STRIP) $(PROG) $(PROG).shared: $(OBJS) $(LIBS) - $(LD) $(LDFLAGS) -o $(PROG).shared -e main $(KLIBSRC)/interp.o $(OBJS) -R $(KLIBSRC)/libc.so $(LIBGCC) + $(LD) $(LDFLAGS)

> A Toshiba CB35 Chromebook running Google's stock SeaBIOS reboots after > selecting a relocatable kernel from extlinux 6.03. > > This is a regression caused by commit 8f470e7b > movebits: Add syslinux_memmap_find() > > which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to > the refactoring, prot_mode_size was passed as the length in the first

some files depend on nodes.h, but there is no dependency for that fact. olaf@mandarine:~/klibc-0.87> grep -Er 'include.*nodes.h' ash/ | sed 's-^[^/]\+/\([^.]*\).*-\1.o-' | xargs echo OBJ_NODES = OBJ_NODES = cd.o eval.o exec.o expand.o jobs.o main.o nodes.o options.o parser.o redir.o show.o trap.o var.o make spotless doesnt work reliable, the patch adds a few more targets. Is

A Toshiba CB35 Chromebook running Google's stock SeaBIOS reboots after selecting a relocatable kernel from extlinux 6.03. This is a regression caused by commit 8f470e7b movebits: Add syslinux_memmap_find() which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to the refactoring, prot_mode_size was passed as the length in the first call to syslinux_memmap_type(). After