Andrew Chernow wrote:
I'll hack the makefile and give it a shot.
No need to hack it, set CFLAGS during configure:
shell]# CFLAGS=-m64 ./configure (options)
I tried that and it still built a 32 bit version of perl. When I
checked the make file it didn't have CFLAGS anywhere. I manually
Zdenek Kotala wrote:
Andrew Chernow píše v po 19. 10. 2009 v 14:14 -0400:
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
{snip}
u235sentinel píše v út 20. 10. 2009 v 12:22 -0600:
Now I'm running and will add a few more things in like readline. The
goal is to build plr and plperl and load them into postgres.
Hmm, I'm afraid that 64bit plperl is a problem. Solaris 10 is not
shipped with 64bit perl :(.
Zdenek
Zdenek Kotala wrote:
Hmm, I'm afraid that 64bit plperl is a problem. Solaris 10 is not
shipped with 64bit perl :(.
Zdenek
Found that the hard way today :-)
I'm downloading perl source and will make a 64 bit version. Anybody
know if -m64 will work with compiling 64 bit perl?
I'll hack the makefile and give it a shot.
No need to hack it, set CFLAGS during configure:
shell]# CFLAGS=-m64 ./configure (options)
--
Andrew Chernow
eSilo, LLC
every bit counts
http://www.esilo.com/
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to
u235sentinel píše v ne 18. 10. 2009 v 17:50 -0600:
Are you sure about this? When I try to build and don't have openssl in
the lib/include path it claims it needs it. As I'm building 64 bit I
can now build postgres in 64 bit with openssl 98k just fine. However
when I run it I'm getting
Andrew Chernow píše v ne 18. 10. 2009 v 21:09 -0400:
I'm curious if this is a lost hope. My boss is recommending we flatten
the Sun box and install redhat linux (which I'm fine with). I'd rather
not as threading in Solaris is better.
Maybe solaris threads were better 10-15 years ago,
Zdenek Kotala wrote:
Andrew Chernow píše v ne 18. 10. 2009 v 21:09 -0400:
I'm curious if this is a lost hope. My boss is recommending we flatten
the Sun box and install redhat linux (which I'm fine with). I'd rather
not as threading in Solaris is better.
Maybe solaris threads were better
Zdenek Kotala wrote:
I can point on this article:
http://tweakers.net/reviews/649/all/database-test-sun-ultrasparc-t1-vs-punt-amd-opteron.html
Zdenek
Ok so I'm checking everything in my environment. The system actually
builds postgres with openssl98k. Comes back and says it's
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
symbol (unknown). Can you turn on debugging symbols? Knowing the
symbol may point to a library that was not compiled
Andrew Chernow píše v po 19. 10. 2009 v 14:14 -0400:
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
symbol (unknown). Can you turn on debugging symbols?
Are you sure about this? When I try to build and don't have openssl in
the lib/include path it claims it needs it. As I'm building 64 bit I
can now build postgres in 64 bit with openssl 98k just fine. However
when I run it I'm getting the same error message.
I'm curious if this is a lost
I'm curious if this is a lost hope. My boss is recommending we flatten
the Sun box and install redhat linux (which I'm fine with). I'd rather
not as threading in Solaris is better.
Maybe solaris threads were better 10-15 years ago, but I'm not convinced that is
still the case. Any data
You can look on
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=ghost_mothdt=2009-10-07%2021:06:00
How it is built. You also does not needed own version of Openssl. All
security fixes are backported. It is located in /usr/sfw/lib or
/usr/sfw/lib/64
Sometimes are problem with gcc and
Zdenek Kotala wrote:
You can look on
http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=ghost_mothdt=2009-10-07%2021:06:00
How it is built. You also does not needed own version of Openssl. All
security fixes are backported. It is located in /usr/sfw/lib or
/usr/sfw/lib/64
Sometimes are
So I compiled postgres with Solaris 10 and have problems running it.
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
# ldd pg_ctl
libpq.so.5 =
u235sentinel wrote:
So I compiled postgres with Solaris 10 and have problems running it.
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
Maybe libpq.so wasn't built
Andrew Chernow a...@esilo.com writes:
u235sentinel wrote:
So I compiled postgres with Solaris 10 and have problems running it.
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not
Andrew Chernow wrote:
u235sentinel wrote:
So I compiled postgres with Solaris 10 and have problems running it.
# ./pg_ctl
ld.so.1: pg_ctl: fatal: relocation error: R_AMD64_32: file
/usr/local/postgres64/lib/libpq.so.5: symbol (unknown): value
0xfd7fff1cf210 does not fit
Killed
Maybe
19 matches
Mail list logo
