Re: [PHP4BETA] sybase-ct
| From: | Joey | Date: | Thu, 02 Sep 1999 12:33:44 +0000 |
| Subject: | Re: [PHP4BETA] sybase-ct | ||
| References: | 1 | Groups: | php.version4 |
| Request: | Send a blank email to php-version4+get-3998@lists.php.net to get a copy of this message | ||
I just wanted to make sure I wasn't losing my marbles.
Anyone have any ideas why "libtcl.so" on my Sun is the same
library as libsytcl.so on my linux box? That seems odd to me...
Ahh, well.
While I understand that it is not php's problem, I _AM_ curious
as to whether php can detect said name conflict and either
A) Warn user
OR
B) Resolve it (ie, symlink or something)
Just an idea...
--Joey Smith
On Thu, 2 Sep 1999, Jakub Skopal wrote:
> 01.09.1999 v 13:18:17 (-0600), Joey napsal:
> >
> > Also, on a side note:
> > On Sun, could not get --with-sybase-ct compiled.
> > I track it down to -ltcl. I appear to have a libtcl.so
> > in my "tcl 8.0" toolkit, and a libtcl.so in my "sybase
> > ct" toolkit. I symlinked the sybase one to libsybtcl.so,
> > added -lsybtcl, and it worked fine...anyone else have
> > experience with this?
> Yes. This is not a problem of php, but the name-conflict
> you described. Only working workaround, except temporarily
> override libtcl from tcl8.0, as you described above, I
> found, was not adding -ltcl while linking, but
> <full-path-to-libtcl-of-sybase>/libtcl.so. it works then,
> but I'm not sure, whether the final binary can be moved to
> another system, having libtcl.so somewhere else.
>
> Jakub
>
> --
>
> Jakub "RiffRaff" Skopal
> mailto:j@kubs.cz
>