Still badness on FreeBSD/Alpha:
gcc -pipe -O -g -Wall -Wmissing-prototypes -Wmissing-declarations -fpic -DPI
C -I. -I../../../src/include -DFRONTEND -DSYSCONFDIR='"/home/chriskl/local/
etc/postgresql"' -c -o fe-secure.o fe-secure.c -MMD
fe-secure.c: In function `verify_peer':
fe-secure.c:417: structure has no member named `s6_addr8'
gmake[3]: *** [fe-secure.o] Error 1
gmake[3]: Leaving directory `/home/chriskl/pgsql-head/src/interfaces/libpq'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/home/chriskl/pgsql-head/src/interfaces'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/home/chriskl/pgsql-head/src'
gmake: *** [all] Error 2
Chris
> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org]On Behalf Of Bruce Momjian
> Sent: Monday, 17 June 2002 11:11 PM
> To: Tom Lane
> Cc: PostgreSQL-development
> Subject: Re: [HACKERS] Massive regression failures
>
>
> Tom Lane wrote:
> > Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > > I am seeing massive regression failures on a freshly
> compiled, initdb'ed
> > > version of CVS:
> >
> > That's because you broke the regression test data files.
>
> Wow, I had a corrupted CVS regression directory. I was seeing it during
> CVS update failure for the /regression directory, but I ignored it.
> Then I thought I saw a commit touching regression, which didn't make
> sense, but I closed the window too soon without investigating.
>
> Later, I deleted the directory and recreated it, but seems I had already
> accidentally modified those files. I don't see any other /regression
> changes except /data, so I backed out those changes. We should be OK
> now.
>
> > Kindly unbreak them ASAP. I had wanted to do a cvs update this
> morning...
>
> Fixed now.
>
> --
> Bruce Momjian | http://candle.pha.pa.us
> pgman@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
