LIBWINE.SO.1 RPM FREE DOWNLOAD

Personal Menu Create account Log in. Is there a solution other than chroot with full wine and cups install. I will try to find some of the posts for people who tried to get this working. One issue with extremely stable distros like CentOS is that your libraries may be older versions than those required by the newest wine release or the tip of the WineHQ git tree. Is it because 32bit wine cannot talk to 64bit CUPS? Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Thu Nov 25, 9:

Uploader:	Mezim
Date Added:	10 July 2004
File Size:	65.41 Mb
Operating Systems:	Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads:	34522
Price:	Free* [*Free Regsitration Required]

Personal Menu Create account Log in.

- The search engine for Linux rpm and Debian packages - -

If you want a WoW64 version, that should be possible too. This repo contains updates and extra packages backported from Fedora to more stable Red Hat-based distros. Join our community today!

Tue Apr 12, Once a i version of the EPEL becomes available, you r;m be able to follow the same instructions above to install a fully functional wine package libwine.soo.1 CentOS 7 and its siblings. Fri Mar 25, 7: According to user "gcomes" on the CentOS forumsas of Feb. Once you do have the source repos enabled, the actual installation should take only a single command:. Starting with release 7 and the Subscription Manager system, you'll need to activate both the optional and extras repos with subscription-manager.

Wed Sep 08, Share your knowledge at the LQ Wiki. Page Discussion View source History.

The same lack of bit libraries mentioned above is still a potential obstacle. Retrieved from " https: The time now is Holding 0x55e2a, level 3.

CentOS/RHEL

Gentoo rulez, peace for all your great help. For any work with packages, you'll definitely want to be familiar with your package manager.

Having a problem logging in? Up through release 7, the standard package manager has been yumbut with Fedora adopting the leaner, meaner dnf package manager, there's a good chance this will be increasingly preferred, possibly even the default in release 8. Sat Sep 11, If you do build wine from source, it's strongly suggested that you don't install it into your system but rather run it from within the build-directory.

However, remember that you should never build wine as root or a super-user, especially on Red Hat-like distros where it can particularly wreak havoc.

Another method is to use a build-dependency tool for your package manager. I love you guys. Rather than sudoa common convention in Red Hat and related distros has been to acquire super-user lihwine.so.1 with su -lthen carry out the necessary actions.

One issue with extremely stable distros like CentOS is that your libraries may be older versions than those required by the newest wine release or the tip of the WineHQ git tree.

RPM resource libwine.so.1()(64bit)

Fedora This forum is for the discussion of the Fedora Project. At the time of this writing, EPEL 7 still has no bit packages including wine and its dependencies. Open Source Consulting Domain Registration. Thinking this is here for months!

Display posts from previous: Registration is quick, simple and absolutely free. Print setup dialog in win apps shows no printers, and I'm getting errors like: If your distro does include a wine package by default, you should be able to use the above install command without even enabling the EPEL.

For the same reasons that a functional wine package in EPEL 7 is still a no-go, it used to be a labyrinth trying to build wine on CentOS 7.