Sponsored Content
Full Discussion: GTK2.22 for Fedora 20
Operating Systems Linux Fedora GTK2.22 for Fedora 20 Post 302937464 by Corona688 on Thursday 5th of March 2015 01:31:13 PM
Old 03-05-2015
Forcing an RPM to install is a really bad idea. You are liable to play havoc with other gtk-using things. They may not even work, since they could easily depend on other old libraries you don't have either!

You could extract files by hand and put them somewhere under /opt/, then cause your application to load them via LD_LIBRARY_PATH="/opt/oldlibraries/" if you wanted to do it safely. I don't think they'll work, but you won't have destroyed your system.

We don't know what 32-bit versions you have already though. There may be some acceptable generic choices available in your emul package.

You could also compile statically, as suggested in the other thread.
 

8 More Discussions You Might Find Interesting

1. Linux

Need gtk2 for linux es3

I need to have the ability to read acrobat files on my Red hat linux boxes (enterprise level 3) . however acroread will not install saying i do not have gtk2 (gimp toolkit). Does anyone know where i can either get gtk2 for this linux or where i can get an acrobat reader for this flavour of linux. (1 Reply)
Discussion started by: frankkahle
1 Replies

2. UNIX Desktop Questions & Answers

gtk2-perl load error help

I write this code. It show the first dialog correctly. but, no matter i modify the code(load module by use or require, or something i think maybe error) it can't pop-up anymore. and show this warning. Thanks. (I'm sorry for my English.) Tue Mar 16 17:24:36 2010 ... (0 Replies)
Discussion started by: snyh
0 Replies

3. Programming

perl/Gtk2: issue with initializing Gtk2

hi everybody, currently i'm playing with perl and Gtk2. i've found a fairly old but nice looking example of a client/server application which is written in perl and Gtk2. the server part works perfect but i can't start the client part and keep getting following error message: $ ./client-gui.pl... (1 Reply)
Discussion started by: pseudocoder
1 Replies

4. Red Hat

fedora grub help, moving to tri boot (XP, ubuntu, fedora soemething)

I will shortly be adding a fedora flavor to my devel box. I currently have XP (installed first on an ssd), ubuntu 10.04 (installed second on the first partition of a platter drive), and I want to add either Cent or SL on the second partition of the platter drive. I will probably also want to... (0 Replies)
Discussion started by: LMHmedchem
0 Replies

5. Shell Programming and Scripting

Perl::Gtk2 on Linux --- How to Find the Default Font Being Used?

Hello All, Wasn't sure if this was the correct thread to post this under but figured it has to do with Perl and Gtk2 so why not... Anyway.. How can I find out what the Default font being used is inside a Gtk2::Widget. In this case I'm trying to figure out the font being used inside a... (1 Reply)
Discussion started by: mrm5102
1 Replies

6. Shell Programming and Scripting

Gtk2-Perl

Hai how to activate (script2)page of a note book in Gtk2-Perl when one script1 is run successfully... Thanks kiran (0 Replies)
Discussion started by: kiran425
0 Replies

7. Shell Programming and Scripting

Gtk2-Perl

Hai how to activate (script2)page of a note book in Gtk2-Perl when one script1 is run successfully... Thanks kiran (1 Reply)
Discussion started by: kiran425
1 Replies

8. UNIX for Advanced & Expert Users

32bit GTK2 application

Hi all, So, I have a 32 bit gtk2.22 application that I run flawlessly in Fedora 14. When I compile it on the 32bit machine run it on Fedora 20 64bit machine I get: (myprogram:6736): Gtk-WARNING **: Unable to locate theme engine in module_path: "adwaita", (myprogram.:6736): Gtk-WARNING **:... (15 Replies)
Discussion started by: fedora18
15 Replies
COMPAT_IBCS2(8) 					    BSD System Manager's Manual 					   COMPAT_IBCS2(8)

NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries. XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option. iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have been tested. Most programs should work, but not ones that use or depend on: kernel internal data structures STREAMS drivers (other than TCP/IP sockets) local X displays (uses a STREAMS pipe) virtual 8086 mode The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2. Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro- gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real' /etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam- ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree. Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2 program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run newly imported iBCS2 binaries without any extra work. Setting up shared libraries How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation steps). COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are typically found in /shlib and can be obtained from the following sources: SCO UNIX version 3.x (aka ODT) SCO UNIX version 5.x (aka OpenServer) SCO UnixWare Many versions of SVR4.2/x86 After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/shlib/libc_s /emul/ibcs2/shlib/libnsl_s /emul/ibcs2/shlib/protlib_s ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine the libraries required by a specific binary. After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/usr/lib/libc.so.1 /emul/ibcs2/usr/lib/libcrypt.so /emul/ibcs2/usr/lib/libndbm.so /emul/ibcs2/usr/lib/libsocket.so.1 If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about $20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files. Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally: /usr/share/examples/emul/ibcs2/ibcs2-setup [directory] You should now be set up for SCO binaries which only need standard shared libs. BUGS
The information about SCO distributions may become outdated. Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem- ber that there are no kernel sockets). 16/32/64 bit offsets may not be handled correctly in all cases. BSD
February 8, 1998 BSD
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy