Doug, Well, this just reinforces my point. Every RPM you tried to install is for the Intel platform, hence the "i386" in all the names: sapdb-ind-7.3.0.15-1.i386.rpm glibc-2.2.4-24.i386.rpm glibc-common-2.2.4-24.i386.rpm
Those simply aren't going to work on Linux/390. Until I, or someone else, finishes porting this package, nothing will. If you have anyone on your staff that's familiar with Makefiles and C/C++ that would be able to work with me on this, I'd be more than willing to accept their help. Mark Post -----Original Message----- From: Douglas Becker [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 7:03 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: RE: sapdb on SuSE Linux Enterprise Server 7 for S/390 Mark, Your post was helpful. What we have found is that fundamental to making the sapdb-ind-7.3.0.15-1.i386.rpm install correctly was ld-linux.so.2; not a problem said we, we'll just install it off of glibc-2.2.4-24.i386.rpm. Unfortunately, that led to the dependency of glibc-common = 2.2.4-24. Well, ok, we'll just rpm install glibc-common-2.2.4-24.i386.rpm. But NO! We got "error" failed dependencies: glibc < 2.2.4 conflicts with glibc-common-2.2.4-24. Hmm. We got out the big guns and did a "rpm -Uvh --nodeps --force glibc-common-2.2.4-24.i386.rpm". After churning quite awhile, it came out with "package glibc-common-2.2.4-24 is for a different architecture". It seems that we are stuck with glibc-2.2.2-26, and without 2.2.4, we are dead in the water. We have the latest official version with th 2.4.7-SuSE-SMP October 30, 2001 generation of Linux kernal, and it appears that the glibc versions are earlier than the versions installed on the official system. For now, we will be pursuing PostgreSQL, although it may not be as stable as sapdb [we're concerned about having to run vacuum all the time], but it does contain both foreign keys and stored procedures that MySQL does not. Thanks for responding--it has been helpful. Best regards, Douglas >>> "Post, Mark K" <[EMAIL PROTECTED]> 05/16 6:54 AM >>> Douglas, I'm working (slowly) to port sapdb to Linux/390. There are a number of issues that need to be overcome, one of which is that some of the tools needed to build the product from source are still Intel binaries. The source code for the development tools was just released, and there are problems getting them to compile on Linux/390 as well, so progress has been rather slow. Part of my problem is a lack of experience with C/C++/Makefiles, etc. in general, but the SAP employees on the list have been very helpful so far. Mark Post -----Original Message----- Date: Wed, 15 May 2002 10:43:27 -0700 From: "Douglas Becker" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Subject: sapdb on SuSE Linux Enterprise Server 7 for S/390 It isn't clear that it is possible to run sapdb on SuSE Linux Enterprise Server 7 for S/390 but is worth the effort on our IBM 7060 H30 if it can be made to work. The IBM H30 is a 'sort of' intel based machine and runs OS/2 native on the support element--it is supposed to mostly have the intel instruction set. This is running in a separate LPAR with SuSE Linux. In attempting to install sapdb, I set up sapdb-ind-7.3.0.15-1.i386.rpm in /tmp/linux and tried the following command: rpm -Uv --test sapdb-ind-7.3.0.15-1.i386.rpm this resulted in: error: failed dependencies: ld-linux.so.2 is needed by sapdb-ind-7.3.0.15-15-1 libstdc++-libc6.1-1.so.2 is needed by sapdb-ind-7.3.0.15-1 I cannot figure out where to get these or how to install them--even if it does work. _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
