On Thu, 24 May 2001, Tom Lane wrote:
Great, I'll pass this on thanks.
> Chris Bowlby <excalibur@hub.org> writes:
> > The configure script errors out looking
> > for _eprintf(), which apparently is a now deprecated GCC
> > attempt at a compatibility layer. This tells me I really
> > can't use the binary build made by the HP-UX porting archive
> > folks.
>
> FWIW, I've seen eprintf link failures on HPUX 10.20 as well. I think
> the key to avoiding it is that you have to build all the components with
> the same compiler (all gcc, or all HP's). If you want to link against a
> precompiled ssl library then that will determine your choice of compiler.
>
> > Cannot compile PostgreSQL and C++ library (--with-CXX) with GCC.
> > Can't find <string> class in STL. Suspect packaging
> > job done by HP-UX porting archive: it moves GCC from
> > /usr/local to /opt, and a few things didn't make the
> > trip smoothly.
>
> I agree. I don't have any trouble building the C++ library here,
> using either hand-built gcc or HP's cc. I let gcc install itself
> in the usual place, ie, /usr/local.
>
> The Porting Archive guys do good work, but their stuff gives headaches
> if you want to mix and match it with stuff you build yourself. They're
> way too eager to mess around with install locations.
>
> I'd recommend rebuilding gcc in a vanilla configuration, using the
> porting archive gcc just for bootstrap purposes.
>
> regards, tom lane
>
Chris Bowlby,
-----------------------------------------------------
Web Developer @ Hub.org.
excalibur@hub.org
www.hub.org
1-902-542-3657
-----------------------------------------------------
