"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
>>> Unfortunately, it looks like the allow_non_pic_in_shlib setting broke
>>> platypus: http://lnk.nu/pgbuildfarm.org/3l3.pl
> Damn, I'm sorry, I totally mis-interpreted this. Turns out the failures
> are due to a perl problem.
Yeah, but the nonpic chang
On Wed, Aug 17, 2005 at 01:22:16PM -0400, Johnny Lam wrote:
> Tom Lane wrote:
> >"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> >
> >>Unfortunately, it looks like the allow_non_pic_in_shlib setting broke
> >>platypus: http://lnk.nu/pgbuildfarm.org/3l3.pl
> >
> >
> >>If I back that part of the patch o
Tom Lane wrote:
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
Unfortunately, it looks like the allow_non_pic_in_shlib setting broke
platypus: http://lnk.nu/pgbuildfarm.org/3l3.pl
If I back that part of the patch out, playtypus works fine.
So what's different between platypus and the machine
"Jim C. Nasby" <[EMAIL PROTECTED]> writes:
> Unfortunately, it looks like the allow_non_pic_in_shlib setting broke
> platypus: http://lnk.nu/pgbuildfarm.org/3l3.pl
> If I back that part of the patch out, playtypus works fine.
So what's different between platypus and the machines where it works?
W
Unfortunately, it looks like the allow_non_pic_in_shlib setting broke
platypus: http://lnk.nu/pgbuildfarm.org/3l3.pl
If I back that part of the patch out, playtypus works fine.
On Fri, Aug 12, 2005 at 04:57:58PM -0400, Bruce Momjian wrote:
>
> Patch applied. Thanks. If we made plpython worse,
Bruce Momjian writes:
> Patch applied. Thanks. If we made plpython worse, we will hear about
> it soon enough.
You did, and you're hearing about it. Please revert the
plpython/Makefile change; it is certainly wrong for every other
platform. What's more, it's unnecessary given the port makefil
Tom Lane wrote:
> Bruce Momjian writes:
> > Patch applied. Thanks. If we made plpython worse, we will hear about
> > it soon enough.
>
> You did, and you're hearing about it. Please revert the
> plpython/Makefile change; it is certainly wrong for every other
> platform. What's more, it's unne
Patch applied. Thanks. If we made plpython worse, we will hear about
it soon enough. The freebsd-specific changes seem safe, considering
they came from the FreeBSD port maintainers themselves.
---
Jim C. Nasby wrote:
> O
On Wed, Jul 13, 2005 at 01:24:17PM -0400, Andrew Dunstan wrote:
> >In any case, I've cleared the conflict and I'm running a build right
> >now.
octopus is building again, and is back to the behavior I mentioned in
http://archives.postgresql.org/pgsql-bugs/2005-07/msg00096.php. Is this
something th
