OS/2, eCS & ArcaOS - Technical > Programming

Creating a RPM package for PMDLL

<< < (5/6) > >>

Lars:
One Thing is clear by now: you have a screwed installation of yum/rpm.
I suggest you redo the install of yum/rpm via ANPM, if possible. Possibly also python.

Martin Iturbide:
Hi

I reset the VM to a previous snapshot where RPM/YUM worked fine.
I created PMDLL rpm and install it again, but it keeps stalling at the wps-object.exe process and slowing down the PM desktop. (CPU does not spike). If I stop the installation procedure, the desktop remains unreliable (a reboot was required). I'm attaching the specs file.

If I remove the ";ASSOCTYPE=Executable,Dynamic Link Library;ASSOCFILTER=*.EXE,*.DLL;", the rpm package works perfectly, but does not associate the type and filters of course.

Any other experience trying ASSOCTYPE= and ASSOCFILTER= with RPM?

Regards

Martin Iturbide:
Hi

I also tried a different sample, since Ivan posted the Task Buster binaries. So I tried to create a rpm package for it.

But I may be missing something on the .spec, since the installer tells me it required BUSTER.DLL and I had included it on the package.

This is the error I get:


--- Code: ---[C:\HOME\RPMBUILD\RPMS\I686]yum install TaskBuster-2.00-1.oc00.i686.rpm
Setting up Install Process
Examining TaskBuster-2.00-1.oc00.i686.rpm: TaskBuster-2.00-1.oc00.i686
Marking TaskBuster-2.00-1.oc00.i686.rpm to be installed
Resolving Dependencies
--> Running transaction check
---> Package TaskBuster.i686 0:2.00-1.oc00 will be installed
--> Processing Dependency: buster.dll for package: TaskBuster-2.00-1.oc00.i686
--> Finished Dependency Resolution
Error: Package: TaskBuster-2.00-1.oc00.i686 (/TaskBuster-2.00-1.oc00.i686)
           Requires: buster.dll
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest

--- End code ---

Any tips on how I tell the rpm installer that BUSTER.DLL is already included there?

Regards

ivan:
Hi Martin,

One thing I found with the Task Buster program is that both the exe and dll need to be in the same directory.  I don't know if that will help, I'm a hardware engineer that employed others to do the software.

Lars:
Martin's problem is not a runtime problem but an installation problem.
Nonetheless, if what you say is true, that also means that Martin will have to change the spec file accordingly.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version