Okay, I've now succeeded to build with
default runtime paths built/linked in,
although not using the optimal solution
(see end of this message).
Please see further comments in-lined below ...
Rolf Sponsel, 2005-02-04 23:26 GMT +01:00, wrote:
Tom Lane, 2005-02-01 04:45 GMT +01:00, wrote:
Rolf Sponse
Tom Lane, 2005-02-01 04:45 GMT +01:00, wrote:
Rolf Sponsel <[EMAIL PROTECTED]> writes:
From my understanding, the preferred way
for Solaris is to only set LD_RUN_PATH,
and avoid setting LD_LIBRARY_PATH, at
link-time. This is what I usually do.
And usually works very well.
No, the preferred thing is
Tom Lane wrote:
> Rolf Sponsel <[EMAIL PROTECTED]> writes:
> > From my understanding, the preferred way
> > for Solaris is to only set LD_RUN_PATH,
> > and avoid setting LD_LIBRARY_PATH, at
> > link-time. This is what I usually do.
>
> No, the preferred thing is to set -rpath within the executable
Rolf Sponsel <[EMAIL PROTECTED]> writes:
> From my understanding, the preferred way
> for Solaris is to only set LD_RUN_PATH,
> and avoid setting LD_LIBRARY_PATH, at
> link-time. This is what I usually do.
No, the preferred thing is to set -rpath within the executable, which
we do already (see Ma
*
Seem like I have to re-post once more;
since my post including the log file seemed
to exceede the allowed length restriction
for posted messages, imposed by your mail
server.
This time I'll provide the "attachement"
as a link to wherefrom you can download
t
Hi,
I've successfully built PostgreSQL 8.0.0
on SPARC/Solaris (7), with gcc-3.2.2.
Hardware is SPARCstation 5, 170 MHz.
Because it doesn't build optimally right
out of the box, I'd like to provide you
with some feed-back.
From my understanding, the preferred way
for Solaris is to only set LD_RUN_PA
