Kylix - Deploy binaries on Fedora Core 5 and 4

Author

Deploy binaries on Fedora Core 5 and 4

Toni Martir

2006-06-17, 8:47 am

Hello,

Kylix compiled binaries with database access (TClientDataset) had a problem
with new pthread implementation, so to work on newer distros I used:

export LD_ASSUME_KERNEL=2.2.41

Then the old pthread (libpthread.0.so) implementation is used and the
application work ok.

But new Fedora Core distros dropped old pthread implementation, that is
since Fedora Core 4 there is no support for this feature (choose old
LinuxThreads)

Is there a way to workaround this?
Is there a patch to binaries or libraries to work with new pthreads?

Thanks

Thomas Maeder [TeamB]

2006-06-17, 8:47 am

Please direct your browser at http://info.borland.com/newsgroups/ and
read the newsgroup guidelines. One of them asks us not to post the
same question to different newsgroups, but to pick the most
appropriate one and just post there. Thanks!

In particular, please don't post clearly technical posts in
..non-technical.

Michael Schnell

2006-06-17, 8:47 am

>
> Then the old pthread (libpthread.0.so) implementation is used and the
> application work ok.
>

Don't the new threads work with your application ? Why ?

-Michael

Simon Kissel

2006-06-17, 8:47 am

> Hello,
>=20
> Kylix compiled binaries with database access (TClientDataset) had a =
problem
> with new pthread implementation, so to work on newer distros I used:
>=20
> export LD_ASSUME_KERNEL=3D2.2.41
>=20
> Then the old pthread (libpthread.0.so) implementation is used and the
> application work ok.

I assume you are talking about NPTL (Native Posix Thread Library) that =
is
used by default on Red Hat for quite some time.

To my knowledge all Borland-supplied units including Midas work just =
fine
with NPTL. Most likely, the problem is in your own code. The most common =

problem when using NPTL is calling Suspend on a running thread (which is
highly unclean design anyway).

Simon

Toni Martir

2006-06-24, 8:32 am

>with NPTL. Most likely, the problem is in your own code. The

Well, I found the source of the problem, the mysql dbexpress driver, so it's
not my code but Borland code.

Using the DBExpress-OpenODBC-unixODBC configuration solved the problem, but
on distros supporting the old thread implementation
(LD_ASSUME_KERNEL=2.2.41), the driver woked ok.

Unfortunately I have other instalation with Fedora Core 5 and the midaslib
library is experimenting the same problem, I think a compatibility library
is missing there.

Thanks

"Simon Kissel" <kissel@computerman.de> escribió en el mensaje
news:449071be$1@newsgroups.borland.com...
> Hello,
>
> Kylix compiled binaries with database access (TClientDataset) had a
> problem
> with new pthread implementation, so to work on newer distros I used:
>
> export LD_ASSUME_KERNEL=2.2.41
>
> Then the old pthread (libpthread.0.so) implementation is used and the
> application work ok.

I assume you are talking about NPTL (Native Posix Thread Library) that is
used by default on Red Hat for quite some time.

To my knowledge all Borland-supplied units including Midas work just fine
with NPTL. Most likely, the problem is in your own code. The most common
problem when using NPTL is calling Suspend on a running thread (which is
highly unclean design anyway).

Simon

Simon Kissel

2006-06-24, 8:32 am

> Well, I found the source of the problem, the mysql dbexpress driver, =
so it's=20
> not my code but Borland code.

The Borland mysql driver is crap. Ever was. Invest the few bucks and go =
buy the
MySQL Dbexpress driver from Core Lab (crlab.com). Those drivers work =
with all
versions of Mysql, in multithreading etc and get updated.

(I'm a very happy customer of theirs)

> Using the DBExpress-OpenODBC-unixODBC configuration solved the =
problem, but=20
> on distros supporting the old thread implementation=20
> (LD_ASSUME_KERNEL=3D2.2.41), the driver woked ok.

The Borland MySQL driver never really worked "ok" imho.

> Unfortunately I have other instalation with Fedora Core 5 and the =
midaslib=20
> library is experimenting the same problem, I think a compatibility =
library=20
> is missing there.

I've used midaslib on NPTL-systems already, and didn't see problems.

Simon

Sponsored Links