[Bug 47100] New: Simple command that needs CreateSymbolicLinkW doesn`t work anymore in Staging-4.7
wine-bugs at winehq.org
wine-bugs at winehq.org
Mon Apr 29 15:08:17 CDT 2019
https://bugs.winehq.org/show_bug.cgi?id=47100
Bug ID: 47100
Summary: Simple command that needs CreateSymbolicLinkW doesn`t
work anymore in Staging-4.7
Product: Wine-staging
Version: 4.6
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs at winehq.org
Reporter: xerox.xerox2000x at gmail.com
CC: leslie_alistair at hotmail.com, z.figura12 at gmail.com
Distribution: ---
Hi, I noticed that the patchset in Staging for CreateSymbolicLinkW has been
updated.
Just creating this bug to let you know that the simple command from comment #4:
https://bugs.winehq.org/show_bug.cgi?id=44948#c4 doesn`t work anymore.
I have a compiled recent version lying here ( wine-4.3-339-g865d4c3c72
(Staging)). There it seems to wok fine.
The command from comment #4 in one liner:
cd $(mktemp -d) &&
/media/louis/00e587ff-1035-4ec8-8d1f-b69d3527589a/wine-staging4.3/wine64-build/wine
cmd /C "mklink foo bar" && stat foo
000b:fixme:winediag:start_process Wine Staging 4.3 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
File: foo -> /home/louis/.wine/dosdevices/z:/tmp/tmp.8TxcDBiOH7/bar
Size: 54 Blocks: 0 IO Block: 4096 symbolic link
Device: 821h/2081d Inode: 1048736 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 1000/ louis) Gid: ( 1000/ louis)
Access: 2019-04-29 21:56:16.530708099 +0200
Modify: 2019-04-29 21:56:16.530708099 +0200
Change: 2019-04-29 21:56:16.530708099 +0200
in current Staging 4.7:
cd $(mktemp -d) && /opt/wine-staging/bin/wine cmd /C "mklink foo bar" && stat
foo
000b:fixme:winediag:start_process Wine Staging 4.7 is a testing version
containing experimental patches.
000b:fixme:winediag:start_process Please mention your exact version when filing
bug reports on winehq.org.
Failed to open 'foo'
stat: cannot stat 'foo': No such file or directory
If I remember correctly running Office365 installer with Staging was enough to
avoid manually copying files to correct locations.
I did not yet test if that is broken too now in Staging-4.7, will do later
(takes quite some time). Just reporting this simple example for now.
--
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.
More information about the wine-bugs
mailing list