Re: ReRe: Compiling gtk+ with MinGW on WindowsXP - perl problem

[Tor Lillqvist <tml iki fi>]

(Keeping gtk-list in the loop, as that is where the thread started.)

> The problem with chmod is, that XP simply has no mechanisms to store the
> result of chmod -m a+w, for example.

Well, that depends on one's point of view;) The access control lists
of NTFS is in general more powerful than the traditional rwxrwxrwx
bits of UNIX. But it is of course very different. That's why it's hard
to make Windows file protection look and behave like it was based on
only UNIX bits.

IIRC, Cygwin (and thus MSYS?) does some semi-ugly tricks here,
ordering the ACEs (access control entries) in an ACL in a non-standard
fashion to make the end result look and behave like the UNIX bits. But
at least my personal experience is that when you mix Cygwin and
non-Cygwin tools you quickly end up in a strange mess with file
protections being quite weird, and I always use the CYGWIN=nontsec
environment variable when I use Cygwin to avoid its over-cleverness. I
haven't had to do that in MSYS, though, I don't know if it's because
MSYS doesn't even attempt those tricks, or what.

> Thus my question again: Is there a way to work around glib-mkenums ?

Well, you could always copy the generated files from a build on some
UNIX box... But really, making the perl script work shouldn't be that
hard. I don't know what your exact problem is. Don't you have MSYS's
perl.exe in your PATH? What does the configure output say? For me, I
see in GLib's config.log:

configure:7764: checking for perl
configure:7780: found /bin/perl

and that then means that the #! line will use /bin/perl directly,
without using the "/usr/bin/env perl" fallback which apparently is
problematic for you.