From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alexander Klimov <ask(at)wisdom(dot)weizmann(dot)ac(dot)il>, thomas(at)pgsql(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Re: Call for platforms |
Date: | 2001-03-26 16:18:33 |
Message-ID: | 3ABF6BD9.B16E9DAE@alumni.caltech.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
> >> Suddenly I obtain access to
> >> ULTRIX black 4.3 1 RISC
> > Uh ... what kind of processor is that? Offhand I don't see any
> > indication that any of the entries in s_lock.h are supposed to work
> > for Ultrix.
As mentioned earlier, Ultrix on RISC means that it is a MIPS processor.
DEC implemented OSF-1 for their Alpha processors.
> I suspect that some one of the implementations in s_lock.h was intended
> to be usable on Ultrix, and we've somehow dropped the declarations
> needed to make it go. You might want to pull down an old tarball (6.3
> or before) and look at how it compiles the s_lock support on Ultrix.
Any hints for Alexander on how to do it *if* it is a MIPS processor?
- Thomas
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Hamby | 2001-03-26 16:57:24 | Patch (tiny): \cd (change dir) for psql. |
Previous Message | Mayers, Philip J | 2001-03-26 16:15:27 | RE: MACADDR types NULL value (undocumented?) |
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Lockhart | 2001-03-26 17:14:17 | Re: Call for platforms |
Previous Message | Pete Forman | 2001-03-26 14:58:53 | IANA registration |