RE: Slackware and IDS9.4

Though the advice to use libraries from RH is good, the explanation is not correct. The problem is that Slackware comes with i386 version of GLIBC, while Informix requires i686 version which comes with SuSE and RedHat. The difference between i386 and i686 GLIBC packages is that: 1. libpthread doesn't contain some significant functions (smth like _on_exit()) 2. PRIVATE section is missing in ld-linux.so.2 (GLIBC_PRIVATE) => /lib/ld-linux.so.2 GLIBC 2.3 from RH doesn't work well on Slackware, while GLIBC 2.3 from Suse works fine. That is, just install GLIBC 2.3.xxx from Suse Linux (eg glibc-2.3.2-88.i686.rpm) onto your Slackware box - and enjoy Informix 9.4 under Slackware -Alexey > -----Original Message----- > From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On > Behalf Of Spamme > Sent: Thursday, January 20, 2005 12:40 PM > To: informix-list@iiug.org > Subject: Re: slackware and IDS9.4 > > Yes but it is really tricky, I am assuming you are hitting the part > where it just dies about halfway of coming online? Test this first with > a clean installed box before trying it with any kind of production > system since about 1 in 4 that I do this with I end up having to reinstall. > The problem stems from the fact they static linked against glibc 2.2 > whereas most modern distros have 2.3, apperantly with the next release > they should be against modern libraries but currently its what we have > to work with. > The trick is force installing the 2.2 libraries, initializing the > server, and then reinstalling the 2.3 libraries. I normally do the > following, I get rpm's for both 2.2 and 2.3, I also get a copy of rpm > which has been statically linked against glibc 2.2 [any red hat 7.2 box > will work fine for this]. Then use the slackware rpm software to install > the 2.2 glibc, make sure to have a few terminal windows and at least one > sftp session open at this point because until 2.3 is reinstalled you > will not be able to make new connections. You will find this will break > almost everything on the system. > At this point bring up the informix instance, I have had varied > results [I am guessing due to slightly different versions of glibc] > where sometimes I need to reinstall glibc2.3 first sometimes not. > Follow this up by running the 2.2 version of rpm to reinstall > glibc2.3 [the rpm that comes with slackware will be broken]. If this > reinstalls fine then you will be set. Sometimes also the rpm package > database will not work properly with the older rpm so you may need to > move some files around [or over from a rh 7.2 system] to correct this issue. > Once you force reinstall glibc 2.3 everything should be back to > normal but informix will have everything it needs to run. There may be a > much simpler way of just moving libraries around to solve the problem > but I have yet to find it. > If you want a safer method, run knoppix, and mount the drive you are > installing to, have one ssh session open to standard knoppix with the drive > mounted, and one to it with the drive chrooted, so in case anything goes wrong > on the chrooted enviorment you can still change things on the fly from the > knoppix mounted drive. > -Tom Beebe > > > malabapa wrote: > > >Has anyone gotten 9.4 working on slackware. I am trying slackware 10.0 > >and not really getting any success. I have seen older versions of IDS > >working on older releases of slackware, but not 9.4. If someone has, I > >would really like to know the release of slackware they are using as > >well as the glibc and open_motif. > > > >I hate the thought of familiarizing myself with another *nix OS when I > >have so many Slack boxes in use now. > > > >Thanks in advance. > > > > > > > > > > sending to informix-list sending to informix-list