Issue 126091 - 3xwpi installation on non-networked pc fails to install dependency dlls
Summary: 3xwpi installation on non-networked pc fails to install dependency dlls
Status: UNCONFIRMED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: 4.1.1
Hardware: PC OS/2
: P3 Major (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-07 18:06 UTC by Gerry Prosser
Modified: 2017-05-25 17:19 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
result of the command 'chkdll32 soffice.exe' showing first two missing dlls (372 bytes, text/plain)
2015-02-26 14:48 UTC, Gerry Prosser
no flags Details
warpin log of 4.1.1.0 and 4.1.1.1 installations with no explicit mention of anything coming from the rpi wpi (529.85 KB, text/plain)
2015-02-26 14:50 UTC, Gerry Prosser
no flags Details
list (ordered by date) of \usr\lib includes nothing installed by YUM on the network-connected computer (8.40 KB, text/plain)
2015-02-26 14:52 UTC, Gerry Prosser
no flags Details
list (ordered by date/time) of dlls in AOO's PROGRAM folder (14.12 KB, text/plain)
2015-02-26 15:00 UTC, Gerry Prosser
no flags Details
extract from re-run warpin log showing rpm action (2.57 KB, text/plain)
2015-02-27 12:08 UTC, Gerry Prosser
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description Gerry Prosser 2015-02-07 18:06:04 UTC
OS/2 installation provides for two ways to install the pre-req/dependencies:
1. via yum/rpm, and
2. using a third .wpi file

on a non-networked laptop (ethernet and wifi chips not supported by os/2) the three wpi files were placed in a single directory, as per instructions. However, none of the dependency dlls were available to AOO once the installation was complete
Comment 1 Silvan Scherrer 2015-02-25 15:27:46 UTC
the additional wpi should have most dll. which dll are missing exactly?
it's not easy for us to know whats missing w/o this information. at least in eCS 2.1 and above most if not all should be there. beside the stuff in the wpi.
Comment 2 Gerry Prosser 2015-02-26 14:48:31 UTC
Created attachment 84545 [details]
result of the command 'chkdll32 soffice.exe' showing first two missing dlls
Comment 3 Gerry Prosser 2015-02-26 14:50:41 UTC
Created attachment 84546 [details]
warpin log of 4.1.1.0 and 4.1.1.1 installations with no explicit mention of anything coming from the rpi wpi
Comment 4 Gerry Prosser 2015-02-26 14:52:49 UTC
Created attachment 84547 [details]
list (ordered by date) of \usr\lib includes nothing installed by YUM on the network-connected computer
Comment 5 Gerry Prosser 2015-02-26 15:00:59 UTC
Created attachment 84548 [details]
list (ordered by date/time) of dlls in AOO's PROGRAM folder

I cannot give you a full list of missing dlls without knowing what the rpi.wpi contained, but by comparison with yum-updated machine I would hazard a guess that NOTHING has come out of the rpi.wpi file - the only pre-req dlls present are those installed by ECS 2.2 from the outset.
Comment 6 Silvan Scherrer 2015-02-26 18:39:17 UTC
did you select to install the rpm.wpi at all? As afair you need to select it manually.
Comment 7 Gerry Prosser 2015-02-27 12:08:08 UTC
Created attachment 84552 [details]
extract from re-run warpin log showing rpm action

a lot of dlls are now being brought in; however, chkdll32 claims that most of them are not valid os/2 dlls. gcc1 and gcc446 to name but two.
however, some dlls are still missing - libc066 for instance.
Comment 8 Gerry Prosser 2015-02-27 12:22:48 UTC
good news .... copying LIBC066 and GCC1 from working system results in chkdll32 giving all .exe files a clean bill of health .....
Comment 9 Yuri Dario 2015-03-02 13:40:40 UTC
Which is the installed CPU?
Comment 10 Silvan Scherrer 2015-03-04 09:07:15 UTC
(In reply to Gerry Prosser from comment #8)
> good news .... copying LIBC066 and GCC1 from working system results in
> chkdll32 giving all .exe files a clean bill of health .....

The libc part was an error in the wpi file. We fixed that and the next drop will be right. Could it be, that libc066 was the only dll missing? And only copy it would have solved your issue?