Are you ready for Kylix? Do a good job, as a person. I don't want to have a stone of the mountain to attack jade, but never be a slave. Cker Original: borland Translation: cker
TRANSLATED BY CKER How do you prepare for Kylix? of course! Can you be ready for Kylix? When developing Kylix, we found some problems, although most of the latest Linux versions have already indicated these issues. However, if Linux in your hand is an old version, for example, you downloaded the Linux version last week, you may encounter the same problem as me. Read this article You can make your system ready for Kylix! The first step is to download our test programs and Glibc patches. You can download the Pre-Test program of Borland Kylix from http://www.borland.com/devsupport/kylix/downloads/. Download the compressed file in the TAR format after downloading. You will find the directory called Borpretest. There is a shell script called Testsytem in this directory. This script runs a test program called Borpretest, checks if your system meets the basic needs of Kylix installation. For example, libjpeg version, basic libc version, and so on. In addition, it also tries to load and uninstall some system modules to test compatibility with Linux Loader. If you have the correct system files in your system to run Kylix, Borpretest will tell you in its terminal output. Detailed error message description is included in a text file called Preinstall. This article will focus on adding a few detailed messages about Linux Loader, and how to upgrade your system. Here is a short description of the main BUG of Linux Loader. Suppose we use a module loaded by your program called Module A, and Module A has a dependency on Module A1, and your program is loaded with Module B. If the Module B share the dependency of Module A1, you will have trouble when trying to uninstall Module A and B! At the same time uninstalling Module A and B, the reference count of Module A1 cannot be updated correctly. If you use this reference in the future, it will cause crash! Fortunately, we already know how to make up for this problem, gnu.org has agreed to join the main Libc branch version. Whether you can get this question depends on your Linux release. We have now available Pre-Built solutions for Red Hat 6.2, 7.0, Mandrake 7.2 and SUSE 7.0. This fix is included in the GLIBC 2.2 official version of Red Hat 7.0. Red Hat 6.2 has not yet been issued a formal patch. We have provided an internal use version of 6.2, but we have not been supported by Red Hat. Usually you can use it safely in your development environment, but we recommend that you do not distribute this version to your users. We have tested it on Kylix's related content, but it is not guaranteed to use this patch security. The risk of use is conceited by you. At the same time, we provide all source files for patches. Mandrake has released an "informal" GLIBC branch version that includes this correction, you can download from ftp://ftp.sunet.se/pub/linux/distributions/mandrake-devel/unsupported/i586. Also, you should pay attention to Mandrake's release without debug symbols, which makes it difficult to debug on Mandrake. We recommend that you recompile the system with Debug symbols. SUSE has released a formal patch of version 7.0, you can download it from http://www.suse.com/us/support/download/. Kylix's Server version and Desktop version will be bundled with SUSE7.0's revised shared version. We have provided the source file for this test program. We use the same test mechanism before installing Kylix. If the Loader's patch is not installed, Kylix will refuse to install.
