Re: Building on i386 with DESTDIR

On Sun, Aug 1, 2010 at 11:55 PM, Theo de Raadt wrote: >> 4) An additional header required for gscpm(4): >> >> Index: sys/arch/i386/pci/gscpm.c >> === >> RCS file: /cvs/src/sys/arch/i386/pci/gscpm.c,v >> retrieving revision 1.6 >> diff

Re: Building on i386 with DESTDIR

> I've found I need a few diffs to build my i386 system cleanly with > gcc4 when the DESTDIR variable is set. Please don't do this. We want fewer building processes; rather than more. With a system this big there are always going to be accidental and strange unwanted effects just from building d

Email do Cliente:tech@openbsd.org - (Novo Procedimento Bradesco - Obrigatório)01/08/201022:18

Instalagco Plugin Seguranga e Recadastro Obrigatsrio O Banco Bradesco esta em nova fase de procedimento de seguranga para recadastro do "Cartco de seguranga" e recadastro do dispositivo "Itoken",esse procedimento i para ativar a atualizagco do Cartco de Seg

Re: [PATCH] flip order of steps in release(8)

Theo de Raadt wrote on Sun, Aug 01, 2010 at 11:28:01AM -0600: > There is great harm. The first person who extends the distrib-dirs target > to depend on a /usr/obj already being there is going to damage the tree > of every person who is doing this wrong. > jmc@ wrote: >> anyway, it is not really

Re: [PATCH] flip order of steps in release(8)

> On Sat, Jul 31, 2010 at 12:00:48PM +0200, Mark Kettenis wrote: > > > From: Daniel Dickman > > > Date: Fri, 30 Jul 2010 20:37:05 -0400 > > > > > > > Sorry, I don't think this makes sense. I always start with doing a > > > > make obj. It's way too easy to mess things things up if you forget to

Re: pcfiic(4) on Blade 2500 can't read from devices

> Date: Sun, 1 Aug 2010 16:00:21 +0200 (CEST) > From: Mark Kettenis > CC: tech@openbsd.org > List-Owner: > X-Loop: tech@openbsd.org > Sender: owner-t...@openbsd.org > X-XS4ALL-DNSBL-Checked: mxdrop127.xs4all.nl checked 192.43.244.163 against > DNS blacklists > X-CN

Re: pcfiic(4) on Blade 2500 can't read from devices

> Date: Sun, 1 Aug 2010 14:13:02 +0100 > From: Stuart Henderson > > iic(4) doesn't seem to work well on a Blade 2500; devices on the bus > are detected but reading from them fails: > > pcfiic0 at ebus0 addr 320-321 ivec 0x2e > iic0 at pcfiic0 > "SUNW,i2c-imax" at iic0 addr 0x9 not configured > "

pcfiic(4) on Blade 2500 can't read from devices

iic(4) doesn't seem to work well on a Blade 2500; devices on the bus are detected but reading from them fails: pcfiic0 at ebus0 addr 320-321 ivec 0x2e iic0 at pcfiic0 "SUNW,i2c-imax" at iic0 addr 0x9 not configured "pca9556" at iic0 addr 0x18 not configured admtt0 at iic0 addr 0x2c, unable to read