Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0KLXdV39818 for ; Sun, 20 Jan 2002 16:33:40 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g0KLXU305519; Sun, 20 Jan 2002 16:33:30 -0500 (EST) To: Peter Eisentraut cc: Brent Verner , Murray Prior Hobbs , Lamar Owen , pgsql-hackers@postgresql.org Subject: Re: pltlc and pltlcu problems In-reply-to: References: Comments: In-reply-to Peter Eisentraut message dated "Sun, 20 Jan 2002 16:12:45 -0500" Date: Sun, 20 Jan 2002 16:33:30 -0500 Message-ID: <5516.1011562410@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/815 X-Sequence-Number: 17818 Peter Eisentraut writes: >> Peter, didn't you have a proposal on the table to fix this? > Yeah, complain loudly to whoever dared to package a broken Tcl like > that... Or we'll work with Andreas Zeugwetter's patches and eliminate the > use of tclConfig.sh mostly. Yeah, I was taking a second look at Andreas' patch myself. At the time, the report was that we were only seeing a failure in RPM-packaged Postgres and so I thought that the root problem was somewhere in our RPM script. However, I have now tried it for myself and can confirm that we fail in a Postgres source build too. The bogus soname switch might be blamable on the Tcl RPM package and not on Tcl sources, but that doesn't make a lot of difference to us either way. I'm still quite nervous about making these changes so late in the cycle. OTOH I suspect Andreas was right: we haven't been getting any pltcl portability testing from our beta testers. If it's broken now, we can hardly make it worse. regards, tom lane