PostgreSQL 8.0.0beta2 compile error with Sun CC.

From: Mark Round <mark(at)markround(dot)com>
To: pgsql-ports(at)postgresql(dot)org
Subject: PostgreSQL 8.0.0beta2 compile error with Sun CC.
Date: 2004-09-24 13:23:48
Message-ID: 41541FE4.2070103@markround.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Mark Round
Your email address : mark(at)markround(dot)com

System Configuration
---------------------
Architecture (example: Intel Pentium) : Sparc (UltraSparc IIi)

Operating System (example: Linux 2.4.18) : Solaris 8

PostgreSQL version (example: PostgreSQL-8.0): PostgreSQL-8.0.0beta2

Compiler used (example: gcc 2.95.2) : Sun C 5.5 2003/03/12

Please enter a FULL description of your problem:
-----------------------------------------------
Compilation fails with the error that ".seg" is no a recognised opcode.
The error is in src/backend/storage/lmgr/s_lock.c , lines 228 and 229.

Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
Compile using Sun's C compiler.

If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
.seg should be changed to .section.
Lines 229 and 229 in s_lock.c should be changed to the following :

asm(".section \"data\"");
asm(".section \"text\"");

From docs.sun.com SPARC assembly manual : "This pseudo-op (.seg) is
currently supported for compatibility with existing SunOS 4.1 SPARC
assembly language programs. This pseudo-op has been replaced by the
.section pseudo-op."

Responses

Browse pgsql-ports by date

  From Date Subject
Next Message Tom Lane 2004-09-24 14:42:18 Re: PostgreSQL 8.0.0beta2 compile error with Sun CC.
Previous Message Tom Lane 2004-09-18 16:12:11 Re: