drive-trust-alliance / syslinux Goto Github PK

I get the following error, while running:

$ make
...
make[4]: Entering directory '/home/july/msed/syslinux/gpxe/src' [BUILD] bin/int13.o arch/i386/interface/pcbios/int13.c: In function ‘register_int13_drive’: arch/i386/interface/pcbios/int13.c:469:2: warning: asm operand 0 probably doesn’t match constraints __asm__ __volatile__ ( ^ arch/i386/interface/pcbios/int13.c:469:2: error: impossible constraint in ‘asm’ bin/deps/arch/i386/interface/pcbios/int13.c.d:86: recipe for target 'bin/int13.o' failed make[4]: *** [bin/int13.o] Error 1

My build env is:
$ nasm -v
NASM version 2.11.08 compiled on Mar 24 2015

$ gcc -v
Using built-in specs.

COLLECT_GCC=/usr/bin/gcc

COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/5.3.0/lto-wrapper

Target: x86_64-unknown-linux-gnu

Configured with: /build/gcc-multilib/src/gcc-5.3.0/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --enable-libmpx --with-system-zlib --with-isl --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object --enable-linker-build-id --enable-lto --enable-plugin --enable-install-libiberty --with-linker-hash-style=gnu --enable-gnu-indirect-function --enable-multilib --disable-werror --enable-checking=release

Thread model: posix

gcc version 5.3.0 (GCC)

$ make -v

GNU Make 4.1

Built for x86_64-unknown-linux-gnu

$ uname -a

Linux stoffle 4.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux

I'm running Arch Linux, so all the tools are the latest versions of respective tools.

I'm not an expert of asm constraints, but I did a couple of changes in order to complete the make process (see the patch file). I assume, those changes might be wrong (EDIT: are wrong - see my next comment).
asm_constraints.patch.zip

Regards,
Julian

Howdy. I've just "turned on" encryption via msed on my Crucial MX200 500GB drive. I set it up with the instructions here: http://vxlabs.com/2012/12/22/ssds-with-usable-built-in-hardware-based-full-disk-encryption/ . However, I seem to be getting denied with my password, but the output is ambiguous (see attached screenshot):

Does this response from OPAL tell me that the passphrase as given was incorrect, or that the PBA cannot actually talk to my drive's firmware to give it the passphrase?

Thanks!

Howdy. I'm working on packaging msed (and, therefore, 'syslinux') for Gentoo. It's a bit easier on us if you create a tagged release of the 'syslinux' package so that some of our automagic versioned downloads can work. As an example, we have built-in constructs in Portage like so:

https://github.com/Drive-Trust-Alliance/sedutil/releases/download/${P}.tar.gz

Where ${P} is the version of the release. I'd like to do something similar for the PBA Syslinux stuffs, and, us being Gentoo, we of course prefer to compile it. :)

Thanks! Please let me know if I've left out important details.