Re: bootstrapping gnat GCC on amd64

Hi. After a week off, another update: I've realised, too late, that I'm using a version of binutils (2.19) that's incompatible with the system binutils (2.15). Specifically, assembler code emitted by the native GNAT contains .cfi_personality directives (and no doubt other things too) that can't

Re: bootstrapping gnat GCC on amd64

On 2009-05-18 09:48:31, xorquew...@googlemail.com wrote: 1. Compile binutils-2.15. Unfortunately, compiling these as cross-binutils appear to be problematic: gmake[3]: Entering directory `/root/memfs/c1-bu-obj/gas' gcc -DHAVE_CONFIG_H -I. -I/root/binutils-2.15/gas -I. -D_GNU_SOURCE

porting info for FreeBSD's kernel?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I've been googling, trying to see if I can find notes regarding what needs changing, in what order, to adapt the FreeBSD kernel to a new processor. Anyone know where stuff like that can be found? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9

Re: bootstrapping gnat GCC on amd64

On Mon, 18 May 2009, xorquew...@googlemail.com wrote: Hi. After a week off, another update: I've realised, too late, that I'm using a version of binutils (2.19) that's incompatible with the system binutils (2.15). Specifically, assembler code emitted by the native GNAT contains

sshd(8) - alert user when fails to execute from rc.d

Good evening, hackers. Earlier this evening, I submitted a PR about sshd(8) giving a false-positive when starting on an already occupied socket[1]. I would like to enable some form of console output when the rc.d script is called if the service cannot properly bind to the socket, but I want to