Re: Postgres for Sunos 4.1.4

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: stevek(at)uimage(dot)com (Stephen Kogge)
Cc: hackers(at)postgreSQL(dot)org (PostgreSQL-development), dg(at)illustra(dot)com
Subject: Re: Postgres for Sunos 4.1.4
Date: 1998-11-16 03:10:57
Message-ID: 199811160310.WAA29221@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

OK, folks, I need help on this one. We use the new structure slock_t,
but it is not defined in all include/port/*.h files. It is missing in:

#$ ls *.h |diff - /tmp/x
< dgux.h
< sco.h
< sunos4.h
< ultrix4.h
< win32.h

If any of these ports tries to access the locking code, the compile will
fail, or is that wrong? I thought sco works, or is that unixware works?
sunos4 seems to require it, and doesn't have it.

Can someone knowledgeable about this area supply a patch?

>
> I decided to build the current on my 4.1.4 system. No luck - there is
> the usual missing def's for fprintf, printf... which are easy to list for
> a possible massive #include for sunsos builds - I can send you the list later.
> The main problem is in s_lock.c
>
> ....
> gcc -I../../../include -I../../../backend -Wall -Wmissing-prototypes
> -I../..
> -c s_lock.c -o s_lock.o
> s_lock.c:43: warning: type defaults to `int' in declaration of `slock_t'
> s_lock.c:43: parse error before `*'
> s_lock.c: In function `s_lock_stuck':
> s_lock.c:47: `lock' undeclared (first use in this function)
> s_lock.c:47: (Each undeclared identifier is reported only once
> s_lock.c:47: for each function it appears in.)
> s_lock.c:47: `file' undeclared (first use in this function)
> s_lock.c:47: `line' undeclared (first use in this function)
> s_lock.c: At top level:
> s_lock.c:60: warning: type defaults to `int' in declaration of `slock_t'
> s_lock.c:60: parse error before `*'
> s_lock.c:61: warning: no previous prototype for `s_lock'
> s_lock.c: In function `s_lock':
> s_lock.c:64: warning: implicit declaration of function `TAS'
> s_lock.c:64: `lock' undeclared (first use in this function)
> s_lock.c:74: `file' undeclared (first use in this function)
> s_lock.c:74: `line' undeclared (first use in this function)
> gmake[3]: *** [s_lock.o] Error 1
> ...
>
> which means that .o never is built and much later the entire build fails.
>
> Since you last checked out this file - I figured you might want to
> take a stab at it. I am open to suggestions before I try to puzzle it out.
>
> --
> Stephen N. Kogge
> stevek(at)uimage(dot)com
> http://www.uimage.com
>
>
>

--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-11-16 03:13:15 Re: [HACKERS] Concurrency control questions 6.3.2 vs. 6.4
Previous Message Taral 1998-11-16 03:02:34 SQL vs. OQL