Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Wine use xattr to store Windows ACL information as extended attribution, (well, it's an emulation for compatibility reason...) fracting@fracting-ThinkPad-Edge-E431: ~/.wine/drive_c/cygwin$ $ getfattr tmp # file: tmp user.DOSATTRIB user.wine.sd fracting@fracting-ThinkPad-Edge-E431: ~/.wine/drive_c/cygwin$ getfattr -n user.wine.sd tmp # file: tmp user.wine.sd=0sAQAUEAAAHBwA7AEFAAAFFQAAAOgDAAABBQAABRUBAgAAAgDsAAkBABQAAQACAAEBJAD/AR8AAQUAAAUV6AMAJACAABIAAQUAAAUVAQIAAAEAJAB/AQAAAQUAAAUVAQIAFAC/ARIAAQEAAAEAAQsUAgABAQAACxQA/wEfAAEBAAADAAALFACpABIAAQEAAAMBAAsUAKkAEgABAQAAAQA= As a temporary hack, you can remove ~/.wine/drive_c/cygwin/tmp from Linux and re-create using Linux mkdir (rather than Cygwin mkdir). Or use Linux's `fgetxattr` to clear user.wine.sd attribution of ~/.wine/drive_c/cygwin/tmp, this should make `mktemp` and gcc work. I'm still investigating what is the root cause. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
I wrote a test case demonstrate the problem at the Cygwin level.
It is almost only one line:
open("haha", O_RDWR | O_CREAT | O_EXCL, S_IRUSR | S_IWUSR); //
remember to unlink the file "haha" first
On Windows + Cygwin, this program creates a file in 0600 mode:
Administrator@short ~
$ stat haha
File: ‘haha’
Size: 0 Blocks: 0 IO Block: 65536 regular empty file
Device: 903b0bf0h/2419788784d Inode: 91760842407778598 Links: 1
Access: (0600/-rw---) Uid: (197108/Administrator) Gid: (197121/None)
Access: 2016-02-19 10:34:19.917782200 +0800
Modify: 2016-02-19 10:34:19.917782200 +0800
Change: 2016-02-19 10:34:19.917782200 +0800
Birth: 2016-02-19 09:35:08.796316900 +0800
Administrator@short ~
$ getfacl.exe haha
# file: haha
# owner: Administrator
# group: None
user::rw-
group::---
other:---
On Wine + Cygwin, this program creates a file in 0505 mode:
fracting@fracting-ThinkPad-Edge-E431 ~
$ stat haha
File: ‘haha’
Size: 0 Blocks: 0 IO Block: 65536 regular empty file
Device: 4fdc55f7h/1339839991d Inode: 36447801Links: 1
Access: (0505/-r-x---r-x) Uid: (197608/fracting) Gid: (197121/None)
Access: 2016-02-19 10:32:36.828596900 +0800
Modify: 2016-02-19 10:32:31.820695700 +0800
Change: 2016-02-19 10:32:31.820695700 +0800
Birth: 2016-02-19 10:32:31.820695700 +0800
fracting@fracting-ThinkPad-Edge-E431 ~
$ getfacl.exe haha
# file: haha
# owner: fracting
# group: None
user::r-x
group::---
group:SYSTEM:rwx
mask:r-x
other:r-x
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Hi John,
This looks like a bug in wineserver.
Cygwin strace log show an access error soon after fhandler_base::open()
[main] mktemp 111 fhandler_base::open:
(\??\C:\cygwin\tmp\tmp.kAEScb0yvo, 0x108A02)
[main] mktemp 111 __set_errno: int aclsort32(int, int,
aclent_t*):1403 setting errno 22
[main] mktemp 111 __set_errno: void* set_posix_access(mode_t, uid_t,
gid_t, aclent_t*, int, security_descriptor&, bool):269 setting errno
13
fhandler_base::open() is forwarded to NtCreateFile, but Wine
+relay,+server log show that NtCreateFile seems fine (please ignore
the difference of random file name):
0009:Call
ntdll.NtCreateFile(0060c7d4,c010,0060c7e8,0060c7e0,,0080,0007,0002,4020,,)
ret=6103a45d
0009:trace:ntdll:FILE_CreateFile handle=0x60c7d4 access=c010
name=L"\\??\\C:\\cygwin\\tmp\\tmp.BM21HIw0vU" objattr=0042
root=(nil) sec=(nil) io=0x60c7e0 alloc_size=(nil) attr=0080
sharing=0007 disp=2 options=4020 ea=(nil).0x
0009:trace:file:wine_nt_to_unix_file_name
L"\\??\\C:\\cygwin\\tmp\\tmp.BM21HIw0vU" ->
"/media/workspace/wine-cygwin-1028/dosdevices/c:/cygwin/tmp/tmp.BM21HIw0vU"
0009: create_file( access=c010, sharing=0007, create=2,
options=4020, attrs=0080,
objattr={rootdir=,attributes=0042,sd={},name=L""},
filename="/media/workspace/wine-cygwin-1028/dosdevices/c:/cygwin/tmp/tmp.BM21HIw0vU"
)
0009: create_file() = 0 { handle=00f4 }
0009:Ret ntdll.NtCreateFile() retval= ret=6103a45d
(looks identity to the good version of log, so I won't paste the good
version here)
In this case, comparing +relay,+server log between good case and bad
case doesn't expose enough information, so we might need to compare
Linux strace log from good case and bad case:
[pid 11724] write(2, 0xb7584000, 2440009: create_file(
access=c010, sharing=0007, create=2, options=4020,
attrs=0080,
objattr={rootdir=,attributes=0042,sd={},name=L""},
filename="/media/workspace/wine-cygwin-1028/dosdevices/c:/cygwin/tmp/tmp.2kmv323jLu"
)
[pid 11732] close(9
[pid 11724] <... write resumed> ) = 244
[pid 11732] <... close resumed> ) = 0
[pid 11724] open(0xa3a0e90, O_RDONLY|O_NONBLOCK|O_LARGEFILE) = 107
[pid 11724] fstat64(107, {...}) = 0
[pid 11724] fgetxattr(107, 0x80a30e8, 0xbfe5dcec, 65536) = 314
[pid 11724] close(107) = 0
[pid 11724] open(0xa3a0e40,
O_RDWR|O_CREAT|O_EXCL|O_NONBLOCK|O_LARGEFILE, 0555
By comparing to the good case, i found the above open syscall should
open the file as 0666 mode.
Related code below:
https://github.com/wine-compholio/wine-patched/blob/master/server/file.c#L408
226 if (sd)
227 {
228 const SID *owner = sd_get_owner( sd );
229 if (!owner)
230 owner = token_get_user( current->process->token );
231 mode = sd_to_mode( sd, owner );
232 }
233 else if (options & FILE_DIRECTORY_FILE)
234 mode = (attrs & FILE_ATTRIBUTE_READONLY) ? 0555 : 0777;
235 else
236 mode = (attrs & FILE_ATTRIBUTE_READONLY) ? 0444 : 0666;
I need to do more research in order to write test and figure out the
right way to fix this bug, my current guess is Wine's sd/token
emulation is not completed yet, which cause unexpected behavior.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
On Feb 14 05:10, Qian Hong wrote: > Hi John, > > Thanks a lot for testing Cygwin on Wine. > Wine Staging team and I done some Cygwin support work on Wine, we are > glad to see people using Cygwin on Wine! > However, generic speaking, if Cygwin works on Windows but breaks on > Wine, I believe the first place to report is the Wine project. You are > welcome to submit bug report to https://bugs.wine-staging.com/ and CC > me :) It's also a good idea to search msys2/cygwin before submit new > bugs: https://bugs.wine-staging.com/buglist.cgi?quicksearch=msys2_id=4821 > > If any Cygwin developers are annoyed by Wine related post then I'll feel > guilty. Not at all. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat signature.asc Description: PGP signature
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Greetings, Qian Hong! > Thanks a lot for testing Cygwin on Wine. > Wine Staging team and I done some Cygwin support work on Wine, we are > glad to see people using Cygwin on Wine! > However, generic speaking, if Cygwin works on Windows but breaks on > Wine, I believe the first place to report is the Wine project. You are > welcome to submit bug report to https://bugs.wine-staging.com/ and CC > me :) It's also a good idea to search msys2/cygwin before submit new > bugs: https://bugs.wine-staging.com/buglist.cgi?quicksearch=msys2_id=4821 > If any Cygwin developers are annoyed by Wine related post then I'll feel > guilty. > Regarding your specific problem, yes, I am able to reproduce it on > Wine, and I can confirm it works on Windows. > Could you file a bug to Wine Staging and CC me? I suggest to > investigate the Wine side first before bother Cygwin devs too much :) Pardon me for inserting my own noise, but there were cases, when running Cygwin under Wine, due to Wine's "generic" behavior some questionable Cygwin's behavior was uncovered. Thus, knowing there's a bug report is still useful. Just don't forget to report it to both sides and include reference links in your report. -- With best regards, Andrey Repin Sunday, February 14, 2016 19:31:09 Sorry for my terrible english... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Hi all, I installed wine-staging (i386) 1.9.3 and Cygwin (i386) on my Ubuntu 15.10 laptop in hopes of being able to maintain Cygwin compatibility of some software without having to actually use Windows. I've seen several difficulties, but the most serious one was that gcc would fail with various errors relating to temporary files. I was able to reduce it to a very simple test case: echo hi > $(mktemp) On a fresh Cygwin 2.3.1-1 install, this works, on a separate fresh Cygwin 2.5.0-0.2 install, this fails with bash: $(mktemp): Permission denied Permissions and ACLs on /tmp and the created temp files look OK on 2.3.1 but broken on 2.5.0. See the attached typescripts. The other problems I've had (but not fully debugged) include null dereferences from setup_x86.exe near completion of the install (this may relate to mixed usage of 2.3.0 and 2.5.1 on the same Cygwin install and messed-up permissions/ACLs), and (on both 2.3.0 and 2.5.1) postinstall scripts being unable to remove and/or write to the their temporary setup.log file and popping up console windows instead. All this works fine on a real Windows install, of course. So any of this could easily be Wine issues, but the first issue does suggest a Cygwin problem. The obvious suspect is the POSIX ACL improvements, but that's just a guess. I can help with further debug if needed. I'd have included cygcheck output for both these installs but it hangs on both of them. The installs are from the same recent download from a mirror, with the only difference being the cygwin package version. The inlined typescripts are a mess because of escape sequences so I've attached them as well. regards, --jh - Cygwin 2.3.1 - Script started on Sat, Feb 13, 2016 2:21:06 PM ]0;~ [32mcgull@minibit [33m~[0m $ uname -a CYGWIN_NT-5.2-WOW minibit 2.3.1(0.291/5/3) 2015-11-14 12:42 i686 Cygwin ]0;~ [32mcgull@minibit [33m~[0m $ echo hi > $(mktemp) ]0;~ [32mcgull@minibit [33m~[0m $ ls -l /tmp total 8 -rw--- 1 cgull None 3 Feb 13 14:21 tmp.5ZU8NzX5yV ]0;~ [32mcgull@minibit [33m~[0m $ getfacl /tmp/tmp.5ZU8NzX5yV # file: /tmp/tmp.5ZU8NzX5yV # owner: cgull # group: None user::rw- group::--- other:--- ]0;~ [32mcgull@minibit [33m~[0m $ exit Script done on Sat, Feb 13, 2016 2:21:43 PM Script started on Sat, Feb 13, 2016 2:23:40 PM ]0;~ [32mcgull@minibit [33m~[0m $ ls -l /[K[Ka /tmp total 8 drwxrwxrwt+ 1 cgull None 0 Feb 13 14:21 . drwxr-xr-x+ 1 cgull None 0 Feb 13 13:58 .. -rw--- 1 cgull None 3 Feb 13 14:21 tmp.5ZU8NzX5yV ]0;~ [32mcgull@minibit [33m~[0m $ getfacl /tmp # file: /tmp # owner: cgull # group: None # flags: --t user::rwx group::--- other:rwx default:user::rwx default:group::r-x default:other:r-x ]0;~ [32mcgull@minibit [33m~[0m $ getfacl / # file: / # owner: cgull # group: None user::rwx group::--- other:r-x default:user::rwx default:group::r-x default:other:r-x ]0;~ [32mcgull@minibit [33m~[0m $ exit Script done on Sat, Feb 13, 2016 2:24:05 PM - Cygwin 2.5.0 - Script started on Sat, Feb 13, 2016 2:22:06 PM ]0;~ [32mcgull@minibit [33m~[0m $ uname -a CYGWIN_NT-5.2-WOW minibit 2.5.0(0.294/5/3) 2016-01-28 22:13 i686 Cygwin ]0;~ [32mcgull@minibit [33m~[0m $ echo hi > $(mktemp) bash: $(mktemp): Permission denied ]0;~ [32mcgull@minibit [33m~[0m $ ls -la /tmp total 0 drwx---rwt+ 1 cgull None 0 Feb 13 14:22 . drwx---r-x+ 1 cgull None 0 Feb 13 14:11 .. -r-x---r-x+ 1 cgull None 0 Feb 13 14:22 tmp.Vqq2SdFykx ]0;~ [32mcgull@minibit [33m~[0m $ getfacl /tmp/tmp.Vqq2SdFykx # file: /tmp/tmp.Vqq2SdFykx # owner: cgull # group: None user::r-x group::--- group:SYSTEM:rwx mask:r-x other:r-x ]0;~ [32mcgull@minibit [33m~[0m $ getfacl /tmp # file: /tmp # owner: cgull # group: None # flags: --t user::rwx group::--- other:rwx default:user::rwx default:group::r-x default:other:r-x ]0;~ [32mcgull@minibit [33m~[0m $ getfacl / # file: / # owner: cgull # group: None user::rwx group::--- other:r-x default:user::rwx default:group::r-x default:other:r-x ]0;~ [32mcgull@minibit [33m~[0m $ exit Script done on Sat, Feb 13, 2016 2:24:14 PM Script started on Sat, Feb 13, 2016 2:21:06 PM ]0;~ [32mcgull@minibit [33m~[0m $ uname -a CYGWIN_NT-5.2-WOW minibit 2.3.1(0.291/5/3) 2015-11-14 12:42 i686 Cygwin ]0;~ [32mcgull@minibit [33m~[0m $ echo hi > $(mktemp) ]0;~ [32mcgull@minibit [33m~[0m $ ls -l /tmp total 8 -rw--- 1 cgull None 3 Feb 13 14:21 tmp.5ZU8NzX5yV ]0;~ [32mcgull@minibit [33m~[0m $ getfacl /tmp/tmp.5ZU8NzX5yV # file: /tmp/tmp.5ZU8NzX5yV # owner: cgull # group: None user::rw- group::--- other:--- ]0;~ [32mcgull@minibit [33m~[0m $ exit Script done on Sat, Feb 13, 2016 2:21:43 PM Script started on Sat, Feb 13, 2016 2:23:40 PM ]0;~ [32mcgull@minibit [33m~[0m $ ls -l /[K[Ka /tmp total 8 drwxrwxrwt+ 1 cgull None 0 Feb 13 14:21 . drwxr-xr-x+ 1 cgull None 0 Feb 13 13:58 ..
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
cygcheck runs OK from CMD, though not under bash. So here is that. regards, --jh Cygwin Configuration Diagnostics Current System Time: Sat Feb 13 15:36:41 2016 Windows 2003 Server Ver 5.2 Build 3790 Service Pack 2 Running under WOW64 on AMD64 Path: C:\windows\system32 C:\windows C:\windows\system32\wbem Output from C:\cygwin23\bin\id.exe UID: 197608(cgull) GID: 197121(None) 197121(None)66048(LOCAL)4(INTERACTIVE) 11(Authenticated Users) 544(Administrators) 545(Users) 4095(CurrentSession) SysDir: C:\windows\system32 WinDir: C:\windows USER = 'cgull' GNOME_KEYRING_PID = '' PAM_KWALLET5_LOGIN = '/tmp/kwallet5_cgull.socket' LANGUAGE = 'en_US:en' XDG_SEAT = 'seat0' HOSTNAME = 'minibit.glup.org' SESSION = 'gnome' XDG_SESSION_TYPE = 'x11' SHLVL = '1' LESS = '-C' QT4_IM_MODULE = '' OLDPWD = '/home/cgull/.wine/drive_c/cygwin' DESKTOP_SESSION = 'gnome' GIO_LAUNCHED_DESKTOP_FILE = '/home/cgull/Desktop/xterm.desktop' GTK_MODULES = 'canberra-gtk-module:canberra-gtk-module' XDG_SEAT_PATH = '/org/freedesktop/DisplayManager/Seat0' PAGER = 'less' LC_CTYPE = 'en_US.UTF-8' INSTANCE = '' ENV = '/home/cgull/.shrc' DBUS_SESSION_BUS_ADDRESS = 'unix:abstract=/tmp/dbus-F1rPRF5nY9' CSCOPE_VIEWER = '/home/cgull/bin/cemacs' GIO_LAUNCHED_DESKTOP_FILE_PID = '11481' LIBVIRT_DEFAULT_URI = 'qemu:///system' GNOME_KEYRING_CONTROL = '' FXTTY = '5500:5:4bf:8a3b:3:1c:7f:15:4:0:1:0:11:13:1a:0:12:f:17:16:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0:0' MANDATORY_PATH = '/usr/share/gconf/gnome.mandatory.path' IM_CONFIG_PHASE = '1' SESSIONTYPE = 'gnome-session' LOGNAME = 'cgull' GTK_IM_MODULE = '' WINDOWID = '65011727' _ = '/opt/wine-staging/bin/wineconsole' XTERM_SHELL = '/bin/bash' DEFAULTS_PATH = '/usr/share/gconf/gnome.default.path' XDG_SESSION_ID = 'c2' TERM = 'xterm' BLOCKSIZE = '1024' GNOME_DESKTOP_SESSION_ID = 'this-is-deprecated' LC_COLLATE = 'en_US.UTF-8' GTK2_MODULES = 'overlay-scrollbar' SESSION_MANAGER = 'local/minibit:@/tmp/.ICE-unix/3483,unix/minibit:/tmp/.ICE-unix/3483' GDM_LANG = 'en_US' XDG_MENU_PREFIX = 'gnome-' XDG_SESSION_PATH = '/org/freedesktop/DisplayManager/Session0' XDG_RUNTIME_DIR = '/run/user/1000' DISPLAY = ':0.0' TRNINIT = '-B -e -f -I -N -r -s -T -v' LANG = 'en_US.UTF-8' XDG_CURRENT_DESKTOP = 'GNOME' XMODIFIERS = '' XDG_SESSION_DESKTOP = 'gnome' XAUTHORITY = '/home/cgull/.Xauthority' XDG_GREETER_DATA_DIR = '/var/lib/lightdm-data/cgull' LESSOPEN_HIDE = '' SSH_AUTH_SOCK = '/run/user/1000/keyring/ssh' LC_MESSAGES = 'en_US.UTF-8' SHELL = '/bin/bash' PAM_KWALLET_LOGIN = '/tmp/kwallet_cgull.socket' GDMSESSION = 'gnome' GPG_AGENT_INFO = '/tmp/gpg-NdsIyX/S.gpg-agent:3414:1' UPSTART_SESSION = 'unix:abstract=/com/ubuntu/upstart-session/1000/3158' XDG_VTNR = '7' BTDT = 'yes' CLUTTER_IM_MODULE = '' XDG_CONFIG_DIRS = '/etc/xdg/xdg-gnome:/usr/share/upstart/xdg:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings' XTERM_LOCALE = 'en_US.UTF-8' MPAGE = '-Pps -bletter -2 -H' XDG_DATA_DIRS = '/usr/share/gnome:/usr/local/share/:/usr/share/' XTERM_VERSION = 'XTerm(318)' JOB = 'dbus' EDITOR = 'emacs' WINELOADERNOEXEC = '1' NUMBER_OF_PROCESSORS = '2' OS = 'Windows_NT' PATHEXT = '.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH' PROCESSOR_ARCHITECTURE = 'x86' PROCESSOR_IDENTIFIER = 'AMD64 Family 20 Model 1 Stepping 0, GenuineIntel' PROCESSOR_LEVEL = '20' PROCESSOR_REVISION = '0100' SystemDrive = 'c:' SYSTEMROOT = 'C:\windows' winsysdir = 'C:\windows\system32' ComSpec = 'C:\windows\system32\cmd.exe' TEMP = 'C:\users\cgull\Temp' TMP = 'C:\users\cgull\Temp' windir = 'C:\windows' ALLUSERSPROFILE = 'C:\users\Public' APPDATA = 'C:\users\cgull\Application Data' CLIENTNAME = 'Console' HOMEDRIVE = 'C:' HOMEPATH = '\users\cgull' LOCALAPPDATA = 'C:\users\cgull\Local Settings\Application Data' LOGONSERVER = '\\minibit' SESSIONNAME = 'Console' USERDOMAIN = 'minibit' USERNAME = 'cgull' USERPROFILE = 'C:\users\cgull' COMPUTERNAME = 'minibit' PROCESSOR_ARCHITEW6432 = 'AMD64' ProgramW6432 = 'C:\Program Files' ProgramFiles = 'C:\Program Files (x86)' CommonProgramW6432 = 'C:\Program Files\Common Files' CommonProgramFiles = 'C:\Program Files (x86)\Common Files' PROMPT = '$P$G' = 'Z:=Z:\home\cgull' = 'C:=C:\cygwin23\bin' HKEY_LOCAL_MACHINE\Software\Cygwin HKEY_LOCAL_MACHINE\Software\Cygwin\Installations (default) = '\??\Z:\home\cgull\.wine\drive_c\cygwin' b61a932adbe77b7c = '\??\C:\cygwin23' c5e39b7a9d22bafb = '\??\C:\cygwin' d864ef4f7a56737e = '\??\C:\cygwin25' HKEY_LOCAL_MACHINE\Software\Cygwin\setup (default) = 'C:\cygwin25' obcaseinsensitive set to 1 Cygwin installations found in the registry: System: Key: 44340b27b0cc4ed5 Path: Z:\home\cgull\.wine\drive_c\cygwin System: Key: b61a932adbe77b7c Path: C:\cygwin23 System: Key: c5e39b7a9d22bafb Path: C:\cygwin System: Key: d864ef4f7a56737e Path: C:\cygwin25 c: hd NTFS196456Mb 94% CP PA z: hd NTFS196456Mb 94% CP PA C:\cygwin23 / system binary,auto C:\cygwin23\bin /usr/bin
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
Hi John, Thanks a lot for testing Cygwin on Wine. Wine Staging team and I done some Cygwin support work on Wine, we are glad to see people using Cygwin on Wine! However, generic speaking, if Cygwin works on Windows but breaks on Wine, I believe the first place to report is the Wine project. You are welcome to submit bug report to https://bugs.wine-staging.com/ and CC me :) It's also a good idea to search msys2/cygwin before submit new bugs: https://bugs.wine-staging.com/buglist.cgi?quicksearch=msys2_id=4821 If any Cygwin developers are annoyed by Wine related post then I'll feel guilty. Regarding your specific problem, yes, I am able to reproduce it on Wine, and I can confirm it works on Windows. Could you file a bug to Wine Staging and CC me? I suggest to investigate the Wine side first before bother Cygwin devs too much :) Thanks! -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: mktemp() fails on Wine 1.9.3 + Cygwin 2.5.0-0.2
I'm not able to debug it right now, but if you have time, I would suggest the following approach: Firstly, get two/three strace logs, one from Cygwin 2.3 + Wine, one from Cygwin 2.5 + Wine, and one from Cygwin 2.5 on Windows if you have Windows. Using vimdiff to compare 1.log, 2.log and 3.log, remove/replace some useless noise (like timestamp, process id, etc), vimdiff would give you pretty comparison result, and help you find out which part has changed between different version or between different platform. Secondly, get two WINEDEBUG logs [1]: Run wine with WINEDEBUG=+tid,+pid,+relay like below: WINEDEBUG=+tid,+pid,+relay wineconsole usr/bin/bash >> /tmp/cygwin.good.log (test mktemp inside wineconsole) Search for mktemp.exe and record down the pid number of mktemp.exe, grep the log of mktemp.exe from cygwin.good.log by the tid number. Repeat the above step for /tmp/cygwin.bad.log and compare the good version with the bad version using vimdiff or anything like that. Again, remove/replace noise information like pid numbers, after that vimdiff would provide pretty nice comparison for you. By gather information from the strace log comparison and the WINEDEBUG log comparison, we would be very closed to what's wrong in Wine. Once you need more details log, you might consider more Wine debug channel like WINEDEBUG=+tid,+pid,+relay,+file,+ntdll or something else, see [1] for an introduction. If you are too curious, you are encouraged to download Wine source code and start hacking! [1] https://wiki.winehq.org/Debug_Channels -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: WINE on Cygwin
Guys, Sorry for not getting involved with this discussion before. For those interested in more details about this topic, I included several good references in this message. I can think of many reasons why someone would want to run WINE under Cygwin and my reason, put shortly, is: GDI-X11. I did quite a research to identify all the issues related to this, and end up knowning that this sendmsg() limitation is a major one. I was really willing to start making things happen by getting more info on how to tackle this, but the discussion diverged to the rather philosophical why do this discussion. The only useful info I got from this thread was that this is still an issue, from Corinna. Can anyone point me to any reference covering the implementation of the missing sendmsg functionality (exchanging file descriptors across processes) ? Any (incomplete) piece of code ? Any help ? My company has manifested a clear commitment to having this done, and I'm trying to do my best not to let this die again. Tks FLu-X 1 - These are quite informative threads with many useful references: http://ask.slashdot.org/article.pl?sid=03/02/21/093223tid=109tid=104tid=4 http://www.cygwin.com/ml/cygwin-xfree/2002-09/msg00094.html 2 - Some related projects: http://sourceware.org/XOpenWin/ http://xwinx.sourceforge.net/index.php http://sources.redhat.com/win32-x11/ http://www.d1.dion.ne.jp/~sawanaka/peace/ (em japonês) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Nov 16 10:02, Informa??es wrote: Guys, Sorry for not getting involved with this discussion before. For those interested in more details about this topic, I included several good references in this message. I can think of many reasons why someone would want to run WINE under Cygwin and my reason, put shortly, is: GDI-X11. I did quite a research to identify all the issues related to this, and end up knowning that this sendmsg() limitation is a major one. I was really willing to start making things happen by getting more info on how to tackle this, but the discussion diverged to the rather philosophical why do this discussion. The only useful info I got from this thread was that this is still an issue, from Corinna. Can anyone point me to any reference covering the implementation of the missing sendmsg functionality (exchanging file descriptors across processes) ? Any (incomplete) piece of code ? Any help ? My company has manifested a clear commitment to having this done, and I'm trying to do my best not to let this die again. Red Hat would be delighted to do some contractual work for your company to target the problem of the missing descriptor passing functionality. See http://www.redhat.com/software/cygwin/ for contact information. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
Informações wrote: Can anyone point me to any reference covering the implementation of the missing sendmsg functionality (exchanging file descriptors across processes) ? Any (incomplete) piece of code ? Any help ? Stevens, UNIX Network Programming Volume 1, chapter 15, section 7. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
Flu-X AKA Informações wrote: Any other comments regarding the bulding/execution of the Wine under Cygwin would be very welcome. FLu-X Andrew DeFaria responded: I guess I don't see the point. One obvious application -- facing me now -- is to run Win 3.11 and Win 95 applications that break under XP but not under WINE. In a larger company, I'd simply turn a random workstation into a Linux server and put CygWin/X on each workstation, but in a very small company (say, 2 or 3 workstations) that's not a practical option. CygWINE would be perfect for those. We do MS-Windows better than Microsoft does. (-: BTW, about the spam-armouring on the list archives... I copied and pasted the addresses in this email, verbatim, from sources.redhat.com into KMail and they all came out right. If KMail can do it, so can spammers. Two tricks I use to achieve the same ends are to simply leave the word dot out of the domain, so my email becomes leon at cyberknights com au, and to scramble the addresses and use an OnMouseOver to descramble them at view time. Sooner or later, the nasties will start executing JavaScript too, but at the moment it seems to work. Cheers; Leon -- http://cyberknights.com.au/ Modern tools; traditional dedication http://plug.linux.org.au/ Member, Perth Linux User Group http://slpwa.asn.au/Member, Linux Professionals WA http://osia.net.au/ Member, Open Source Industry Australia http://linux.org.au/Member, Linux Australia -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
Leon Brooks wrote: One obvious application -- facing me now -- is to run Win 3.11 and Win 95 applications that break under XP but not under WINE. I suffer no such malady! If there is a Win 3.11 or Win 95 application that's having a problem running under XP then the chances are high that there's already a better version of that program floating about. I mean, come on - Win 95 is now 10 years old! -- A PBS mind in an MTV world. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Sun, Nov 13, 2005 at 06:56:26PM -0800, Andrew DeFaria wrote: Leon Brooks wrote: One obvious application -- facing me now -- is to run Win 3.11 and Win 95 applications that break under XP but not under WINE. I suffer no such malady! If there is a Win 3.11 or Win 95 application that's having a problem running under XP then the chances are high that there's already a better version of that program floating about. I mean, come on - Win 95 is now 10 years old! Yep. And, topics about Cygwin and Wine are also several years old. Surely if it was really that crucial someone would have done something by now. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Thu, 2005-11-03 at 18:25 -0500, Eliah Kagan wrote: It would seem to me that making an arbitrary window application use X11 to draw its windows would involve cygwin. Would it be appropriate to move this to the Cygwin-X list? There has been discussion in http://cygwin.com/ml/win32-x11/2002-q3/ and following but without any improvements. this topic comes up on cygwin-xfree from time to time but silences right after I point to the archived discussions. If you wan't to discuss this, use the win32-x11 mailinglist. signature.asc Description: This is a digitally signed message part
WINE on Cygwin
Hey All, I'm seriously interested in making the WINESERVER work under Cygwin and have been invistigating some of the issues related to this matter. One of the WineHQ developers informed me that: ... the last time someone tried, the main obstacle was that cygwin doesn't support sendmsg() to send file descriptors across processes, which means that the wine server cannot work. This in turn means you cannot run kernel32 or user32. Some further invistigation shows that this is an old issue that has arisen several times during the course of the Cygwin history. Does anybody has any clue on the status of this issue ? Could anyone provide me some useful information that I could take as an starting point for this implementation ? Any other comments regarding the bulding/execution of the Wine under Cygwin would be very welcome. FLu-X -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Nov 3 11:08, Informa??es wrote: Hey All, I'm seriously interested in making the WINESERVER work under Cygwin and have been invistigating some of the issues related to this matter. One of the WineHQ developers informed me that: ... the last time someone tried, the main obstacle was that cygwin doesn't support sendmsg() to send file descriptors across processes, which means that the wine server cannot work. This in turn means you cannot run kernel32 or user32. Some further invistigation shows that this is an old issue that has arisen several times during the course of the Cygwin history. Does anybody has any clue on the status of this issue ? It's still an issue. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
Informações wrote: Hey All, I'm seriously interested in making the WINESERVER work under Cygwin and have been invistigating some of the issues related to this matter. One of the WineHQ developers informed me that: ... the last time someone tried, the main obstacle was that cygwin doesn't support sendmsg() to send file descriptors across processes, which means that the wine server cannot work. This in turn means you cannot run kernel32 or user32. Some further invistigation shows that this is an old issue that has arisen several times during the course of the Cygwin history. Does anybody has any clue on the status of this issue ? Could anyone provide me some useful information that I could take as an starting point for this implementation ? Any other comments regarding the bulding/execution of the Wine under Cygwin would be very welcome. FLu-X I guess I don't see the point. Isn't Wine an emulator for running Windows apps on Unix/Linux? If so then why would you need it under Cygwin as Cygwin already runs on Windows so if your want to run a Windows apps, well then just run the Windows app! -- Do Lipton employees take coffee breaks? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Thu, 2005-11-03 at 07:41 -0800, Andrew DeFaria wrote: I guess I don't see the point. Isn't Wine an emulator for running Windows apps on Unix/Linux? If so then why would you need it under Cygwin as Cygwin already runs on Windows so if your want to run a Windows apps, well then just run the Windows app! Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. bye ago signature.asc Description: This is a digitally signed message part
Re: WINE on Cygwin
On Thu, 03 Nov 2005 16:00:51 GMT, Alexander Gottwald wrote: On Thu, 2005-11-03 at 07:41 -0800, Andrew DeFaria wrote: I guess I don't see the point. Isn't Wine an emulator for running Windows apps on Unix/Linux? If so then why would you need it under Cygwin as Cygwin already runs on Windows so if your want to run a Windows apps, well then just run the Windows app! Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? AndyM -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: WINE on Cygwin
Andy Moreton wrote: On Thu, 03 Nov 2005 16:00:51 GMT, Alexander Gottwald wrote: On Thu, 2005-11-03 at 07:41 -0800, Andrew DeFaria wrote: I guess I don't see the point. Isn't Wine an emulator for running Windows apps on Unix/Linux? If so then why would you need it under Cygwin as Cygwin already runs on Windows so if your want to run a Windows apps, well then just run the Windows app! Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? AndyM Well, how about sandboxing? It's the ideal way to test out a virus or other suspect warez: run it on a virtual machine where it can't escape into your real one. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Thu, 2005-11-03 at 16:36 +, Andy Moreton wrote: Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? Because it can be done! VNC is slow, there is no integration with the local desktop. You can't work without interfering with the local desktop. Using wine just to redirect the graphic display is overkill but unfortunatly the most promising solution. Separation is yet another reason. signature.asc Description: This is a digitally signed message part
Re: WINE on Cygwin
Dave Korn wrote: Well, how about sandboxing? It's the ideal way to test out a virus or other suspect warez: run it on a virtual machine where it can't escape into your real one. But WINE isn't a virtual machine, and it doesn't offer that kind of protection. You would need Xen / VMWare / etc for that. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: WINE on Cygwin
Brian Dessent wrote: Dave Korn wrote: Well, how about sandboxing? It's the ideal way to test out a virus or other suspect warez: run it on a virtual machine where it can't escape into your real one. But WINE isn't a virtual machine, and it doesn't offer that kind of protection. You would need Xen / VMWare / etc for that. Oh, I stand corrected. You mean it doesn't even do virtual-drive-in-a-file-on-the-real-HD then? That's a shame. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
Dave Korn wrote: But WINE isn't a virtual machine, and it doesn't offer that kind of protection. You would need Xen / VMWare / etc for that. Oh, I stand corrected. You mean it doesn't even do virtual-drive-in-a-file-on-the-real-HD then? That's a shame. Well, considering WINE stands for WINE Is Not an Emulator... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: WINE on Cygwin
Brian Dessent wrote: Dave Korn wrote: But WINE isn't a virtual machine, and it doesn't offer that kind of protection. You would need Xen / VMWare / etc for that. Oh, I stand corrected. You mean it doesn't even do virtual-drive-in-a-file-on-the-real-HD then? That's a shame. Well, considering WINE stands for WINE Is Not an Emulator... It doesn't need to be an emulator. It translates file-system accesses from something like C:\foo.txt into something that makes sense to the underlying FS, yeh? But that could just as easily be done by translating device-driver-level read and write block calls into reads and writes to sectors within a file on the host FS. The issues of virtualisation/emulation are entirely orthogonal to that. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
I guess I don't see the point. Isn't Wine an emulator for running Windows apps on Unix/Linux? If so then why would you need it under Cygwin as Cygwin already runs on Windows so if your want to run a Windows apps, well then just run the Windows app! Well how about to support WINE development? It would be quite nice to be able to run an app under windows and under WINE at the same time to help differentiate between wine bugs and software bugs (Including Windows bugs). -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On 11/3/05, Alexander Gottwald [EMAIL PROTECTED] wrote: On Thu, 2005-11-03 at 16:36 +, Andy Moreton wrote: Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? Because it can be done! VNC is slow, there is no integration with the local desktop. You can't work without interfering with the local desktop. Using wine just to redirect the graphic display is overkill but unfortunatly the most promising solution. Separation is yet another reason. Not only is VNC slow, but VNC only lets one user log on and run graphical programs at a time on Windows. It is possible to have multiple simultaneous Remote Desktop sessions, but only with Windows Terminal Server, which is expensive and pay-per-license (you need a license for each login slot), and only runs on Windows Server operating systems, which are also expensive. It would be very, very nice to be able to run graphical Windows programs remotely using ssh -X. Does anyone know if there any other way to do this, besides with Wine? (Perhaps something more native?) -Eliah -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Thu, Nov 03, 2005 at 05:20:57PM -0500, Eliah Kagan wrote: On 11/3/05, Alexander Gottwald [EMAIL PROTECTED] wrote: On Thu, 2005-11-03 at 16:36 +, Andy Moreton wrote: Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? Because it can be done! VNC is slow, there is no integration with the local desktop. You can't work without interfering with the local desktop. Using wine just to redirect the graphic display is overkill but unfortunatly the most promising solution. Separation is yet another reason. Not only is VNC slow, but VNC only lets one user log on and run graphical programs at a time on Windows. It is possible to have multiple simultaneous Remote Desktop sessions, but only with Windows Terminal Server, which is expensive and pay-per-license (you need a license for each login slot), and only runs on Windows Server operating systems, which are also expensive. It would be very, very nice to be able to run graphical Windows programs remotely using ssh -X. Does anyone know if there any other way to do this, besides with Wine? (Perhaps something more native?) Since we seem to have gotten pretty far afield from anything cygwin-related (Corinna has already indicated that Cygwin doesn't do what was originally requested) maybe it would be best to take this to another forum. I do have to say that this may be the first time I've ever heard anyone indicate that they wanted to use cygwin because it gave them a speed advantage, though... cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On 11/3/05, Christopher Faylor [EMAIL PROTECTED] wrote: On Thu, Nov 03, 2005 at 05:20:57PM -0500, Eliah Kagan wrote: On 11/3/05, Alexander Gottwald [EMAIL PROTECTED] wrote: On Thu, 2005-11-03 at 16:36 +, Andy Moreton wrote: Sometimes it's useful to have a separation between the program and windows. You could trace all registry or file access of a program. Wine would be useful for remote program usage since it exports the display via X11. This still sounds fairly pointless. the tools from sysinternals.com allow you to monitor all file and registry access from an application. A VNC client will solve your remote operation needs. So what is the real reason for wanting to do something so perverse ? Because it can be done! VNC is slow, there is no integration with the local desktop. You can't work without interfering with the local desktop. Using wine just to redirect the graphic display is overkill but unfortunatly the most promising solution. Separation is yet another reason. Not only is VNC slow, but VNC only lets one user log on and run graphical programs at a time on Windows. It is possible to have multiple simultaneous Remote Desktop sessions, but only with Windows Terminal Server, which is expensive and pay-per-license (you need a license for each login slot), and only runs on Windows Server operating systems, which are also expensive. It would be very, very nice to be able to run graphical Windows programs remotely using ssh -X. Does anyone know if there any other way to do this, besides with Wine? (Perhaps something more native?) Since we seem to have gotten pretty far afield from anything cygwin-related (Corinna has already indicated that Cygwin doesn't do what was originally requested) maybe it would be best to take this to another forum. I do have to say that this may be the first time I've ever heard anyone indicate that they wanted to use cygwin because it gave them a speed advantage, though... cgf cgf-- It would seem to me that making an arbitrary window application use X11 to draw its windows would involve cygwin. I recognize that as moderator, it's your call. If you say nothing more on it, nor shall I. Would it be appropriate to move this to the Cygwin-X list? -Eliah -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: WINE on Cygwin
On Thu, Nov 03, 2005 at 06:25:17PM -0500, Eliah Kagan wrote: It would seem to me that making an arbitrary window application use X11 to draw its windows would involve cygwin. Not necessarily. I recognize that as moderator, it's your call. If you say nothing more on it, nor shall I. Would it be appropriate to move this to the Cygwin-X list? Er, if you are going to discuss X, I guess so. Knowing how these things go, however, I think it will be a fruitless discussion until someone starts actually coding. This issue has come up repeatedly over the years so I doubt that anyone is going to come up with a magic solution. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
OT? Legacy code and constants / good and portable coding (RE: Compiling Wine in Cygwin)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Marcel Telka On 05.09.2003 22:06, Gregory Nutt wrote: Trying to compile wine-20030813 in the first release of the 1.5.x series. I discovered that shader.c is looking for -HUGE which is apparently supposed to be defined in math.h. I was able to make it compile by changing the shader.c to look for -HUGE_VAL which is defined in cygwin's math.h. However, I'd like to know if this is a bug to report to Wine or a bug to report to Cygwin. Since Wine compiles on Linux without a problem, I thought I'd start with Cygwin. IMHO, that is wine-related problem. http://www.opengroup.org/onlinepubs/007904975/basedefs/math.h.html -- Ughhh... I wonder who it was that wrote: On Fri, 5 Sep 2003, Igor Pechtchanski wrote: HUGE is a SVID-specific value that is equal to MAXFLOAT on my RedHat 7.3 box. That is *not* the same as HUGE_VAL, BTW, so I'd use MAXFLOAT instead. MAXFLOAT is outdated. I would suggest FLT_MAX in float.h. As there seems to some confusion regarding this: Thus I wonder; Is there ANY good reading on what is legacy/outdated - and what isn't!? /Hannu E K Nevalainen, B.Sc. EE - 59°16.37'N, 17°12.60'E --END OF MESSAGE-- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Compiling Wine in Cygwin
Trying to compile wine-20030813 in the first release of the 1.5.x series. I discovered that shader.c is looking for -HUGE which is apparently supposed to be defined in math.h. I was able to make it compile by changing the shader.c to look for -HUGE_VAL which is defined in cygwin's math.h. However, I'd like to know if this is a bug to report to Wine or a bug to report to Cygwin. Since Wine compiles on Linux without a problem, I thought I'd start with Cygwin. Greg -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Compiling Wine in Cygwin
On 05.09.2003 22:06, Gregory Nutt wrote: Trying to compile wine-20030813 in the first release of the 1.5.x series. I discovered that shader.c is looking for -HUGE which is apparently supposed to be defined in math.h. I was able to make it compile by changing the shader.c to look for -HUGE_VAL which is defined in cygwin's math.h. However, I'd like to know if this is a bug to report to Wine or a bug to report to Cygwin. Since Wine compiles on Linux without a problem, I thought I'd start with Cygwin. IMHO, that is wine-related problem. http://www.opengroup.org/onlinepubs/007904975/basedefs/math.h.html -- +---+ | Marcel Telka e-mail: [EMAIL PROTECTED] | |homepage: http://telka.sk/ | |jabber: [EMAIL PROTECTED] | +---+ -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Compiling Wine in Cygwin
On Fri, 5 Sep 2003, Marcel Telka wrote: On 05.09.2003 22:06, Gregory Nutt wrote: Trying to compile wine-20030813 in the first release of the 1.5.x series. I discovered that shader.c is looking for -HUGE which is apparently supposed to be defined in math.h. I was able to make it compile by changing the shader.c to look for -HUGE_VAL which is defined in cygwin's math.h. However, I'd like to know if this is a bug to report to Wine or a bug to report to Cygwin. Since Wine compiles on Linux without a problem, I thought I'd start with Cygwin. IMHO, that is wine-related problem. http://www.opengroup.org/onlinepubs/007904975/basedefs/math.h.html HUGE is a SVID-specific value that is equal to MAXFLOAT on my RedHat 7.3 box. That is *not* the same as HUGE_VAL, BTW, so I'd use MAXFLOAT instead. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Compiling Wine in Cygwin
On Fri, 5 Sep 2003, Igor Pechtchanski wrote: HUGE is a SVID-specific value that is equal to MAXFLOAT on my RedHat 7.3 box. That is *not* the same as HUGE_VAL, BTW, so I'd use MAXFLOAT instead. MAXFLOAT is outdated. I would suggest FLT_MAX in float.h. -- Brian Ford Senior Realtime Software Engineer VITAL - Visual Simulation Systems FlightSafety International Phone: 314-551-8460 Fax: 314-551-8444 -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
wine under cygwin under wine under...
Front page slashdot story: http://developers.slashdot.org/developers/02/11/17/1648220.shtml?tid=125 --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
