From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Lars Ewald (web(dot)de)" <l(dot)ewald-web(at)lars-ewald(dot)de> |
Cc: | pgsql-bugs(at)postgreSQL(dot)org |
Subject: | Re: Compile fails on AIX 6.1 |
Date: | 2014-07-15 19:19:30 |
Message-ID: | 9154.1405451970@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
[ again, please keep the mailing list cc'd ]
"Lars Ewald (web.de)" <l(dot)ewald-web(at)lars-ewald(dot)de> writes:
>> PPC what exactly?
> PowerPC_POWER5:
> System Model: IBM,9110-51A
> Machine Serial Number: *********
> Processor Type: PowerPC_POWER5
> Processor Implementation Mode: POWER 5
Huh. POWER5 certainly ought to be good with lwsync. I think the lwarx
hint bit doesn't do anything on POWER5, but it's not supposed to cause
problems either.
> Would it help to use a POWER7 system as followed?
If you can try the same build there and see whether it works, that would
be useful information; but we'd like PG to work on POWER5 too ...
>> Still, configure should have caught that. Does configure end up
>> defining HAVE_PPC_LWARX_MUTEX_HINT in src/include/pg_config.h?
> Yes, I HAVE_PPC_LWARX_MUTEX_HINT was defined.
> Commenting out USE_PPC_LWSYNC did not help. Also, commenting
> USE_PPC_LWSYNC out and set HAVE_PPC_LWARX_MUTEX_HINT to "0", was
> not successful.
I'm stumped then. Maybe the problem is something else entirely.
Could you look at the assembler output file and see exactly what
lines it's complaining about? If the temp file is not left
behind by a normal build, do the failing gcc call over again
manually, substituting -S for -c so you get a .s file as output.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2014-07-15 22:01:21 | Re: BUG #10794: psql sometimes ignores .psqlrc |
Previous Message | Tom Lane | 2014-07-15 18:43:56 | Re: INET datatype and '<<' operator results in bad row estimate |