similar to: syslinux and nasm tester

> Hello Ady, > > On Fri, Aug 01, 2014 at 08:35:27PM +0300, Ady wrote: > > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > > (with an optional Syslinux menu containing multiple entries). > > > > Problem (solved) #1: The default directory location for both > > syslinux.efi is the same. > > > > Solution #1: Rename each

Op 2014-08-01 om 20:35 schreef Ady: > Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 > (with an optional Syslinux menu containing multiple entries). What I would like to have is the same thing for network boot. So having one topdirectory on the TFTP server that can serve several "architectures". > Problem (solved) #1: The default directory location for

Despite being documented as the place for submitting bug reports and patches, it seems like the sf.net bug tracker isn't get much attention, so here it is: http://sourceforge.net/p/flac/bugs/400/ During x86-windows builds using mingw or mingw-w64, nasm complains: nasm.h:83: warning: COFF section names limited to 8 characters: truncating I think the section .note.GNU-stack stuff aren't

Hi, Matt Fleming wrote: > On Tue, 25 Jun, at 01:52:00PM, Helmut Hullen wrote: >> Thanks - now it crashes later ... > > What crash are you seeing? > >> I don't have the ia64 files which are needed for a complete binary. But >> maybe that's only my special problem. > > You shouldn't need ia64 files to build ia32 and x86-64 versions of > gnu-efi or

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 CentOS Errata and Security Advisory CESA-2005:381 https://rhn.redhat.com/errata/RHSA-2005-381.html The following updated files have been uploaded and are currently syncing to the mirrors: i386: nasm-0.98.38-3.EL4.i386.rpm nasm-rdoff-0.98.38-3.EL4.i386.rpm nasm-doc-0.98.38-3.EL4.i386.rpm x86_64: nasm-0.98.38-3.EL4.x86_64.rpm

Goal: To have one USB drive capable of booting UEFI IA32 and UEFI X64 (with an optional Syslinux menu containing multiple entries). Problem (solved) #1: The default directory location for both syslinux.efi is the same. Solution #1: Rename each syslinux.efi to bootx64.efi and to bootia32.efi. Problem (solved) #2: Each syslinux.efi needs at least its respective ldlinux module. Solution #2:

CentOS Errata and Security Advisory CESA-2005:381 https://rhn.redhat.com/errata/RHSA-2005-381.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/nasm-0.98.35-3.EL3.s390.rpm updates/s390/RPMS/nasm-doc-0.98.35-3.EL3.s390.rpm updates/s390/RPMS/nasm-rdoff-0.98.35-3.EL3.s390.rpm s390x:

CentOS Errata and Security Advisory 2005:381 nasm security update for CentOS 3 i386: https://rhn.redhat.com/errata/RHSA-2005-381.html The following updated file has been uploaded and is currently syncing to the mirrors: i386: updates/i386/RPMS/nasm-0.98.35-3.EL3.i386.rpm addons/i386/RPMS/nasm-doc-0.98.35-3.EL3.i386.rpm addons/i386/RPMS/nasm-rdoff-0.98.35-3.EL3.i386.rpm source:

CentOS Errata and Security Advisory 2005:381 nasm security update for CentOS 3 x86_64: https://rhn.redhat.com/errata/RHSA-2005-381.html The following updated file has been uploaded and is currently syncing to the mirrors: x86_64: updates/x86_64/RPMS/nasm-0.98.35-3.EL3.x86_64.rpm addons/x86_64/RPMS/nasm-doc-0.98.35-3.EL3.x86_64.rpm addons/x86_64/RPMS/nasm-rdoff-0.98.35-3.EL3.x86_64.rpm source:

Hi folks, here's a patch which cleans up the nasm call from Makefiles. Abusing libtool and then having to drop in some additional wrapper script to rewrite the commandline again is rather stupid. cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/

Hi, trying to build syslinux on Linux. Please help. bash-2.05b$ uname -a Linux bongo 2.4.32-ARXc3 COHERENT #4-ARX (Build 2660) Sun May 21 15:35:22 CEST 2006 i686 i686 i386 GNU/Linux bash-2.05b$ BUILD/syslinux-3.11/opt/nasm-0.98.38-2/bin/nasm -version NASM version 0.98.38 compiled on Jun 26 2006 But failed with: + make NASM=/home/axel/p/rpm/BUILD/syslinux-3.11/opt/nasm/bin /nasm

They are not needed since the section is defined in nasm.h. --- src/libFLAC/ia32/bitreader_asm.nasm | 4 ---- src/libFLAC/ia32/cpu_asm.nasm | 4 ---- src/libFLAC/ia32/fixed_asm.nasm | 4 ---- src/libFLAC/ia32/lpc_asm.nasm | 4 ---- src/libFLAC/ia32/stream_encoder_asm.nasm | 4 ---- 5 files changed, 20 deletions(-) diff --git

where can I get the lastest nasm to compile syslinux 1.75. http://www.cryogen.com/Nasm is not accessible and the latest on ftp://ftp.kernel.org/pub/software/devel/nasm/source/ is nasm-0.98.tar.bz2 Thanks, Jeff [ jchua at fedex.com ]

> On Mon, 2005-07-11 at 19:24 +0100, Aaron Gray wrote: >> The NASM like the MASM does not have % symbols on the register names so >> will >> either inherit from the MASM printer or have its own TableGen class. > > Couldn't one conditionally output some macros for the assembler to > translate the reg names rather than having another .td file? or is '%'

On Mon, 11 Jul 2005, Aaron Gray wrote: >> On Mon, 2005-07-11 at 19:24 +0100, Aaron Gray wrote: >>> The NASM like the MASM does not have % symbols on the register names so >>> will >>> either inherit from the MASM printer or have its own TableGen class. >> >> Couldn't one conditionally output some macros for the assembler to >> translate the

The following errata for CentOS-2 have been built and uploaded to the centos mirror: RHSA-2005:381-01 Low: nasm security update Files available: nasm-0.98-8.EL21.i386.rpm nasm-doc-0.98-8.EL21.i386.rpm nasm-rdoff-0.98-8.EL21.i386.rpm More details are available from the RedHat web site at https://rhn.redhat.com/errata/rh21as-errata.html The easy way to make sure you are up to date with all the

Is Nasm always available when the target architecture is IA-32? For example, FLAC has FLAC__lpc_compute_autocorrelation_asm_ia32_sse_lag_NN() functions that require NASM presence, and FLAC__lpc_compute_autocorrelation_intrin_sse_lag_NN() functions that require x86 intrinsics support. FLAC makes use of the former (if NASM is available) but doesn't try to use the latter when NASM is not found.

>> I am not really sure whether to do a X86NASMPrinter or whether to bypass >> that for now and work on an X86COFFWriter which would be more useful to >> me ? > > I wouldn't suggest writing an X86NASMPrinter: just change the current > Intel printer to do what you want. Noone is currently using the intel > printer, so you can do what you wish to it. Once I

Could generated assembly with option "-x86-asm-symtab=intel" be assembled by nasm directly? On Thu, Jun 21, 2012 at 2:30 PM, Sean Silva <silvas at purdue.edu> wrote: > If by "NASM format" you mean Intel syntax, then yes. In my experience most > LLVM tools refer to it with the option "-x86-asm-syntax=intel". For > example, tools/llvm-objdump has this

CentOS Errata and Security Advisory CESA-2005:381 https://rhn.redhat.com/errata/RHSA-2005-381.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/nasm-0.98.38-3.EL4.ia64.rpm updates/ia64/RPMS/nasm-doc-0.98.38-3.EL4.ia64.rpm updates/ia64/RPMS/nasm-rdoff-0.98.38-3.EL4.ia64.rpm -- Pasi Pirhonen - upi@iki.fi -