From owner-freebsd-current Sun Mar 22 21:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA26265 for freebsd-current-outgoing; Sun, 22 Mar 1998 21:22:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (tc-35.acadiau.ca [131.162.2.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA26257 for ; Sun, 22 Mar 1998 21:22:44 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.2) with SMTP id BAA15566; Mon, 23 Mar 1998 01:22:11 -0400 (AST) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 23 Mar 1998 01:22:11 -0400 (AST) From: The Hermit Hacker To: Simon Shapiro cc: Andreas Klemm , current@FreeBSD.ORG Subject: RE: pgaccess doesn't run on -current anymore, possibly shared li In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 22 Mar 1998, Simon Shapiro wrote: > > On 22-Mar-98 Andreas Klemm wrote: > > Hi ! > > > > During my work on updating the postgresql port I stepped into > > a problem, that pgacces isn't able anymore, to load the postgresql > > .so files ... > > > > When I committed the postgresql 6.2.1 and pgaccess port months ago > > everything was fine with current. But now it fails. > > 6.3? Actually, 6.3.1 now...we're just about to put out a *post-release* patch based on some bugs that leaked through... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message