Skip site navigation (1) Skip section navigation (2)

Re: libpgtcl.so?

From: Brett Schwarz <brett_schwarz(at)yahoo(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: libpgtcl.so?
Date: 2004-03-19 03:07:33
Message-ID: 20040319030733.54211.qmail@web40614.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
Is pgaccess not running for you? Have you tried the
newest snapshot?

You don't necessarily need libpgtcl right now, but if
you really want it, then you should be able to compile
it from the makefile supplied in the libpgtcl
directory. I would be surprised if RedHat didn't
already come with libpgtcl installed. Have you checked
(sorry, I don't use RedHat).

What other dependencies are you having problems with?

BTW, there is a dedicated pgaccess list, if you would
like to use that. Go to www.pgaccess.org

    --brett


--- Vickriz Buenaventuura <vickr1z(at)operamail(dot)com>
wrote:
> good day too guru.
> pgaccess has lot of dependencies, actually nnot so
> much :)
> i already install tcl/tk in my system rh7.3 and the
> next step is the libpgtcl package [libpgtcl.so]
> which i found from postgresql installation source.
> my directory:
>
/usr/src/redhat/SOURCES/postgresql-7.3.2/src/interfaces/libpgtcl
> 
> and then i found this instraction at postgresql
> mailing list, tryingg to look for possible solution
> for other installation dependencies. but i really
> can understand what has to do with it. i need to
> post iit here so anybbody can help me..
> --
> Rather than applying that patch, it would probably
> be easier creating a
> 'Makefile.custom' file in the postgresql-6.3.2/src
> (which get included
> by Makefile.global, and thus every Makefile in the
> tree). Set
> LINUX_ELF=true in Makefile.custom, and you won't
> have to patch all of
> the shared library makefiles. You can also specify
> CUSTOM_CC and
> CUSTOM_COPT in Makefile.custom to specify your
> compiler and compile
> flags, respectively.
> 
> As for libpgtcl.so and unresolved symbols, I run a
> Redhat 5.0 system
> where the crypt() function lives in its own library
> (libcrypt) and not
> libc. libpgtcl.so is linked to libpq.so, which is
> statically linked.
> crypt() is probably used by libpq.so for passwords,
> etc, but since
> libpq.so is *not* linked with libcrypt, you must
> link libcrypt.so as
> well libpq.so into your app. The Tk shell, wish8.0,
> is *not* linked to
> libcrypt.so. Thus, when pgaccess.tcl loads the
> libpgtcl.so library, the
> system can't resolve the calls to crypt(). One
> solution is to run
> pgaccess.tcl with pgtksh, which *is* linked with
> libcrypt.so. Just
> change the first line of pgaccess.tcl to
> #!/usr/local/pgsql/bin/pgtksh
> (or where ever you installed postgresql). You could
> also link
> libpgtcl.so manually, adding the '-lcrypt' crypt
> option, which would let
> you run pgaccess.tcl and any other postgresql tcl
> scripts with wish and
> tclsh.
> ==================end===
> 
> please help how to edit my Makefile.custom at
> /usr/src/redhat/SOURCES/postgresql-7.3.2/src
> the next thing was the libpgtcl.. where should i put
> it and or what should i make a link to it?
> ..and what really next thing to do.
> 
> all i want is to use pgacces[gui] to administer my
> postgres database..
> 
> any help wwill appreciate very much. tnx..
> 
> vic
> 
> 
> -- 
>
_____________________________________________________________
> Web-based SMS services available at
> http://www.operamail.com.
> From your mailbox to local or overseas cell phones.
> 
> Powered by Outblaze
> 
> ---------------------------(end of
> broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster


__________________________________
Do you Yahoo!?
Yahoo! Mail - More reliable, more storage, less spam
http://mail.yahoo.com

In response to

  • libpgtcl.so? at 2004-03-19 02:54:54 from Vickriz Buenaventuura

pgsql-interfaces by date

Next:From: Vickriz BuenaventuuraDate: 2004-03-19 05:56:29
Subject: Re: libpgtcl.so?
Previous:From: Vickriz BuenaventuuraDate: 2004-03-19 02:54:54
Subject: libpgtcl.so?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group