--- On Mon, 1/7/13, David Laight wrote:
> On Mon, Jul 01, 2013 at 06:13:26PM
> +0200, Peter Rosin wrote:
> >
> > I would like to point out that it seems that the
> current bug does not
> > appear to be *in* setup.exe, but rather occurs when
> setup.exe runs
> > a bash post-install script, where
Hello,
my name is Wolf I am from germany and use OSX 10.8 to develop my apps, play
games etc. I have read that there is no one, who compile the OSX version of
WINE. I would do this. I have tried the osxwinebuilder script from
http://code.google.com/p/osxwinebuilder and it did the job.
I have do
Hello all Wine developers,
[the second attempt to send, is the list subscribers only?]
the firs I would like to express my respect to the work done.
Now to one of our application, we maintain open-source chromatographic
software CHROMuLAN
https://sourceforge.net/projects/chromulan/
Unfortuna
you are right, i'm attaching a new patch.
2013/7/1 Hans Leidekker :
> On Mon, 2013-07-01 at 08:56 +0900, Rosen Diankov wrote:
>
>> diff -ru wine-1.6-rc3-old/dlls/wbemprox/builtin.c
>> wine-1.6-rc3/dlls/wbemprox/builtin.c
>> --- wine-1.6-rc3-old/dlls/wbemprox/builtin.c2013-06-22
>> 03:24:01.0
--- On Tue, 2/7/13, Alan W. Irwin wrote:
> > Going personal and accusing others of being biased is
> not a way of
> getting help.
...In short, I have
> a
> prejudice against anyone stating anecdotal evidence
> concerning issues
> with _any_ open-source software if they don't back up that
> anec
On Mon, Jul 1, 2013 at 7:11 PM, Alan W. Irwin wrote:
> On 2013-07-01 19:58+0100 Hin-Tak Leung wrote:
>
>> --- On Mon, 1/7/13, Alan W. Irwin wrote:
>> ... I hope your negative
>>>
>>> attitude
>>> toward the Cygwin toolchain is not typical of such
>>> developers. After
>>> all, even though the Wi
On 2013-07-01 19:58+0100 Hin-Tak Leung wrote:
--- On Mon, 1/7/13, Alan W. Irwin wrote:
... I hope your negative
attitude
toward the Cygwin toolchain is not typical of such
developers. After
all, even though the Windows GNU toolchain code bases have
diverged
between the two groups of developer
On Mon, Jul 01, 2013 at 06:13:26PM +0200, Peter Rosin wrote:
>
> I would like to point out that it seems that the current bug does not
> appear to be *in* setup.exe, but rather occurs when setup.exe runs
> a bash post-install script, where the bash.exe that interprets the
> script depends on cygwi
On Jul 1, 2013, at 4:26 PM, Ken Thomases wrote:
> On Jul 1, 2013, at 3:29 PM, Юрий Воротилов wrote:
>
>> Fix to support input of characters with diacritic symbols using AltGr (e.g.
>> Latvian - AltGr+a=ā).
>> Tested on Ubuntu 12.04 and Centos 6.
>> I also have a bug opened in Crossover tracker:
On Jul 1, 2013, at 3:29 PM, Юрий Воротилов wrote:
> Fix to support input of characters with diacritic symbols using AltGr (e.g.
> Latvian - AltGr+a=ā).
> Tested on Ubuntu 12.04 and Centos 6.
> I also have a bug opened in Crossover tracker:
> http://www.codeweavers.com/support/tickets/browse/?tick
--- On Mon, 1/7/13, Alan W. Irwin wrote:
... I hope your negative
> attitude
> toward the Cygwin toolchain is not typical of such
> developers. After
> all, even though the Windows GNU toolchain code bases have
> diverged
> between the two groups of developers, there is still a
> common interest
On 2013-06-28 23:37, Hin-Tak Leung wrote:
> --- On Fri, 28/6/13, Alan W. Irwin wrote:
>
> ... However, because of the Cygwin fork
>> bug, Cygwin on
>> Wine has largely been untested for the last three years so
>> this could
>> be a good opportunity to do such testing for the combination
>> of Cyg
Signed-off-by: Pavel Shilovsky
---
fs/locks.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/locks.c b/fs/locks.c
index 60f3ce8..86f3a93 100644
--- a/fs/locks.c
+++ b/fs/locks.c
@@ -1758,6 +1758,12 @@ SYSCALL_DEFINE2(flock, unsigned int, fd, unsigned int,
cmd)
goto
On 2013-07-01 18:13+0200 Peter Rosin wrote:
On 2013-06-29 18:33, Alan W. Irwin wrote:
Those have been mentioned before here, and I have looked at them.
Cygwin is a very large collection of software so the number of bugs
that are reported does not seem excessive to me, and for my personal
needs
that maps them into O_DENY* flags and make them visible for
applications on mounts with sharelock option.
Signed-off-by: Pavel Shilovsky
---
fs/locks.c | 1 +
fs/nfsd/nfs4state.c | 46 +-
fs/nfsd/nfsproc.c | 1 +
3 files changed, 47 insert
by passing these flags to NFSv4 open request. Make it return
-ESHAREDENIED on share conflicts with other opens and disable
O_DENYDELETE support since NFSv4 doesn't support it.
Signed-off-by: Pavel Shilovsky
---
fs/nfs/dir.c | 4
fs/nfs/internal.h | 3 ++-
fs/nfs/nfs4file.c | 4 ++
Construct share_access value from O_DENY* flags and send it to
the server. Use NTCreateAndX command rather than Trans2
all the time we have any of O_DENY* flags regardless of unix
extensions support. Also change smb error mapping of
NT_STATUS_SHARING_VIOLATION to -ESHAREDENIED.
Signed-off-by: Pave
and simplify CIFSSMBOpen params.
Signed-off-by: Pavel Shilovsky
---
fs/cifs/cifsacl.c | 8
fs/cifs/cifsglob.h | 2 +-
fs/cifs/cifsproto.h | 8
fs/cifs/cifssmb.c | 50 +++---
fs/cifs/dir.c | 12 ++--
fs/cifs/file.
Introduce new LOCK_DELETE flock flag that is suggested to be used
internally only to map O_DENYDELETE open flag:
!O_DENYDELETE -> LOCK_DELETE | LOCK_MAND.
Signed-off-by: Pavel Shilovsky
---
fs/locks.c | 55 +---
fs/namei.c
This patch adds 3 flags:
1) O_DENYREAD that doesn't permit read access,
2) O_DENYWRITE that doesn't permit write access,
3) O_DENYDELETE that doesn't permit delete or rename.
Network filesystems CIFS, SMB2.0, SMB3.0 and NFSv4 have such flags -
this change can benefit cifs and nfs modules as well a
Main changes from v6:
1) Fix LOCK_DELETE mandatory lock detection for O_DENYDELETE opens.
2) Add ESHAREDENIED error code definition for alpha, mips, parisc and sparc
arches.
3) Remove code changes in do_last function if sharelocks are disabled.
Main changes from v5:
1) O_DENYDELETE is now support
On 2013-07-01 06:13+0100 Hin-Tak Leung wrote:
[...]In terms of "relative" importance, consider that mingw (both native and cross) GNU toolchain works well,
the toolchain part of cygwin is hardly a priority.
Once again you are implying the MinGW GNU toolchain is better than the
Cygwin GNU toolc
On 2013-06-29 18:33, Alan W. Irwin wrote:
> Those have been mentioned before here, and I have looked at them.
> Cygwin is a very large collection of software so the number of bugs
> that are reported does not seem excessive to me, and for my personal
> needs (building and testing software on the Cy
On Mon, 2013-07-01 at 08:56 +0900, Rosen Diankov wrote:
> diff -ru wine-1.6-rc3-old/dlls/wbemprox/builtin.c
> wine-1.6-rc3/dlls/wbemprox/builtin.c
> --- wine-1.6-rc3-old/dlls/wbemprox/builtin.c2013-06-22 03:24:01.0
> +0900
> +++ wine-1.6-rc3/dlls/wbemprox/builtin.c2013-06-27
24 matches
Mail list logo
