Hi Tom,
I tried to apply the patch. I succeeded in patching configure, configure.in and src/include/pg_config.h.in files.
But while applying the patch for src/include/storage/s_lock.h , I am getting an error.
This is how I am doing the patch,
- I copied the diff output given in the link mentioned in the below email.
- Changed the file names appropriately (patch file path is different from source file path. But I have initialized --- and +++ appropriately
- Executed the patch command in the Postgres 9.1.1 directory as “patch src/include/storage/s_lock.h -i s_lock.h_Patch”
- Got the following output
Hunk #1 succeeded at 252 with fuzz 1.
Hunk #2 FAILED at 292.
1 out of 2 hunks FAILED -- saving rejects to file src/include/storage/s_lock.h.rej
Thought of doing the failed patch manually. But couldn’t understand what to do.
Please let me know what I am doing wrong and what I should be doing.
Thanks and Regards
Jayashankar
-----Original Message-----
From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx]
Sent: 24 February 2012 AM 09:20
To: Jayashankar K B
Cc: pgsql-general@xxxxxxxxxxxxxx; pgsql-performance@xxxxxxxxxxxxxx
Subject: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
From: Tom Lane [mailto:tgl@xxxxxxxxxxxxx]
Sent: 24 February 2012 AM 09:20
To: Jayashankar K B
Cc: pgsql-general@xxxxxxxxxxxxxx; pgsql-performance@xxxxxxxxxxxxxx
Subject: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
Jayashankar K B <Jayashankar.KB@xxxxxxxxxx> writes:
> Hi All,
> I am trying to compile Postgres Source code for ARM cortex A8 architecture.
> While compiling, I got an error message which read "selected processor does not support `swpb r4,r4,[r3]' "
> One of the Postgres forums at the location "http://postgresql.1045698.n5.nabble.com/BUG-6331-Cross-compile-error-aborts-Works-if-disable-spinlock-is-used-td5068738.html"
> Mentioned that by using -disable-spinlocks, we can overcome the error at the cost of performance. I did the same and it compiled successfully.
> But the INSTALL guide in Postgres source code mentioned that I should inform the Postgres community in case I am forced to use -disable spinlocks to let the code compile.
> Hence this email. So please suggest me what I should do now.
Try this patch:
BTW, please don't cross-post to multiple PG mailing lists; there's very seldom a good reason to do that.
regards, tom lane
Larsen & Toubro Limited
www.larsentoubro.com
This Email may contain confidential or privileged information for the intended recipient (s) If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.
