search for: libflags

When we add -ffreestanding the compiler won't get to inline this any more. Signed-off-by: David Woodhouse <dwmw2 at infradead.org> --- com32/lib/math/fabs.S | 15 +++++++++++++++ mk/lib.mk | 2 +- 2 files changed, 16 insertions(+), 1 deletion(-) create mode 100644 com32/lib/math/fabs.S diff --git a/com32/lib/math/fabs.S b/com32/lib/math/fabs.S new file mode 100644 index

Hi, Bartlett I decided to cut some subsystem by myself, So I spent several days to study the SAMBA 4 WAF build system and now know the base steps of build. but which subsystem can be removed for snmd/nmbd/smbpasswd ? followings are the full dependencies of these 3 binary ldd bin/smbpasswd libpthread.so.0 => /lib/libpthread.so.0 (0xf7139000) libsamba-util.so.0 =>

...@ endif ifeq ($(ARCH),x86_64) GCCOPT += $(call gcc_ok,-m64,) +ifeq ($(FWCLASS),EFI) + GCCOPT += $(call gcc_ok,-mno-red-zone) +endif #let preferred-stack-boundary be default(=4) MARCH = x86-64 endif @@ -54,9 +57,7 @@ CFLAGS = $(OPTFLAGS) $(REQFLAGS) $(WARNFLAGS) $(LIBFLAGS) -ifeq ($(FWCLASS),EFI) -CFLAGS += -mno-red-zone -else +ifneq ($(FWCLASS),EFI) CFLAGS += -mregparm=3 -DREGPARM=3 endif

On 10/5/2020 11:58 AM, Rowland penny via samba wrote: > On 05/10/2020 16:30, Jason Keltz via samba wrote: >> Hi. >> >> Using MIT5 backend with Samba.. > I hope you mean on the clients, the use of MIT as the kdc on a Samba > DC is experimental and shouldn't be used in production Hi Roland, our environment uses CentOS 7.? I don't have much choice but to use this

On 10/5/2020 12:16 PM, Rowland penny via samba wrote: > On 05/10/2020 17:01, Jason Keltz via samba wrote: >> On 10/5/2020 11:58 AM, Rowland penny via samba wrote: >> >>> On 05/10/2020 16:30, Jason Keltz via samba wrote: >>>> Hi. >>>> >>>> Using MIT5 backend with Samba.. >>> I hope you mean on the clients, the use of MIT as the

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

...jdir/include/efi/$ARCH/efibind.h" -a -f "$objdir/lib/libefi.a" exit 1 fi + popd >/dev/null else printf "skip gnu-efi build/install\n" fi diff --git a/mk/lib.mk b/mk/lib.mk index ceb95bd..f00dd94 100644 --- a/mk/lib.mk +++ b/mk/lib.mk @@ -38,6 +38,31 @@ LIBFLAGS = -DDYNAMIC_CRC_TABLE -DPNG_NO_CONSOLE_IO \ -DPNG_NO_MNG_FEATURES \ -DPNG_NO_READ_tIME -DPNG_NO_WRITE_tIME +ifdef EFI_BUILD + +ifeq ($(ARCH),i386) + ARCHOPT = -m32 -march=i386 + EFI_SUBARCH = ia32 +endif +ifeq ($(ARCH),x86_64) + ARCHOPT = -m64 -march=x86-64 + EFI_SUBARCH = $(ARCH) +endi...

Hi, These patches contain support for some features that are already in Syslinux 4 but weren't working properly on the elflink branch. It's another step closer to feature parity with Syslinux 4. Having to jump through the comboot API for localboot support is less than ideal and I'll eventually fix that, probably when we move a big chunk of code from asm to C. Also, there's a

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,

Hello everybody, Could someone give me an estimate on when the repositories are resolving the right dependencies for the freeipa pacakges in CentOS Stream release 8? I have about +10 systems sending me alerts everyday that dnf-automatic.service is failing because of the freeipa dependency issues. Since freeipa is one of the security elements I would like to give people an estimate on when

From: Matt Fleming <matt.fleming at intel.com> The following patch series is available at, git://git.zytor.com/users/mfleming/syslinux.git elflink All patches are against the 'elflink' branch. This series fixes a few serious bugs and some behavioural incompatibilities with the 4.x series. Matt Fleming (19): ldlinux: Initialise 'p' before using it. ldlinux: Parse

it's not very helpful when the process exists without any output [root at srv-rhsoft:~]$ /usr/sbin/smbd -D [root at srv-rhsoft:~]$ /usr/sbin/smbd --foreground [root at srv-rhsoft:~]$ ps aux | grep smb root 8877 0.0 0.0 10904 960 pts/1 S<+ 15:04 0:00 /usr/bin/grep --color smb [root at srv-rhsoft:~]$ rpm -qa | grep samba samba-libs-4.7.4-2.fc27.x86_64

From: Matt Fleming <matt.fleming at linux.intel.com> This series fixes some bugs and switches the elflink branch to be entirely ELF modules. It applies on top of, http://syslinux.zytor.com/archives/2011-April/016369.html The deletions in the diff stat below are mainly from deleting com32/elflink/modules (finally!). Now there should be no duplicate code because we don't need COM32 and