search for: sdi

...he latest Git my build fails which gcc-7 (see attached file for details). Do I really need to build clang-from-git? I have llvm-7/clang-7 binaries installed on my system? But I run the test after symlinking clang-7 ---> clang... $ ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/config.py:334: note: using clang: /usr/bin/clang llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/subst.py:126: note: Did not find c-index-test in /home/sdi/src/llvm/build/./bin:/home/sdi/src/llvm/build/./bin llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/...

...(see > attached file for details). > Do I really need to build clang-from-git? > I have llvm-7/clang-7 binaries installed on my system? > > But I run the test after symlinking clang-7 ---> clang... > > $ ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c > llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/config.py:334: > note: using clang: /usr/bin/clang > llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/subst.py:126: > note: Did not find c-index-test in > /home/sdi/src/llvm/build/./bin:/home/sdi/src/llvm/build/./bin > llvm-lit: /home/sdi/src/llvm...

Hi, As I have not seen any confirmation yet on the list, I just wanted to let you know that sdi.c32 works fine here, at least as fine as my initial syslinux-2.11 asm patch. I only use XPe SDI images with the following structure (of course PART blob size can vary): Type Offset Size Base Address Attr ---- ------------------- ------------------- -------------...

...-7 (see > attached file for details). > Do I really need to build clang-from-git? > I have llvm-7/clang-7 binaries installed on my system? > > But I run the test after symlinking clang-7 ---> clang... > > $ ./bin/llvm-lit -v ./tools/clang/test/Sema/asm.c > llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/config.py:334: > note: using clang: /usr/bin/clang > llvm-lit: /home/sdi/src/llvm/llvm/utils/lit/lit/llvm/subst.py:126: > note: Did not find c-index-test in > /home/sdi/src/llvm/build/./bin:/home/sdi/src/llvm/build/./bin > llvm-lit: /home/sdi/src/llvm...

...py -sv > --param=build_mode=Win32 --param=build_config=Debug > --param=clang_site_config=C:\Tools\build\tools\clang\test\lit.site.cfg > C:\Tools\llvm\tools\clang\test\Sema\wchar.c > > I transformed this... > > $ python /usr/lib/llvm-7/build/utils/lit/lit.py -sv > /home/sdi/src/linux-kernel/clang/test/Sema/asm.c > lit.py: /usr/lib/llvm-7/build/utils/lit/lit/TestingConfig.py:101: > fatal: unable to parse config file > '/home/sdi/src/linux-kernel/clang/test/lit.cfg.py', traceback: > Traceback (most recent call last): > File "/usr/lib/llvm-7...

...python C:\Tools\llvm\utils\lit\lit.py -sv --param=build_mode=Win32 --param=build_config=Debug --param=clang_site_config=C:\Tools\build\tools\clang\test\lit.site.cfg C:\Tools\llvm\tools\clang\test\Sema\wchar.c I transformed this... $ python /usr/lib/llvm-7/build/utils/lit/lit.py -sv /home/sdi/src/linux-kernel/clang/test/Sema/asm.c lit.py: /usr/lib/llvm-7/build/utils/lit/lit/TestingConfig.py:101: fatal: unable to parse config file '/home/sdi/src/linux-kernel/clang/test/lit.cfg.py', traceback: Traceback (most recent call last): File "/usr/lib/llvm-7/build/utils/lit/lit/Test...

Hi I did a google search on this and came up with nothing. OK, in the latest release of R for windows, I want to change the gui to SDI mode. Edit -> GUI preferences Choose SDI Apply I get the message about properties not being able to be changed on a running console, and that I need to save. So I click Save, and am met with a "Save As" dialogue box with the default file called Rconsole, the file type as "All...

R gurus: I'm trying to get another round of rconifers out and I need some advice/help crushing differences in the examples test. I'm trying to make sure the max sdi values are being respected. I've added a tests/rconifers-Ex.Rout.save (from windows i386-pc-mingw32) and when I ran R CMD check (both R-2.13.0), I got the following results: * using log directory 'c:/conifers/trunk/rconifers.Rcheck' * using R version 2.13.0 (2011-04-13) * using platf...

I have tackled a major bug that affected sdi.c32 especially, but might at least theoretically have affected other formats as well. It *appears* to load the SDI image I managed to stitch together with XP Embedded Studio, but it doesn't actually boot neither on my system nor in simulation; then trying to upgrade it to SP2 caused it to...

Hi, I added support in pxelinux for SDI (Wndows XP embedded images) files a few time ago for specific needs. It works well (at least for me atm) and I think I can now submit it to this list. I get a very good improvement in speed over the traditional way of loading SDI images. * Links : The 'diff -urN' patch for syslinux-2.11...

...les/LLVMBitReader.dir/MetadataLoader.cpp.o >>>>>> /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE >>>>>> -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS >>>>>> -Ilib/Bitcode/Reader >>>>>> -I/home/sdi/src/llvm-toolchain/llvm/lib/Bitcode/Reader -Iinclude >>>>>> -I/home/sdi/src/llvm-toolchain/llvm/include -fPIC >>>>>> -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wextra >>>>>> -Wno-unused-parameter -Wwrite-strings -Wcast-qual...

..._Name: Rob Cranfill Version: 2.8.1 OS: Windows XP SP2 Submission from: (NULL) (130.76.32.19) Using the Windows installer for 2.8.1, partway through the process there is a dialog that looks something like this: ---------------------------------------------- Display Mode Do you prefer the MDI or SDI interface? ------- Please specify MDI or SDI, then click Next. (*) MDI (one big window) ( ) SDI (separate windows) ---------------------------------------------- Those descriptions are reversed: "MDI" is Multiple Document Interface, with separate windows; SDI is Single Document...

...or this in my build-script? > > From your other email, when the compiler crashed, ninja printed the invocation: > > /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE > -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS > -Ilib/Bitcode/Reader > -I/home/sdi/src/llvm-toolchain/llvm/lib/Bitcode/Reader -Iinclude > -I/home/sdi/src/llvm-toolchain/llvm/include -fPIC > -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wextra > -Wno-unused-parameter -Wwrite-strings -Wcast-qual > -Wno-missing-field-initializers -pedantic -Wno-long-lon...

...ce at all that this array will pull through with most or all of my data. Background info about the machine /dev/md0 is a RAID1 consisting of /dev/sda1 and /dev/sda2 /dev/md1 is a RAID1 consisting of /dev/sda2 and /dev/sdb2 /dev/md2 (our special friend) is a RAID5 consisting of /dev/sd[c-j] /dev/sdi and /dev/sdj were the drives that detached from the array and were marked as faulty. I did the following things that in hindsight were probably VERY BAD Step 1 (Misassign drives to wrong array): I could probably have had things going again in a tenth of a second if I hadn't typed this: md...

...sel of rPath (with a great test case); it appears that deleted files can confuse extlinux so that it misses files. This is bad. As a result, I have pushed out 3.63-pre3, and intend to make a 3.63 final shortly. I would appreciate any help testing this. Furthermore, I would like to finish the SDI booting module, but I have yet to receive a SDI file from anyone to test with. I probably won't have time to experiment with the XP embedded trial edition, so I would appreciate any help. -hpa

If someone could try it out and let me know if it works, I would appreciate it... (also, if someone can actually send me an .sdi image, for testing only, I would also appreciate it...) http://www.zytor.com/~hpa/syslinux/0001-COM32-module-to-load-a-Microsoft-System-Deployment-I.patch -hpa

.../Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o FAILED: lib/Bitcode/Reader/CMakeFiles/LLVMBitReader.dir/MetadataLoader.cpp.o /usr/bin/g++-8 -DGTEST_HAS_RTTI=0 -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Bitcode/Reader -I/home/sdi/src/llvm-toolchain/llvm/lib/Bitcode/Reader -Iinclude -I/home/sdi/src/llvm-toolchain/llvm/include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wno-missing-field-initializers -pedantic -Wno-long-long -Wno-maybe-uniniti...

CORE SDI http://www.core-sdi.com SSH1 CRC-32 compensation attack detector vulnerability Date Published: 2001-02-08 Advisory ID: CORE-20010207 Bugtraq ID: 2347 CVE CAN: CAN-2001-0144 Title: SSH1 CRC-32 compensation attack detector vulnerability Class: Bou...

...MENU LABEL WinPE MENU INDENT 3 COM32 pxechn.c32 APPEND http://192.168.1.100/undionly.kpxe And then in the same location, I put this boot.ipxe file and all support files: #!ipxe kernel wimboot initrd bootmgr bootmgr initrd boot/bcd BCD initrd boot/boot.sdi boot.sdi initrd http://<SCCM-server>/boot.wim boot.wim imgstat boot Is that all correct? Spike

...168.1.100/undionly.kpxe undionly.kpxe will likely be BIOS-only also. > And then in the same location, I put this boot.ipxe file and all support > files: > > #!ipxe > kernel wimboot > initrd bootmgr bootmgr > initrd boot/bcd BCD > initrd boot/boot.sdi boot.sdi > initrd http://<SCCM-server>/boot.wim boot.wim > imgstat > boot Likely if you transform the above to Syslinux format. LABEL wimboot LINUX wimboot APPEND initrd=bootmgr,boot/bcd,boot/boot.sdi,http://<sccm-server>/boot.wim -- -Gene