On Fri, Apr 16, 2010 at 10:36 AM, Tom Lane wrote:
> Scott Mead writes:
> > Huh? This I find hard to believe. Whenever I've had problems with
> readline
> > it was actually libtermcap that was giving me a headache. Are you sure
> that
> > there's nothing in there that's pointing you to your lib
Scott Mead writes:
> Huh? This I find hard to believe. Whenever I've had problems with readline
> it was actually libtermcap that was giving me a headache. Are you sure that
> there's nothing in there that's pointing you to your libtermcap being
> 'wonky'
I think he's confusing what happen
On Thu, Apr 15, 2010 at 10:22 PM, zhong ming wu wrote:
> Dear List
>
> I need to build a postgres on a linux machine that I don't have root
> access.
>
> I built readline from source and installed it with prefix of /home/me/local
>
> readline library are in /home/me/local/lib and headers files ar
zhong ming wu wrote:
After explicitly specfying these paths with --with-libs and
with-includes postgres configure is still choking
on readline.
Doing this is painful, but one hack you can try is pointing:
export LD_LIBRARY_PATH=/home/me/local/lib
I've used that combined with setting --with
zhong ming wu writes:
> I need to build a postgres on a linux machine that I don't have root access.
> I built readline from source and installed it with prefix of /home/me/local
If you don't have root you're going to be in for a lot of pain here.
Linux is not designed to be friendly to libraries
Dear List
I need to build a postgres on a linux machine that I don't have root access.
I built readline from source and installed it with prefix of /home/me/local
readline library are in /home/me/local/lib and headers files are in
/home/me/local/include/readline
After explicitly specfying these