libxml2 v2.11.5

[andreas]

Just found out that the new version of libxml2 caused problems with my Open Office (getting killed as soon as trying to open any document)

[David McKenna]

No trouble with it here... what are you trying to do that kills it?

Regards,

[andreas]

when i tried to open a file directly i could just see the loading process before OO went to nowhere. opening soffice.exe showed the menue of the program, but as soon as i chose an option for opening a module the program collapsed.
PM-dll didn't show any missing dll. new install of OO didn't help.
But downgrading livxml2 did.

[KO Myung-Hun]

Hi/2.

Any error reports ? such as popuplog.os2, exceptq ?

[andreas]

in popuplog.os2 I find:
SYS2070 PID 00cc TID 0001 Slot 00c3
C:\Programs\APACHEOFFICE.4\PROGRAM\SOFFICE.BIN
XML22->LIBCN0.2026
182

[Tom]

in popuplog.os2 I find:
SYS2070 PID 00cc TID 0001 Slot 00c3
C:\Programs\APACHEOFFICE.4\PROGRAM\SOFFICE.BIN
XML22->LIBCN0.2026
182

That suggests that your installed version of libc is not new enough. Which version do you have installed?
The most recent version is libc-0.1.12-1.oc00.pentium4.rpm

[andreas]

ic. my version is 0.1.9.1 i686, update to pentium4 was not possible with YUM/ANPM. Maybe need to install the package manually..

[Dave Yeo]

ic. my version is 0.1.9.1 i686, update to pentium4 was not possible with YUM/ANPM. Maybe need to install the package manually..

Did you try updating to 0.1.9.1 pentium4 first by right clicking on libc and choosing "Get specific release"?
Need to do similar with libcx too.

[andreas]

oh, i didn't know about that option.
My os/s-system is not connected with the internet. i have a repo-folder with the packages only on my hard disc.
Will try to install 0.1.9.1 pentium4 over the i686-version. Does it work with yum/install ?

[Dave Yeo]

I've never tried it. What I did when my internet connection was bad was have a local repository and use that.

[Tom]

ic. my version is 0.1.9.1 i686, update to pentium4 was not possible with YUM/ANPM. Maybe need to install the package manually..

In ANPM, use the menu YUM --> Platform to add pentium4 (if it is not already listed). After that, move the line pentium4 to the top (using the buttons on the right side of the window). And restart ANPM (maybe not needed, but it won't hurt).

After that, you should be able to update a package from i686 to pentium4.

[andreas]

ic. my version is 0.1.9.1 i686, update to pentium4 was not possible with YUM/ANPM. Maybe need to install the package manually..

In ANPM, use the menu YUM --> Platform to add pentium4 (if it is not already listed). After that, move the line pentium4 to the top (using the buttons on the right side of the window). And restart ANPM (maybe not needed, but it won't hurt).

After that, you should be able to update a package from i686 to pentium4.

oh i did that from before.

Tried to install old pentium4-libc-version over old i686-version. didn't work - neither with ANPM nor with YUM

Getting message "incompatible platform - replace operation is not supported for local files"

[ivan]

Excuse me for butting in but what is the difference between the i686 to pentium4 versions of any DLL and why is there the two versions?  All my computers have AMD Ryzen 3 processors and I have the RPM/YUM program but don't use it - if I need a DLL I just download the package and unpack it locally, extract what is needed and dump the other junk included with it.

[andreas]

i have no idea what the difference is, but  - as you can read in the thread - the new version of libxml2 caused a problem wth OpenOffice - appearently due to the older version of libc.
I can use OO by downgrading.
But in general i have a problem to change some installed i686-packages to pentium4-packages...

[Dariusz Piatkowski]

ivan,

Excuse me for butting in but what is the difference between the i686 to pentium4 versions of any DLL and why is there the two versions?

The packages are built with CPU specific optimizations, and those will differ between i686 and P4. In particular for the P4 CPUs the focus is on using the MMX, SSE and SSE2 instruction set.

Keep in mind that this whole approach is applicable to multiple GCC compilation options, be it '-mtune' or '-march', and there are always the more generic options that just focus on generating either FASTER code, or SMALLER code.