Horton

Thread

  1. crypt not included when compiling libpgtcl !!!!!!!

    Constantin Teodorescu <teo@flex.ro> — 1998-11-05T16:48:52Z

    RedHat 5.1 i386 with PostgreSQL v6.4 final version

./configure --with-tcl

after installing libpgtcl , cannot run pgaccess because library crypt
hasn't been linked into libpgtcl.so

must manually add -lcrypt in Makefile into src/interfaces/libpgtcl

Also, PgAccess version that has been included in 6.4 final version is
0.90 , but current stable version is 0.91
(ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.91.tar.gz)


Constantin Teodorescu
FLEX Consulting Braila, ROMANIA

  2. Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-11-05T17:29:59Z

    > Also, PgAccess version that has been included in 6.4 final version is
> 0.90 , but current stable version is 0.91
> (ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.91.tar.gz)

Yes, it missed the code freeze cutoff and the bug fix cutoff. Next
release try to get the new version announced at least a couple of weeks
before the nominal release date, and a month before would be even
better. Should be in v6.4.1 but I don't think anyone has committed it
yet.

                   - Tom

  3. Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Marc G. Fournier <scrappy@hub.org> — 1998-11-06T03:14:01Z

    On Thu, 5 Nov 1998, Thomas G. Lockhart wrote:

> > Also, PgAccess version that has been included in 6.4 final version is
> > 0.90 , but current stable version is 0.91
> > (ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.91.tar.gz)
> 
> Yes, it missed the code freeze cutoff and the bug fix cutoff. Next
> release try to get the new version announced at least a couple of weeks
> before the nominal release date, and a month before would be even
> better. Should be in v6.4.1 but I don't think anyone has committed it
> yet.

	Working on it right now...sorry Constantin :(

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org

  4. Re: [HACKERS] Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Bruce Momjian <maillist@candle.pha.pa.us> — 1998-11-06T04:37:14Z

    > On Thu, 5 Nov 1998, Thomas G. Lockhart wrote:
> 
> > > Also, PgAccess version that has been included in 6.4 final version is
> > > 0.90 , but current stable version is 0.91
> > > (ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.91.tar.gz)
> > 
> > Yes, it missed the code freeze cutoff and the bug fix cutoff. Next
> > release try to get the new version announced at least a couple of weeks
> > before the nominal release date, and a month before would be even
> > better. Should be in v6.4.1 but I don't think anyone has committed it
> > yet.
> 
> 	Working on it right now...sorry Constantin :(

I did pull down 0.90 about a month ago, and never went back to see if a
newer one existed.

-- 
  Bruce Momjian                        |  http://www.op.net/~candle
  maillist@candle.pha.pa.us            |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

  5. Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Eric Lee Green <eric@linux-hw.com> — 1998-12-06T20:45:15Z

    On Thu, 5 Nov 1998, Constantin Teodorescu wrote:
> RedHat 5.1 i386 with PostgreSQL v6.4 final version
> 
> ./configure --with-tcl
> 
> after installing libpgtcl , cannot run pgaccess because library crypt
> hasn't been linked into libpgtcl.so
> 
> must manually add -lcrypt in Makefile into src/interfaces/libpgtcl

Hi Constantin. This is a problem only with systems running glibc, because
for legal reasons the FSF doesn't want to include encryption as part of
glibc. I assume you are doing this on Debian or on Red Hat 5.x?

Perhaps we  need an extra template for glibc?  

I came across this problem too today (I am currently packaging 6.4 into an
RPM for Red Hat 5.2). I have generated a patch file which fixes the lack
of -lcrypt in a number of places for glibc systems. After I have
thoroughly tested it I'll try to post it here.

> Also, PgAccess version that has been included in 6.4 final version is
> 0.90 , but current stable version is 0.91
> (ftp://ftp.flex.ro/pub/pgaccess/pgaccess-0.91.tar.gz)

Thanks for the pointer. I will incorporate that as another patch in
the .spec file for my Red Hat RPM. 

--
Eric Lee Green         eric@linux-hw.com     http://www.linux-hw.com/~eric
 "Linux represents a best-of-breed UNIX, that is trusted in mission
  critical applications..."   --  internal Microsoft memo

  6. Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-12-06T23:39:04Z

    > (I am currently packaging 6.4 into an RPM for Red Hat 5.2).

Is this an alternative to the RedHat packaging, or are you using the
same layout and RPM setup that the RedHat 6.3 package had? Just curious;
I've been thinking about trying to help with RPM support but would be
happy that someone else is looking after it.

btw, we are currently looking at a date/time peculiarity in Postgres
with glibc2 which gives funny results for at least one test case. You
might want to stay in touch so we can fix that up for you also, once we
have a good workaround.

Actually, we should also test with RH5.2 to make sure the date/time
problem is still present, since it may have been due to a problem in
glibc2 which has since been fixed. I'm only running RH4.2 and RH5.1 so
can't directly test that myself...

                    - Tom

  7. Re: [INTERFACES] crypt not included when compiling libpgtcl !!!!!!!

    Eric Lee Green <eric@linux-hw.com> — 1998-12-07T05:33:36Z

    On Sun, 6 Dec 1998, Thomas G. Lockhart wrote:
> > (I am currently packaging 6.4 into an RPM for Red Hat 5.2).
> 
> Is this an alternative to the RedHat packaging, or are you using the
> same layout and RPM setup that the RedHat 6.3 package had? Just curious;

I am using the same layout and RPM setup that the Red Hat 6.3 package
had, but I had to make a fair number of changes to their setup to make
6.4 work.  I think I probably ended up changing about 1/3rd of the
"action" portions of their .spec file, and the patch file I used to
make it install and link cleanly was generated from scratch. I am not
doing this for Red Hat Software, I am doing it because I need to
deploy 6.4 and doing it via RPM is the easiest way to deploy on Red
Hat. And perhaps more importantly, I'm doing it because it's there
:-).

> I've been thinking about trying to help with RPM support but would be
> happy that someone else is looking after it.

Well, if you have some suggestions I'm certainly not loathe to ignore them!
Right now, the only suggestion I can think of that I'd like to implement
would be to somehow figure out how to compile the Python module at the same
time that I compile the rest of it, but I'm not sure that Python is capable
yet of doing that Perl trick of compiling a module against the Perl .so 
link library without having the source code around. I'll have to check
with the Python gurus on that one. 

> Actually, we should also test with RH5.2 to make sure the date/time
> problem is still present, since it may have been due to a problem in
> glibc2 which has since been fixed. I'm only running RH4.2 and RH5.1 so
> can't directly test that myself...

Well, RH5.2 is still using glibc 2.0.7, albeit patched up about 10
more times since RH 5.1 :-). But sure, if you have a test case to run,
drop it in the mail to me and I'll be happy to run it. 

One thought: Do you have a TZ environment variable set on your RH5.1?
I don't remember whether glibc needs one or not (I know there were other
programs sensitive to the TZ environment variable under RH5.1, like BRU, 
but it is 12:30am here on the east coast and my mind is not as clear as
it should be :-). 

--
Eric Lee Green         eric@linux-hw.com     http://www.linux-hw.com/~eric
 "Linux represents a best-of-breed UNIX, that is trusted in mission
  critical applications..."   --  internal Microsoft memo