Displaying 20 results from an estimated 5000 matches similar to: "wine -v error"
2005 Feb 21
2
Execution of WineTools with Wine version 20041201 on RedHat 9
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
2005 Feb 24
1
[Fwd: Re: Execution of WineTools with Wine version 20041201 on RedHat 9]
Joachim, apologies again for bothering you,
but after I sent the email below, I managed to link Xdialog in /usr/bin
to /usr/local/Winetools to get Winetools to work (I'm still getting used
to the 'peculiarities' of linux!). I went through the Base Setup
procedure as advised, and it seemed to work 'mostly OK', but I think
there is a problem with my glibc as you advised - a
2005 Feb 22
0
unsucribe
>From: wine-users-request@winehq.org
>Reply-To: wine-users@winehq.org
>To: wine-users@winehq.org
>Subject: wine-users digest, Vol 1 #2023 - 12 msgs
>Date: Tue, 22 Feb 2005 02:26:01 -0600
>MIME-Version: 1.0
>Received: from wine.codeweavers.com ([198.144.15.226]) by
mc1-f4.hotmail.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 22 Feb 2005
00:34:01
2005 Feb 07
1
Winetools not working on my desktop
So, I installed Wine 20050111 and Winetools 2.1 on my desktop which is
a P4 HT 3.4ghz ICH6 chipset based box. Redhat seems to function just
fine on it, and I'm running the latest stable SMP Kernel.
My problem is included in the following test. When I launch WineTools,
it starts complaining about not being able to create directories and
the such, but I'm running this as root (I can hear
2005 Mar 06
1
wine wont' run
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
2006 Jun 07
1
winecfg failure (GLXBadContext?)
This is on Fedora FC5 x86_64
rpm -q wine
wine-0.9.14-1.fc5
winecfg
wine: creating configuration directory '/home/nbecker/.wine'...
X Error of failed request: GLXBadContext
Major opcode of failed request: 143 (GLX)
Minor opcode of failed request: 5 (X_GLXMakeCurrent)
Serial number of failed request: 166
Current serial number in output stream: 166
wine: wineprefixcreate failed
2008 Apr 28
6
RHEL5 - Download via EPEL was success but with errors
Errors keep coming back when I try to configure WINE. This is on RHEL5, and I do not have sound support installed (if it makes any difference).
[root at dev02 ~]# winecfg
wine: creating configuration directory '/root/.wine'...
ALSA lib seq_hw.c:457:(snd_seq_hw_open) open /dev/snd/seq failed: No such file or directory
Could not load Mozilla. HTML rendering will be disabled.
X Error of
2006 Mar 30
1
GLX Problem
Hello,
after a fresh install on and amd64, nvidia, linux 2.6.16, i get this
error after starting wine:
bowman@discovery ~ $ winecfg
wine: creating configuration directory '/home/bowman/.wine'...
X Error of failed request: BadAlloc (insufficient resources for
operation) Major opcode of failed request: 144 (GLX)
Minor opcode of failed request: 3 (X_GLXCreateContext)
Serial number
2007 Mar 19
1
error, wine in linux
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...
2007 Mar 19
1
"BadWindow" error w/ NV-GLX
Running wine 0.9.28, Ubuntu Edgy. nvidia 6800GT, dual-LCD w/ xinerama,
nv-glx driver.
Running winecfg always returns:
wine: creating configuration directory '/home/myusername/.wine'...
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 144 (NV-GLX)
Minor opcode of failed request: 4 ()
Resource id in failed request: 0x24a
Serial
2008 May 01
5
winecfg
:( i cant get the wine config to open. I have tryed uninstalling reinstalling but no luck. this is what i get when i type in winecfg
tom at tom-desktop:~$ winecfg
wine: creating configuration directory '/home/tom/.wine'...
Could not load Mozilla. HTML rendering will be disabled.
err:seh:setup_exception_record stack overflow 28 bytes in thread 0009 eip 7e07e153 esp 00231314 stack
2006 Mar 28
3
winecfg not creating ~/.wine/config file
Hello,
after a fresh install, wine 0.9.10 wont start while giving the following errors:
flo@HAL2000 ~ $ wine
can't create key_t for shm: No such file or directory
wineserver: chdir /home/flo/.wine : No such file or directory
winecfg also wont start:
flo@HAL2000 ~ $ winecfg
wine: creating configuration directory '/home/flo/.wine'...
Can't open configuration file
2005 Jan 26
0
Unhandled exception c0000005 after fresh rpm install on FC3 x86_86
I got stuck with Wine on 64-bit Fedora Core 3. I can not remember when
it happened (I was using wine few times a month), but somehow wine
stopped working. I have removed all rpms and installed wine20050111-1fc3
rpm but when I start wine for the first time as a "normal" user, it
fails with the following:
wine: creating configuration directory '/home/robert/.wine'...
wine:
2004 Dec 17
2
wine error after installation
After installing wine, on starting wine, I get the following error. How to
resolve this?
err:module:load_builtin_dll failed to load .so lib for builtin
L"gdi32.dll": libstdc++.so.6: cannot open shared object file: No such file
or directory
err:module:import_dll Loading library gdi32.dll (which is needed by
L"c:\\windows\\system\\user32.dll") failed (error c000007a).
2005 Feb 11
1
Desktop malfunction - Wine
So, this is the capture I got from running Wine alone on my desktop.
Fedora Core 3, Wine 20050111, without Winetools. This is using the
latest stable SMP kernel (don't have version number off the top of my
head, -740 or something like that). I may have left out numerous dubious
details. If so, please let me know...
FWIW, this is installed off the latest RPM.
>>>
2013 Jan 22
0
[LLVMdev] Embed LLVM/Clang in our project
This is just standard behavior of the Python interpreter. The files
are just a cache (it is not the sources being modified) and also won't
be written if the source tree is made read only, and shouldn't cause a
problem in practice.
- Daniel
On Jan 22, 2013, at 0:02, Duncan Sands <baldrick at free.fr> wrote:
> I would have expected the .pyc files to go in the objects directory.
2019 Jun 30
2
orc vs mcjit
yeah i m concerned about jit compilation time..
On Sun, Jun 30, 2019 at 12:57 PM Praveen Velliengiri <
praveenvelliengiri at gmail.com> wrote:
> Yes I think so.. Could you please tell me in which context (compile time
> improvement)? That is whether you are interested in knowing whether having
> ORC instead of MCJIT, will increase your LLVM Build time or you are
> concerned
2005 Feb 22
4
Can't get wine to work on amd64
My system:
AMD Athlon 64 3500+ Winchester core
Asus A8N-SLI Deluxe
1 GB Corsair DDR-400
Nvidia 6600GT 128MB
(2) 74 GB SATA WD Raptors
I'm running gentoo with the 2.6.10-gentoo-r7 kernel. My root partition
is on a linux software raid.
Problem:
After many hours of research I learned that I can't compile wine on my
64-bit platform, i have to download a precompiled binary for a 32-bit
2012 May 21
2
[LLVMdev] lli unable to resolve symbol _ZNKSt3__16locale9use_facetERNS0_2idE in bitcode
Ashok Nalkund wrote:
> Resending, any pointers? I demangled the symbol and it turns out to be:
> std::__1::locale::use_facet(std::__1::locale::id&) const
My guess is that you've got a .bc file produced on a mac using libc++
(hence the ::_1 part) and you're trying to run it on linux with
libstdc++ (which doesn't use inline namespaces, the '::_1::' part). That
2012 May 23
0
[LLVMdev] lli unable to resolve symbol _ZNKSt3__16locale9use_facetERNS0_2idE in bitcode
Ashok Nalkund wrote:
>
> Resending :(. Any pointers?
Fundamentally the issue is that the system linker is supposed to define
__dso_handle when linking, but since there is no system linker between
your build of the .bc files and running lli, nobody has defined it.
It seems reasonable to me that lli should define __dso_handle if it's
declared in the module.
You could module