Author Topic: Compiling XPCOM (xpidl) fails -- need help!  (Read 11760 times)

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #15 on: August 21, 2014, 03:34:03 am »
I did yum update, it updated several headers, but then did the following:

[D:\] yum install python
Setting up install process
error: rpmdbNextIterator: skipping h#   134  region trailer:BAD,tag -1 type-1 offset 1 count -1
Package python-2.7.6-10.oc00.i386 already installed and latest version
Nothing to do

[D:\]python --version
Python 2.6.5

I'm outta here until tomorrow, (P.O'ed wife!) thanks for the help

klipp

Please search for python.exe, you most probably got the interpreter installed somewhere else, like, for example, yum bootstrap console, if you haven't erased it, and it's still in your PATH.

R.M. Klippstein

  • Sr. Member
  • ****
  • Posts: 305
  • Karma: +3/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #16 on: August 21, 2014, 10:58:47 pm »
Hi Boris, Now I have python.exe located in D:\tmp\yumbt\usr\ ! I tried running it from that location and it said it needed gcc473.dll. I copied gcc473 from /local473 directory to /ecs/dll and it runs giving this:

Python 2.6.5 (r265:79063, the date and the time!
gcc4.4.4 on os2knix
type "help", "copyright" etc etc for more information

Typing help did nothing and hung the system  --- I rebooted and copied \tmp\yumbt\usr to D:\usr. that looks like it fixed everything, I can use the python help menues etc.
But typing python --version at the root command prompt gives:Python 2.6.5 (not Python 2.7.6)? Which leaves me to wonder what I should use as an "iNCLUDE"  header when trying to compile source that is looking for the python header.
Also returning to yum and trying to install any of the debug, devel, magic, test, or tools packages gives the error:rpmdb:Damaged header #134 retreive----skipping. The system loops on this error and re-boot is only way out.
Thanks again for you're patience and excellent help!

klipp

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #17 on: August 22, 2014, 08:45:46 am »
Hi Boris, Now I have python.exe located in D:\tmp\yumbt\usr\ !

That's where all you problems come from.

I rebooted and copied \tmp\yumbt\usr to D:\usr. that looks like it fixed everything

That was a mistake, you should've just erased the whole \tmp\yumbt directory, then you'd have the only Python of version that yum reports.

You shouldn't have copied the bootstrap directory structure to your unixroot, now I have no idea what is the right way to return the environment to a geniune state.

Maybe yum reinstall python will replace your old python from yumbt with the new one from the repo, and maybe it will go without an apparent problem.

R.M. Klippstein

  • Sr. Member
  • ****
  • Posts: 305
  • Karma: +3/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #18 on: August 23, 2014, 12:53:46 am »
Thanks Boris, I screwed it up good and have been unable to get it straightened out correctly. I had backed up the \usr directory before doing any copying from \tmp\yumbt directory so I'm back to using python 2.6, it seems to work O.K. with my vbox compiling. I installed 2.7 correctly on a different partition and it works fine.  I'm thinking of copying the working  python 2.7 \usr directory to the partition I'm doing my compiling on , I believe that might make it work.

klipp

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #19 on: August 23, 2014, 10:28:27 am »
Thanks Boris, I screwed it up good and have been unable to get it straightened out correctly. I had backed up the \usr directory before doing any copying from \tmp\yumbt directory so I'm back to using python 2.6, it seems to work O.K. with my vbox compiling. I installed 2.7 correctly on a different partition and it works fine.  I'm thinking of copying the working  python 2.7 \usr directory to the partition I'm doing my compiling on , I believe that might make it work.

klipp

If yum reports you have python 2.7 installed, I can't see how it may be not installed, if you haven't modified the files in unixroot by hand.

Again, when you do python --version, the executable file in \tmp\yumbt is most likely gets executed instead of the one in \usr\bin!

And again, you don't need \tmp\yumbt now at all, it is located in the temporary directory \tmp, which means it is for one-time use and it should be deleted after your initial set up of rpm/yum env (yum install yum).

Everything you need is to delete \tmp\yumbt, search for all python.exe executable files, delete all of them that are in PATH but are not in \usr\bin, and you're done.

The python.exe executable that is in \usr\bin are most probably the right one, of version 2.7. After you delete all the garbage python interpreters you have on the file system accidentally, just re-check you're left with 2.7 by python --version. It just should be okay.

If it's still isn't for some reason, like you've modified the files in \usr, then a simple yum update && yum reinstall python will work.

R.M. Klippstein

  • Sr. Member
  • ****
  • Posts: 305
  • Karma: +3/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #20 on: August 23, 2014, 11:25:41 pm »
Hi Boris, this is turning into an unending mess!I think the basic problem is this: As soon as \tmp\yumbt  is deleted yum is GONE, Gives The system cannot find the path specified! Also there is no config.sys.yum created.The only way to run yum is to re-install the wpi. Re-installing, like you recommended, and then running "yum update && yum reinstall python" looks great untill I ran python --version which said: The system cannot find the file python27 (no python27 dll? in \usr).  I downloaded a python27.dll file off the Internet but it wouldn't load in a os2 enviorment. With a workable python27.dll it might work.
Looks like yum install is not creating the necessary run files so that the yumbt directory can be deleted. I verified this by trying it in both partitions. Yum seems to work fine (except for installing python)  as long as \tmp\yumbt isn't removed.

klipp

ivan

  • Hero Member
  • *****
  • Posts: 1363
  • Karma: +15/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #21 on: August 24, 2014, 01:14:50 am »
Hi Klipp,

We run Python2.7.2 here and all we did was to download the zip from Paul's site and unzip it to the programming directory (we use it to produce scripts for control and management of clients servers).

Maybe you could do the same and then move the unzipped directories to where you need them.

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #22 on: August 24, 2014, 01:53:06 am »
Hi Boris, this is turning into an unending mess!I think the basic problem is this: As soon as \tmp\yumbt  is deleted yum is GONE, Gives The system cannot find the path specified! Also there is no config.sys.yum created.The only way to run yum is to re-install the wpi. Re-installing, like you recommended, and then running "yum update && yum reinstall python" looks great untill I ran python --version which said: The system cannot find the file python27 (no python27 dll? in \usr).  I downloaded a python27.dll file off the Internet but it wouldn't load in a os2 enviorment. With a workable python27.dll it might work.
Looks like yum install is not creating the necessary run files so that the yumbt directory can be deleted. I verified this by trying it in both partitions. Yum seems to work fine (except for installing python)  as long as \tmp\yumbt isn't removed.

klipp

As I said in the beginning, your rpm/yum installation is completely screwed, and you do random things, which doesn't help it.

It's good you've reinstalled it from scratch, it's gonna be clearer now a lot.

I can't see what's wrong again. It should work perfectly. Is %UNIXROOT% appropriate? Have you rebooted? Several times? After you did yum install yum? Is \usr\lib in your LIBPATH in CONFIG.SYS? Rebooted? Do you have the \tmp\yumbt directory? Is there a python27.dll file in \usr\lib?

If for some very odd and stupid reason there is no python27.dll file in \usr\lib, which is provided by the python-libs-2.7.6-10.oc00.i386 package (installed automatically as a dependency of python-2.7.6-10.oc00.i386 during yum update), you can still download it from my OS/2 DLLs search service (direct link), or download the package by yourself and extract its contents by rpm2cpio package.rpm | cpio -idmv and then place it into \usr\lib.

!!! PLEASE TRIPLE-RE-CHECK YOU HAVE ONLY ONE PYTHON.EXE EXEMPLAR !!!

P. S. It seems for me that some significant part of OS/2 users are under-qualified to use rpm/yum correctly.
« Last Edit: August 24, 2014, 02:01:31 am by Boris »

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #23 on: August 24, 2014, 01:55:43 am »
Hi Klipp,

We run Python2.7.2 here and all we did was to download the zip from Paul's site and unzip it to the programming directory (we use it to produce scripts for control and management of clients servers).

Maybe you could do the same and then move the unzipped directories to where you need them.

Don't use Paul's software in conjunction with netlabs rpm/yum env's if you don't perfectly know what are you doing, it's generally not quite compatible (just because Paul doesn't care to be compatible with it, it doesn't mean his software is bad).

Python is quite a core component of the env, if you break it, you will need to recover by hand, as yum is broken too. That's not a problem if you know what're you doing.
« Last Edit: August 24, 2014, 01:59:07 am by Boris »

R.M. Klippstein

  • Sr. Member
  • ****
  • Posts: 305
  • Karma: +3/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #24 on: August 24, 2014, 04:00:03 am »
This "Under qualified to use rpm/yum" os2 user corrected the problem by installing a working python27.dll in \usr\lib

klipp

ivan

  • Hero Member
  • *****
  • Posts: 1363
  • Karma: +15/-0
    • View Profile
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #25 on: August 24, 2014, 10:55:35 am »
Sorry Boris, but there are a lot of us that DO NOT have RPM/YUM on our computers for various reasons, one of them being commercial usage and another being that we don't like the arbitrary way it dumps things on the hard disk, so installing Paul's software is not a problem.

dbanet

  • Guest
Re: Compiling XPCOM (xpidl) fails -- need help!
« Reply #26 on: August 24, 2014, 11:28:28 am »
Sorry Boris, but there are a lot of us that DO NOT have RPM/YUM on our computers for various reasons, one of them being commercial usage and another being that we don't like the arbitrary way it dumps things on the hard disk, so installing Paul's software is not a problem.

I'm not talking about the case when you don't use rpm/yum, please re-read my comment.