Trent W. Buck wrote: > zooko <[email protected]> writes: > >> I figured out the mysterious filesystem state -- it was the +x bits on >> the .dll's. Once I ran chmod +x *.dll, everything worked. Thanks >> again, Salvatore! > > Admittedly I don't know anything about Windows, but surely it's not > normal for *libraries* to require their execute bit set? Is this a bug?
Windows will not load libraries without the execute ACL... (This follows from the VMS legacy in modern Windows ACLs. Unlike Unix, VMS and Windows require execute privileges for any executable code loaded including indirectly loaded stuff like libraries...) The lesson here is probably not to do Windows ACL munging with Unix-like (Cygwin) commands... or perhaps that Windows ACLs can ultimately be more strict than Unix ones, but are hardly ever used that way... -- --Max Battcher-- http://worldmaker.net _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
