Skip site navigation (1) Skip section navigation (2)

Re: Compiling on 8.1.3 on Openserver 5.05

From: Mark Campbell <mark(dot)campbell(at)ucs-software(dot)co(dot)za>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: Re: Compiling on 8.1.3 on Openserver 5.05
Date: 2006-05-12 15:05:09
Message-ID: 4464A425.2020400@ucs-software.co.za (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackerspgsql-ports
Thanks very much with your patience and help.

I cannot reinstall this machine as it belongs to my client, but I was 
going to try and make our lives easier (the developers) who have to 
maintain the whole system

Regards

Mark Campbell
mark(dot)campbell(at)ucs-software(dot)co(dot)za
(011) 712 1521

Confidentiality Notice: http://ucs.co.za/conf.html



Tom Lane wrote:
> Mark Campbell <mark(dot)campbell(at)ucs-software(dot)co(dot)za> writes:
>   
>> gcc -b elf -O2 -Wall -Wmissing-prototypes -Wpointer-arith -Winline 
>> -fno-strict-aliasing -I../../../../src/include   -c -o xlog.o xlog.c
>> /usr/tmp/cczOwssE.s:651:syntax error at name: f
>> /usr/tmp/cczOwssE.s:654:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:1092:syntax error at name: f
>> /usr/tmp/cczOwssE.s:1095:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:1541:syntax error at name: f
>> /usr/tmp/cczOwssE.s:1544:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:2218:syntax error at name: f
>> /usr/tmp/cczOwssE.s:2221:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:2327:syntax error at name: f
>> /usr/tmp/cczOwssE.s:2330:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:10457:syntax error at name: f
>> /usr/tmp/cczOwssE.s:10460:syntax error at integer constant: 1
>> /usr/tmp/cczOwssE.s:10732:syntax error at name: f
>> /usr/tmp/cczOwssE.s:10735:syntax error at integer constant: 1
>> gmake[4]: *** [xlog.o] Error 1
>>     
>
> I'm coming to the conclusion that there's something seriously broken
> about your system.  You were having trouble with gcc back at the
> beginning, IIRC, and seeing it emit malformed assembly code (which
> seems to be what's happening above) is certainly something that should
> never happen.  So you've got a borked compiler and/or assembler,
> no ar, headers that don't even come close to following the Single
> Unix Spec ... if I were you I'd get something more standard, or
> at least more up-to-date.  You're going to have trouble building
> *any* nontrivial software on that thing.
>
> Reading between the lines, I surmise that you initially had an
> installation without development tools (ar is certainly on the
> short list of things that MUST be there to do any development).
> It could be that some of the breakage is due to piecemeal addition
> of devel tools.  If so, it might help to reinstall the system from
> the ground up, being sure to select all the devel tools this time.
>
> 			regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>   

In response to

pgsql-ports by date

Next:From: Alan StangeDate: 2006-05-12 16:22:43
Subject: Re: solaris build problem with Sun compilers
Previous:From: Tom LaneDate: 2006-05-12 13:57:52
Subject: Re: Compiling on 8.1.3 on Openserver 5.05

pgsql-hackers by date

Next:From: Tom LaneDate: 2006-05-12 15:06:42
Subject: Re: any, anyelement, and anyarray
Previous:From: Bruce MomjianDate: 2006-05-12 14:51:23
Subject: Re: Continuing "pgstat update timeout" failures in buildfarm

pgsql-general by date

Next:From: Adrian KlaverDate: 2006-05-12 15:09:56
Subject: Re: pl/pgsql question
Previous:From: Rhys StewartDate: 2006-05-12 14:54:23
Subject: pl/pgsql question

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group