http://bugs.winehq.org/show_bug.cgi?id=26088
Summary: WINE fails to compile when configured with
--without-pthread
Product: Wine
Version: 1.3.13
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: silas-wine(a)flatline.org.uk
After doing ./configure --without-pthread and make, I get compile errors as
below.
I need without-pthread because I'm compiling for old hardware that's running a
2.4 Linux kernel and cannot be upgraded to 2.6.
Wine 1.2 and Wine 1.3.13 won't compile, but Wine 1.0 compiles OK (although I
have not yet been able to test the resulting binary on the target kernel).
loader.o(.text+0x5748): In function `attach_process_dlls':
/wine-1.3.13/dlls/ntdll/loader.c:2532: undefined reference to `pthread_sigmask'
server.o(.text+0x382): In function `wine_server_call':
/wine-1.3.13/dlls/ntdll/server.c:289: undefined reference to `pthread_sigmask'
server.o(.text+0x3ac):/wine-1.3.13/dlls/ntdll/server.c:292: undefined reference
to `pthread_sigmask'
server.o(.text+0x41d): In function `server_enter_uninterrupted_section':
/wine-1.3.13/dlls/ntdll/server.c:302: undefined reference to `pthread_sigmask'
server.o(.text+0x477): In function `server_leave_uninterrupted_section':
/wine-1.3.13/dlls/ntdll/server.c:313: undefined reference to `pthread_sigmask'
server.o(.text+0x15f8):/wine-1.3.13/dlls/ntdll/server.c:994: more undefined
references to `pthread_sigmask' follow
thread.o(.text+0xd04): In function `exit_thread':
/wine-1.3.13/dlls/ntdll/thread.c:360: undefined reference to `pthread_join'
thread.o(.text+0xdeb): In function `start_thread':
/wine-1.3.13/dlls/ntdll/thread.c:393: undefined reference to `pthread_sigmask'
thread.o(.text+0x10b4): In function `RtlCreateUserThread':
/wine-1.3.13/dlls/ntdll/thread.c:477: undefined reference to `pthread_sigmask'
thread.o(.text+0x11d2):/wine-1.3.13/dlls/ntdll/thread.c:501: undefined
reference to `pthread_attr_setstack'
thread.o(.text+0x121b):/wine-1.3.13/dlls/ntdll/thread.c:505: undefined
reference to `pthread_create'
thread.o(.text+0x1249):/wine-1.3.13/dlls/ntdll/thread.c:513: undefined
reference to `pthread_sigmask'
thread.o(.text+0x12dd):/wine-1.3.13/dlls/ntdll/thread.c:524: undefined
reference to `pthread_sigmask'
collect2: ld returned 1 exit status
winegcc: gcc failed
make[1]: *** [ntdll.dll.so] Error 2
make[1]: Leaving directory `/wine-1.3.13/dlls/ntdll'
make: *** [dlls/ntdll] Error 2
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #88 from Hans Leidekker <hans(a)meelstraat.net> 2011-02-13 03:35:05 CST ---
(In reply to comment #87)
> Which HOME version are you looking at? I don't recall seeing this key used, but
> it's been a while since I looked into it. Googled the GUID, and it relates to
> disk things, so I could be mistaken.
My HOME version is 2.8.0.2146. 53f56307-b6bf-11d0-94f2-00a0c91efb8b is
the 'Disk Device' interface class. The key is used indirectly by HOME via
a call to SetupDiGetClassDevs.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6254
--- Comment #70 from James McKenzie <jjmckenzie51(a)earthlink.net> 2011-02-12 22:16:54 CST ---
Please disregard my last comment. I had installed riched20 through winetricks
and had not set back the global defaults.
However, the main font for e-Sword DOES change with Options -> Main Font. This
changes the font for the ENTIRE program. And the EM_FORMATRANGE fixme messages
still appear. Will have to change the message for this as it says "stub" and
it should say "Not Implemented."
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6254
--- Comment #69 from James McKenzie <jjmckenzie51(a)earthlink.net> 2011-02-12 21:42:51 CST ---
Also, text is properly formatted in the Main text window for e-Sword and the
print preview function appears to work properly.
Wine was build using the osxwinebuilder application created by R. Woodshall and
used Wine tar.bz2 downloaded from a Wine mirror.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=6254
--- Comment #68 from James McKenzie <jjmckenzie51(a)earthlink.net> 2011-02-12 21:40:56 CST ---
Errors no longer occur with Wine 1.3.13 although there is no proper
implementation in riched20 for the EM_FORMATRANGE function.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=25706
Summary: Crash durring EVE Online starting
Product: Wine
Version: 1.3.10
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mrkaczor(a)interia.pl
After recent EVE Online and wine update
"
system.reg is not a valid registry file
userdef.reg is not a valid registry file
user.reg is not a valid registry file
err:ole:CoGetClassObject class {9a5ea990-3034-4d6f-9128-01f3c61022bc} not
registered
err:ole:CoGetClassObject no class object {9a5ea990-3034-4d6f-9128-01f3c61022bc}
could be created for context 0x1
fixme:heap:HeapSetInformation 0x480000 0 0x33fc50 4
"
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #87 from Michiel Salters <msalters(a)xs4all.nl> 2011-02-12 18:12:36 CST ---
(In reply to comment #86)
> 1. Navigate to this key:
> HKLM\System\CurrentControlSet\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
> and find the subkey that has TomTom somewhere in the name. Export it.
Which HOME version are you looking at? I don't recall seeing this key used, but
it's been a while since I looked into it. Googled the GUID, and it relates to
disk things, so I could be mistaken.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=8571
--- Comment #9 from bitinerant <minimalpair(a)gmail.com> 2011-02-12 16:44:01 CST ---
Created an attachment (id=33267)
--> (http://bugs.winehq.org/attachment.cgi?id=33267)
log of install attempt - Rosetta Stone v2.1.5.3Asms under Wine 1.2.2
(In reply to comment #8)
> Is this still an issue in current (1.2-rc2 or newer) Wine?
Yes, although the symptoms are different. I tried installing Rosetta Stone
v2.1.5.3Asms under Wine 1.2.2. Log attached.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.
http://bugs.winehq.org/show_bug.cgi?id=7711
--- Comment #86 from Hans Leidekker <hans(a)meelstraat.net> 2011-02-12 15:00:24 CST ---
(In reply to comment #85)
> Well, Renault cars don't come with long USB cords. It's kind of logical that
> they use another mechanism for updates (SD card). But a ONE can and is detected
> via USB. See my earlier post, HOME is spelunking the USB bits of the registry.
Yes, I found an alternative workaround that involves copying registry
entries:
0. Attach the device to a Windows machine.
1. Navigate to this key:
HKLM\System\CurrentControlSet\Control\DeviceClasses\{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
and find the subkey that has TomTom somewhere in the name. Export it.
2. Navigate to this key: HKLM\System\CurrentControlSet\Enum\USBSTOR
and find the subkey that has TomTom somewhere in the name. Export it.
3. Export this key: HKLM\SYSTEM\MountedDevices
and edit the reg file to contain only the value that corresponds
to your TomTom device. In my case this is \\DosDevices\\D:
4. Import the registry keys in Wine.
It's looking up a device identifier through setupapi and tries to match
it to the value found under the MountedDevices key for a particular
(removable) drive.
On Wine the relevant setupapi functions are implemented but the registry
keys they query are not populated yet when a new device is attached. And
the values under the MountedDevices key are currently filled with
the targets of the drive symlinks under ~/.wine/dosdevices instead
of device identifiers.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.