-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Reini Urban wrote: | Hmm. Good argument. | Maybe a -i386 suffix against the -i64 suffix is in order. | i64 assumes fastcall-like calling conventions which don't support. | (first 4 args via registers, rest on the stack) | | And later we want to come up with a proper CPAN release of a Cygwin package. | We want more API functions from the dll, and mount table handling. | Cygwin::Version as package is still forbidden. hmm.
The change would mean, of course, rebuilding the other modules which you've already done once for 5.10, but as this is still in experimental, the end users shouldn't really be affected yet. If you're prepared to make this change, I would propose the following schedule: * I wrap up my current dev cycle and upload over the weekend, which would be a "pre-5.10" snapshot; * you re-release 5.10 with the expanded archlib ASAP; * I then begin reviewing all 120+ Perl modules and anything else depending on (lib)perl for 5.10, eliminating any cruft, duplication, etc. and rebuilding the rest (could easily take 2+ weeks of continued development); * once complete, we coordinate your stabilization of 5.10 in the distro with my uploads to sourceware (3 modules) and Ports. Yaakov Cygwin Ports -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHh2eXpiWmPGlmQSMRCNoUAJ0UbtN+pXPsKHgIIlv9CUjHFVq2sACg/Di/ y6E6r0jzAm1A1M/cUspZCM4= =fFdv -----END PGP SIGNATURE----- ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Cygwin-ports-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cygwin-ports-general
