similar to: syslinux-4.03-pre4 + MCONFIG.devel + gcc 4.5

hello hpa, please pull for the latest git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks with the following shortlog: maximilian attems (9): mount: add nodev, noexec and nosuid options mount: add -n option cpio: small cleanups readlink: s/link/link_name/ kinit, mknod: s/(major|minor)/\1_num/ klibc: strcspn, strpbrk, strspn include string.h

Trying to get at least my backlog of bug fixes out... I'm hoping to do a 4.03 next week. Please help by: a) giving it a whirl; b) letting me know if I have missed any low-risk bugfixes. Gene: I did not include your UI branch in this release, because it made me a bit nervous... poke me on IRC when you have a chance. -hpa

On Sun, Oct 23, 2011 at 10:34 PM, James Molloy wrote: > Hi, > > I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. > $ make happiness ... Updated to revision 142790. ... make[4]: Entering directory `/home/ecsardu/LLVM/build-tcclab1/tools/clang/tools/libclang' llvm[4]: Compiling

Commit-ID: 89742f0fc6f93a4a748ab783856a9d441511b808 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=89742f0fc6f93a4a748ab783856a9d441511b808 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sat, 28 Mar 2020 21:04:54 +0000 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:12 +0000 [klibc] Implement stpcpy() and

Hi All, i'm running blazer_usb on my home orvaldi ups and i'm observing in dmesg one, two or three segafults of blazer_usb per day and notifications about broken/re-established communication like this: blazer_usb[2985]: Communications with UPS lost: status read failed! blazer_usb[2985]: Communications with UPS re-established today i've started ups service again with attached (c)gdb

On Sat, Oct 22, 2011 at 12:24 AM, James Molloy wrote: > Hi Paul, > > That should be easy enough, because the LLVM build has no warnings in it! > > Some of us build with -Werror, and even with those of us that don't warnings are not tolerated. You're already seeing all the warnings that are coming out of the build :) So, all the "variable might be used

hello hpa, rebased my branch, please pull latest git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for the following shortlog maximilian attems (6): fstype: add squashfs v3 support reiser4_fs.h: add attribute packed to reiser4_master_sb fstype: add ext4 support .gitignore: add subdir specific entries usr/klibc/Kbuild: beautify klibc build fstype:

Options given on the command line have precedence over configuration from files. This can be useful, for example, for a roaming node, for which 'ConnectTo' and <host>.Address depends on its location. --- This patch is against stable branch. Merging this patch to the 1.1 branch is trivial. I use this patch on my Debian for several weeks. Here is the ifupdown script I use (some

Greetings, As previously reported by me to the Debian bug tracking system: ---------------------------------------------------------------------- An access list in rsyncd.conf may contain hostnames as well as addresses. It may contain several patterns to match against. address_match (in access.c) does this by trying to match hostname and address against each of the patterns until a match is

After upgrade via http://download.opensuse.org/repositories/Virtualization:/openSUSE11.3/openSUSE_11.3/src/xen-4.0.1_21326_01-1.1.src.rpm with any "kotd" or 2.6.34.4-2.2-xen VFB gets broken . It worked with original  Xen 4.0, no matter of  some additional patching to support ZFS 24 has been done and 4.0 src.rpm has been rebuilt to reinstall 4.0   In particular,  virt-install fails to

On Mon, Oct 24, 2011 at 10:07 AM, James Molloy wrote: > That's interesting, what version of GCC are you using? > As I said, gcc version 4.5.0 20100604 [gcc-4_5-branch revision 160292] (SUSE Linux) on openSUSE 11.3 "Teal" Also gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5) on Ubuntu 10.04 LTS -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The

Bryan O'Sullivan wrote: > Update of /home/cvs/klibc/klibc/klibc/arch/i386 > In directory terminus.zytor.com:/tmp/cvs-serv27981/klibc/arch/i386 > > Modified Files: > MCONFIG > Log Message: > Bring sanity to OPTFLAGS. Turn off -fomit-frame-pointer, which is worse > than useless, and use new names for other directives. > This unfortunately breaks older compilers.

Hi, I think I already know the answer to this and I agree with it, but I have a question about "invalid" mailbox naming decisions in dovecot. Technically, RFC3501 (Section 5.1, pg. 18, client consideration 3) says that * and % are legal in mailbox names, though it implicitly discourages their use. We just migrated to dovecot, and unfortunately have a few users who used * in their

I have just released SYSLINUX 2.09-pre4 with a few changes: a) SYSLINUX should now correctly handle mode changes from within a COMBOOT program. b) Tweaks to the menu system to avoid the "grey text on black" problem. c) A new color scheme for the menu system (Murali, check it out and see if you think it works for you.) ftp://ftp.kernel.org/pub/linux/utils/boot/syslinux/Testing/

Hi, I haven't seen those errors. Clang and LLVM both build with no warnings on the 3 versions of GCC I test with. MSVC reports loads of warnings however. Cheers, James ________________________________________ From: Csaba Raduly [rcsaba at gmail.com] Sent: 23 October 2011 18:44 To: James Molloy Cc: Paul Berube; llvmdev at cs.uiuc.edu Subject: Re: [LLVMdev] build warnings On Sat, Oct 22,

On 09/08/2018 03:15 AM, Richard W.M. Jones wrote: > Previously key=value on the command line allowed the key to be pretty > much anything that didn't contain an '=' character. Even empty > strings were permitted. > > This tightens up the permitted keys so they must contain only ASCII > alphanumeric, period, underscore or dash characters, and must not be > an

Hi all, I have pushed out Syslinux 3.81-pre4, which is now a release candidate for 3.81. This version includes halt on idle, and so I'm very keen on getting this tested. -hpa

Hi all, I have pushed out a SYSLINUX 3.32-pre4. This version attempts to work around the "missing floppy drive" issue. If you have systems on which MEMDISK doesn't work without a floppy drive, I would appreciate it if you would test this out. -hpa

Yet another test release for the rewrite in progress. This version generalizes the definition of a boot sector, and puts the boot sector code into all the modules, so that a CD-ROM "boot sector" (like WinNT uses) and a PXE NBP should now all be possible to chainload. PLEASE test it out, pretty please... I haven't heard anything from anyone since at least 1.73-pre2.

hi i'm about to upgrade systems. yesterday i got https://www.zytor.com/pub/syslinux/Testing/6.04/syslinux-6.04-pre3.tar.xz in order to upgrade 6.04-pre1 version. i first was upgrading a usb-disk which was booting smootly with a simple configuration. i changed the EFI installation in /EFI/BOOT: efi64/efi/syslinux.efi (UEFI bootloader for EFI X64 (x86_64) firmware) ?