similar to: Register parameters are unsafe with gcc 3.3.2

In klibc-0.114, any shell script like this: ====================================================================== #!/path/to/klibc-0.114/ash/sh echo hi ====================================================================== ...elicits the following error when executed: /var/tmp/hack.sh: Can't open /var/tmp/hack.sh Running under strace, I get: execve("/var/tmp/hack.sh",

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Was just working with the latest 3.54, and find that the Makefile in the menu directory didn't work until I added the /include/syslinux to the file. < CFLAGS = $(M32) -mregparm=3 -DREGPARM=3 -W -Wall - march=i386 -Os -fomit-frame-pointer -I$(LUDIR)/include - I$(COM32DIR)/include -I$(COM32DIR)/include/syslinux -Ilibmenu - D__COM32__ -

Hi, I am trying to compile the version on rhel 5.x box. Nasm version 0.98.39 I extracted the tar.gz and ran make in the extracted directory. Here is where it stops. gcc -Wp,-MT,rawcon.o,-MD,./.rawcon.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables

Hi I've managed to compile klibc 0.198 and run the hello world program. How can I compile my own program? Can someone give an example or provide a simple wrapper program for doing this? like uclibc did with their earlier versions. I looked at the make process and did a bit reading and figure out this much: gcc -Wp,[preprocessor options] -MT,[target_name_I_think] tests/hello.o,

Please be aware that I HAVE NOT TESTED THIS PROGRAM... please try it in a "safe" environment since for all I know it could nuke your "real root" by mistake. -hpa

04.02.2016 22:05, Jean-Marc Valin ?????: > I can see how that would cause multiple rate changes. At the same time, > since this would be using the interpolated code (unless you're really > lucky with the rate), the cost shouldn't be too high. BTW, do you know > how often the rate gets updated? The rate is, by default, updated every 10 seconds. And sometimes (especially with

I have, hopefully, found and fixed the issue with non-kernel binaries that appeared in 3.35. As a result, I have pushed out 3.36-pre6 and am classifying it as a release candidate. Please try it out, especially if you have had problems with 3.35. ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

--- ../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

make[1]: Entering directory `/syslinux-4.02-6-ge841d69/dos' gcc -Wp,-MT,syslxopt.o,-MD,./.syslxopt.o.d -m32 -ffreestanding -fno-stack-protector -fwrapv -freg-struct-return -march=i386 -Os -fomit-frame-pointer -mregparm=3 -DREGPARM=3 -msoft-float -fno-exceptions -fno-asynchronous-unwind-tables -fno-strict-aliasing -falign-functions=0 -falign-jumps=0 -falign-labels=0 -falign-loops=0

What do I need to do to fix this? [jonsmirl@smirl klibc-0.184]$ make make[1]: Entering directory `/home/dri/klibc-0.184/klibc' gcc -Wp,-MT,syscalls.nrs,-MD,./.syscalls.nrs.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include

2012/6/5 Kok, Auke-jan H <auke-jan.h.kok@intel.com> wrote on systemd-devel list: > It seems your system is taking well into 15+ seconds before btrfs is > actually *ready* on your system, which seems to be the main hiccup > (note, speculation here). I''ve personally become a bit displeased with > btrfs performance recently myself, so, I''m wondering if you should

Hi Ady, Would it work if we removed "ifdef EFI_BUILD" condition and just add -mno-red-zone for all x86_64 builds? If not, do you have any ideas how to pass this flag? This could work, because the patch is adding the -mno-red-zone flag only for x86_64 builds, which are only used in the form of the efi64 target. The efi32 and bios targets are both 32-bit. BTW. I also tried 6.04-pre1 and

From: Sylvain Gault <sylvain.gault at gmail.com> The System V ABI for x86-64 specify that a "red zone" is an area of 128 bytes above the current stack frame. This area can be used by a called function in order to avoid the overhead of modifying the stack pointer. The direct effect is that interrupt/event/signal handlers must not write to this area. In the UEFI calling convention,

The following threads suggest that the way to reclaim memory occupied by initramfs is to remove files from it: http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&frame=right&th=c6cb846bba1a7aea&seekm=SAUO.51B.21%40gated-at.bofh.it#link1 http://seclists.org/lists/linux-kernel/2003/Dec/0707.html However, there is no way to do it using utilities provided by klibs. Could you

The "kinit" program distributed with klibc 0.153 still attempts to do a pivot_root. That doesn't work. The correct way of going into the main system is to mount --bind the root and chroot there, as done in the "run-init" program. Could you please copy that logic into "kinit"? And please fix the comment at the top - there is "/init", not

On 2020-07-27 19:20, hpa at zytor.com wrote: > > I'm not so sure they have dealt with it in the sense of having it work on all architectures. *Most* of the problems are related to the shifting the arguments by one, which can cause a bunch of problems, especially if it means the arguments spill to memory. However, I have absolutely no idea how to correctly implement syscall(3) on s390

hello, all. here is my implementation of printf for use in syslinux core. #include <stdio.h> #include <unistd.h> #define BUF_SIZE 1024 char buf[BUF_SIZE]; extern void myputs(const char *); int printf(const char *format, ...) { va_list ap; int rv; #if 1 myputs("DEBUG:the string we want fomart is\n\r"); myputs(format); #endif va_start(ap, format);

Thank you all. It looks like -mno-red-zone flag is already in master branch since commit 7d70885d, but it seems it is applied to all EFI builds. IIUC, the problem only affects efi64 builds. So here's the modification of my patch to only apply -mno-red-zone flag to efi64 target. The patch is against master. I verified that it builds correctly in master. Please feel free to accept or reject

I have set up a Samba 3.0.7 server (with LDAP password database), and it works perfectly for Windows clients. Now we came to the need of supporting one Linux workstation (with SAMBA 3.0.7 client already installed) in addition to those Windows PCs. Kernel is 2.6.7 on both the client and the server. The problem is the home directories. Usually (without SAMBA) I just share them via NFS in such

I get this with current linus bk now and klibc 187 [jonsmirl@smirl ash]$ make sh mknodes.sh nodetypes nodes.c.pat . gcc -Wp,-MD,.cd.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bits32 -I../include -I../linux/include -I../linux/include2 -I../linux/include