OS/2, eCS & ArcaOS - Technical > Applications
Yum can't find GCC1
Mike La Martina:
I don't use QpdfView often, but when I tried I found that pages do not render. I get black rectangles instead. I had used it successfully in the past, so I thought I should reread the Install.Os2 file, and rferun the yum installs.
yum install libc worked fine, and I updated some files.
Then next command: yum install libssp failed with SYS1804: The system cannot find the file GCC1. And it is true that there is no file gcc1* on my disk.
I was beginning to think that yum was the answer to maintenance, and now this has happened. I fail to see any thing that I have done wrone in running qpdfview or yum.
Can anyone shed some light on either the problem with yum or qpdfview.
Thanks
Mike
Mike La Martina:
I ran Pmdll against qpdfview.exe and learned that the problem with it is is also GCC1.DLL which is loaded by GCC473 which is loaded by STDCPP6.
I don't see how this could have ever worked, but I was sure that it did. :(
guzzi:
Download http://rpm.netlabs.org/release/00/zip/gcc-4_9_2_1-3_oc00.zip, copy gcc*.dll from the @unixroot\usr\lib directory in the zip to the proper location on your drive and run yum install libgcc4*. That should likely make it work again, unless you are missing more stuff.
Mike La Martina:
Thanks guzzi. The download resolved the missing gcc1.dll issue. I forgot to mention even FireFox refused to start when it was missing.
QpdfView did run, but it gave the black pages. Even now it still does not work. I did get this report from yum when I ran yum.
[I:\qpdfview]yum install libgcc4*
Running Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : libgcc-fwd-4.9.2.1-3.oc00.i386 1/14
Erasing : libgcc473-4.7.3.1-1.oc00.i386 2/14
Erasing : libgcc453-4.5.2-2.oc00.i386 3/14
Erasing : libgcc452-4.5.2-2.oc00.i386 4/14
Erasing : libgcc446-4.4.6.17-1.oc00.i386 5/14
Erasing : libgcc445-4.5.2-2.oc00.i386 6/14
Erasing : libgcc444-4.5.2-2.oc00.i386 7/14
Erasing : libgcc442-4.5.2-2.oc00.i386 8/14
Erasing : libgcc441-4.5.2-2.oc00.i386 9/14
Erasing : libgcc440-4.5.2-2.oc00.i386 10/14
Erasing : libgcc434-4.5.2-2.oc00.i386 11/14
Erasing : libgcc433-4.5.2-2.oc00.i386 12/14
Erasing : libgcc432-4.5.2-2.oc00.i386 13/14
Erasing : libgcc335-3.3.5-6.oc00.i386 14/14
libgcc335-3.3.5-6.oc00.i386 was supposed to be removed but is not!
libgcc-fwd-4.9.2.1-3.oc00.i386 was supposed to be installed but is not!
libgcc441-4.5.2-2.oc00.i386 was supposed to be removed but is not!
libgcc445-4.5.2-2.oc00.i386 was supposed to be removed but is not!
libgcc452-4.5.2-2.oc00.i386 was supposed to be removed but is not!
libgcc432-4.5.2-2.oc00.i386 was supposed to be removed but is not!
libgcc434-4.5.2-2.oc00.i386 was supposed to be removed but is not!
Installed:
libgcc-fwd.i386 0:4.9.2.1-3.oc00
Replaced:
libgcc335.i386 0:3.3.5-6.oc00 libgcc432.i386 0:4.5.2-2.oc00
libgcc433.i386 0:4.5.2-2.oc00 libgcc434.i386 0:4.5.2-2.oc00
libgcc440.i386 0:4.5.2-2.oc00 libgcc441.i386 0:4.5.2-2.oc00
libgcc442.i386 0:4.5.2-2.oc00 libgcc444.i386 0:4.5.2-2.oc00
libgcc445.i386 0:4.5.2-2.oc00 libgcc446.i386 0:4.4.6.17-1.oc00
libgcc452.i386 0:4.5.2-2.oc00 libgcc453.i386 0:4.5.2-2.oc00
libgcc473.i386 0:4.7.3.1-1.oc00
Complete!
[I:\]yum install libssp
SYS1804: The system cannot find the file GCC1.
[I:\]cd \qpdfview
So far I am having no other problems.
Dave Yeo:
The "whatever" was supposed to be installed but wasn't error is a cosmetic bug and can be ignored.
When doing a major update to what can be considered a system DLL now such as replacing all the gcc*.dlls or updating libc, you should do a reboot because otherwise the DLLs are unlocked, loaded into memory, and then replaced while the old DLL is still being used by any program that was using them.
The idea of a package manager is good. The problems are, RPM was the first Linux one and being first has weaknesses. And we have a shortage of manpower so there is only 2 or 3 people maintaining all this stuff and they're going to make mistakes as they're human. I've been beating on yum/rpm to test the new graphical front end and I have not been impressed by the underlining RPM.
The other problem is that we're running a hybrid system. Software installed by the system, warpin, yum/rpm, and users just unzipping stuff.
What happens if various GCC*.DLLs or LIBC06*.DLLs are installed in x;\ecs\dll, x:\os2\dll and @UNIXROOT\usr\lib? Depending on your libpath it can be DLL hell. Good idea to watch out for duplicate DLLs and maybe put @UNIXROOT\usr\lib in the front of LIBPATH
Navigation
[0] Message Index
[#] Next page
Go to full version