search for: delori

Sorry, spoke too quickly! The problem was caused by my editing the MkRules file with an editor that replaces tabs with spaces. Make evidently requires that all lines start with a tab (see http://www.delorie.com/djgpp/v2faq/faq22_17.html). Perhaps worth warning windoze users like myself of such perils in readme.packages or somewhere similar! Now I have a new problem, but it looks fixable. Thanks for your attention. Drew Drew Tyre CSIRO Marine Research, PO Box 120 Cleveland, QLD, 4163, Australia...

...and position-independent code and intermittent failures when DLL relocations "collide"... but I really don't want to have to worry about that. Kevin (a couple interesting links ab't enable-auto-import): [1] http://sourceware.org/binutils/docs-2.16/ld/WIN32.html [2] http://www.delorie.com/gnu/docs/binutils/ld_4.html -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20111203/ed514f3e/attachment.html>

Hi, I have just upgraded to LLVM 3.0 (nice job btw!) which I have built as a shared library on Windows using MinGW, and then use from within my Qt-based application. Upon execution, everything works perfectly (incl. the call to llvm::InitializeNativeTarget(); which used to cause problems upon exiting my application; see http://lists.cs.uiuc.edu/pipermail/llvmdev/2011-November/045597.html; in

...ct callback to free > the line? (and if it does, can it be bug in the specific readline > version you are using?) > - ML A cursory look suggests Elmo is right. That you should free the returned line is explicitly mentioned when using the readline() call: http://www.delorie.com/gnu/docs/readline/rlman_24.html#IDX174 No further mention at the reference for the alternative interface: http://www.delorie.com/gnu/docs/readline/rlman_41.html#IDX288 When I added 'free(line)' to src/unix/sys-std.c:readline_handler() valgrind stopped complaining about the leaks...

Hello SYSLINUX, I have been searching for a resource for the "Disk error" messages coming out of isolinux. I am seeing the message "isolinux: Disk error 20, AX=425 c, drive EF" on many occasions where a combination of questionable Linux OS media comes in contact with touchy LITE-ON DVD/RW Drives attempting to load Red Hat Linux. We know that changing the Drive or

Does samba have an equivalent setting as the WINDOZE NameNumericTail setting? For those who don't know about this registry setting, <http://www.delorie.com/djgpp/v2faq/faq22_19.html> can be enlightening. If not are there any plans to implement it? If not would such an implementation be welcome? Right, MartinS

Hi all I'm guessing this is a little off topic but here goes... We use PXELINUX and kickstart to automate our RHEL deployments and updates. Recently we started using PXELINUX/memdisk and an MS-DOS image to update the workstation BIOS'es. After selecting <F12> (network boot) and picking the update BIOS option, the BIOS is flashed, BIOS configuration made standard and then the

Hi all. I once tried to rsync around 100 GB (10 million files), but version 2.6.6 needed too much RAM and was too slow. Is one of the snapshots stable enough to try this again? Greetings Sven -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url :

...ch-O symbol tables have similar fields. The main differences are that Mach-O symbol table entries don’t contain the symbol size, so the size is deduced by looking for the next symbol start address, and COFF holds the symbol sizes in auxiliary info that follows each symbol entry. See also http://www.delorie.com/djgpp/doc/coff/symtab.html and https://developer.apple.com/library/mac/documentation/DeveloperTools/Conceptual/MachORuntime/index.html#//apple_ref/c/tag/nlist_64 -- Teresa Johnson | Software Engineer | tejohnson at google.com | 408-460-2413 -------------- next part -------------- An HTML att...

...ave similar fields. The main > differences are that Mach-O symbol table entries don’t contain the symbol > size, so the size is deduced by looking for the next symbol start address, > and COFF holds the symbol sizes in auxiliary info that follows each symbol > entry. See also http://www.delorie.com/djgpp/doc/coff/symtab.html > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.delorie.com_djgpp_doc_coff_symtab.html&d=AwMFaQ&c=8hUWFZcy2Z-Za5rBPlktOQ&r=Mfk2qtn1LTDThVkh6-oGglNfMADXfJdty4_bhmuhMHA&m=oUy_PB_mSfRgDO7H7bZOR04gv_DMzX5rPO_lv4PHt60&s=7isNRRG84wFLU9z...

...-tree aaca1deef82d3d2545b77919455d044c79b2ca11 (from f01c9464494628c60a9b4bd49dde7b612a340489) Author: Benjamin Otte <otte at gnome.org> Date: Fri Jul 20 01:12:54 2007 +0100 use -std=gnu99 gnu99 will be the default gcc std flag, when c99 support is complete. See http://www.delorie.com/gnu/docs/gcc/gcc_2.html for details. diff --git a/configure.ac b/configure.ac index 6d46ee8..79461a2 100644 --- a/configure.ac +++ b/configure.ac @@ -38,7 +38,7 @@ AC_SUBST(SWFDEC_LIBVERSION) AM_PROG_LIBTOOL dnl C99 is only required to get definitions for NAN and INFINITY. -GLOBAL_CFLAGS=...