From: | Karl DeBisschop <kdebisschop(at)alert(dot)infoplease(dot)com> |
---|---|
To: | lockhart(at)fourpalms(dot)org |
Cc: | thomas(at)pgsql(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Call for platforms |
Date: | 2001-03-22 19:43:27 |
Message-ID: | 3ABA55DF.B0E1E063@alert.infoplease.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
The Hermit Hacker wrote:
>
> On Thu, 22 Mar 2001, Thomas Lockhart wrote:
>
> > Solaris x86 7.0 2000-04-12, Marc Fournier
> >
> > scrappy, do you still have this machine?
>
> Doing tests on Solaris x86/7 right now, will report as soon as they are
> done ...
>
> > Solaris 2.5.1-2.7 Sparc 7.0 2000-04-12, Peter Eisentraut
> >
> > I'll bet that someone already has Solaris covered. Report?
>
> Will do up Sparc/7 also this morning ...
In my tests on sparc/7 my compile died at line 3088 of
postgresql-7.1beta6/src/interfaces/python/pgmodule.c:
./pgmodule.c:3088: parse error before `init_pg'
That's line 3137 of today's (22Mar) snapshot, which reads:
/* Initialization function for the module */
DL_EXPORT(void)
init_pg(void)
{
I'm not a C expert by any means, but I can't figure how that is valid.
Given my ignorance, I don't want to call it a bug. Plus we don't use the
python module in production, nor the sparc platform. But it seemed worth
pointing out.
--
Karl
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Corteen | 2001-03-22 19:45:41 | Re: Birthday comparisons |
Previous Message | Creager, Robert S | 2001-03-22 19:09:13 | RE: using NEW in a trigger calling a function in plpgsq l... |
From | Date | Subject | |
---|---|---|---|
Next Message | Giles Lean | 2001-03-22 19:45:02 | Re: Re: Call for platforms |
Previous Message | Steve Stock | 2001-03-22 19:30:52 | Re: initdb and data directories with lost+found |