similar to: Wine / Whine

Okay went to: http://wine.dataparty.no/ form there downloaded the rpm, http://wine.dataparty.no/rpm/unstripped/wine-cvs-unstripped-013001-1.i386.rpm downloaded the config file and worked through the install guide. I edited the config file to mirror my window setup: c:\ = \mnt\c d:\ = \temp e:\ = \web f:\ = \documents g:\ = \music h:\ = \mnt\cdrom i:\ = \mnt\zip then as a check did $wine -v and

Spoke too soon... running the inst combine pass does seem to resolve the linker/inlining issue. But the resulting code fails to run correctly. I was expecting the same result that I get when running with unstripped modules, that is passing test runs. When it still failed, I guessed the failure mode to be the same, but it isn't. Not sure WHAT to make of this...

Eli, Thanks. I don't think it's a bug in the linker, really… it's required to treat (stripped) opaque types as different, since it really has no way to know if the caller and the callee really are referring to the same thing… though it then seems to turn right around and do exactly that by inserting the bitcast. ;-) (That does come from the linker.) That the linker 'works

On Fri, Nov 9, 2012 at 3:58 PM, Relph, Richard <Richard.Relph at amd.com> wrote: > Eli, > Thanks. I don't think it's a bug in the linker, really… it's required to treat (stripped) opaque types as different, since it really has no way to know if the caller and the callee really are referring to the same thing… though it then seems to turn right around and do exactly that

Hi! I was running lintian on our package... Among the copious errors and warnings there are: W: xen-utils: manpage-has-errors-from-man usr/share/man/man1/xm.1.gz 668: warning: can't find numbered character 160 Should we try to fix this, perhaps? E: xen-hypervisor-pae: unstripped-binary-or-object ./boot/xen_pae-syms-3.0.1 E: xen-hypervisor: unstripped-binary-or-object ./boot/xen-syms-3.0.1

I downloaded wine-010708-stripped.tar.bz2 from the web. (I'm running RedHat 6.2 on a Pentium 133 with 48mb of RAM and a 10gb hard drive which is not recognized by the BIOS. It was running Window$ using Maxblast EZ-Bios software overlay - until that software went south. Last time, for some reason, it fixed itself when I booted to Linux (using my boot floppy) and ran lilo - I've no idea

Question: How to kill a Windows application that runs with wine? I have installed new stable version of wine for Debian. Then the Windows application starts OK but hangs for some reason (its the application logic fault). However I can't see any way to close the application window or to kill the application. I tried as in documentation: # wineserver -k bash: wineserver: command not found I

Hi, I have just compiled and installed wine-20011004, and I have go the following problem when I start Wine: wine client error:0x806bb68: version mismatch 54/59. Your wineserver binary was not upgraded correctly, or you have an older one somewhere in your PATH. Or maybe the wrong wineserver is still running? I have build and install it with wineinstall. I have remove the previous version. Any

Hi, I've installed Wine version 20041201 on RedHat 9 and Winetools 210-jo, but when I try to execute Winetools (by typing wt2 on shell (as a user, not root), I just get all the error messages below. Any suggestions as to what I'm doing wrong, please? Best regards, Andy [andrew@Atlas2 andrew]$ wt2 bash: wt2: command not found [andrew@Atlas2 andrew]$ cd /usr/local/winetools [andrew@Atlas2

Hi! When I'm trying to run wine (I've tried many compilations), I got something like that: wineserver: /root/.wine/config is not a valid registry file Why I'm not using /etc/wine.conf, /usr/etc/wine.conf or /usr/local/etc/wine.conf? Because wineserver wants only $HOME/.wine/config... When I delete this file wineserver 'says' that I don't have configuration file (even

Thank you for doing this. The size issue is actually a big concern for me. So this is step in the right direction. Two other points to consider, that would help us: 1) When using -fcoverage-mapping, some of the information is emitted in the text section. This is creating linking issues with very large files. It does not seem any of this information should necessarily be in the text

Any guess's as to whats going on here? A new from source compile/install vic@zeus:/usr/local/bin$ wine wine: creating configuration directory '/home/vic/.wine'... Unknown option '-w' usage: wineserver [options] options: -d<n> set debug level to <n> -p make server persistent -h display this help message -s server will use shared memory

I hope i am posting this to the right list. Specs: FreeBSD 4.x Wine 20011108 -- FreeBSD ports version Me == Newbie I am trying to configure wine manually because the package i recieved does not include winesetup. I configured the drives to suit my setup and left the rest as the defaults. When i try to start wine with "wine program.exe" i get this error:

I'm trying to install WINE on my newly installed Mandrake v8.2 system. The error I receive is "file /usr/bin/expand from install of wine-cvs-unstripped-061102-1 conflicts with file from package textutils-2.0.17-7mdk" Any input would be greatly appreciated. Thanks, Josh

On Sun, 30 Apr 2006, Aristid Breitkreuz wrote: > I am, as said in the subject, new to this list. I have not actually used > LLVM, I tried with an older version but failed. Recently I noticed that > 1.7 came out and looked at the release notes. And there was something > that stroke me: llvm-g++ adheres to the IA64 ABI but _not for > exceptions_. I was not able to find information why

First - Wine is great. I love it totally. To login into a company website I have to use IE6 - Firefox is not handling the Web Site due to some reglementations. IE6 runs fine and there are NO problems. Only after exit, the Wineserver keeps running and takes away a lot CPU Power. I can stop it manually (System Monitor -> Process. Right Click and I can stop it (and it relieves the Power from the

hello group, when I run wine under slackware 11 it gives me this error in the terminal wine: creating configuration directory '/root/.wine'... wine: Unhandled page fault on write access to 0x003ffd80 at address 0x608f7103 (thread 0009), starting debugger... wine: Unhandled page fault on write access to 0x003ffd80 at address 0x608fc103 (thread 000b), starting debugger...

It's telling me maybe my wineserver crashed. How do I restart it? Logging in and out as user, in and out as root, and rebooting did nothing. I've had to resort to using (shudder) a Win dose to use Agent again. I HATE that! Help me, please, to restart my wineserver. Cybe R. Wizard -- Unofficial "Wizard of Odds", A.H.P. Original PORG Water Wizard, R.P. Ship's "Other

Hi, I have followed the Installation Guide on the winehq website, but the "bz" files they reference in the guide are not there. All I could download was the "unstripped-latest-version" rpm files, which I did. Through following the installation instructions, I copied and renamed the files, as well as changed the attributes, but all I come up with when running wine -v is

Hi, Is it possible to have a single Wineserver which can manage wine processes belonging to different users. If not, please tell me the reason. I'm trying to reduce the memory occupied by wineserver in a multiuser system, for instance: a server shared by 100s of users. In this case, it is better to have a single wineserver which can manage wine processes of multiple users (1 process instead