Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm Sender: cygwin-apps-owner AT cygwin DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Mail-Followup-To: cygwin-apps AT cygwin DOT com Delivered-To: mailing list cygwin-apps AT cygwin DOT com content-class: urn:content-classes:message Subject: RE: fastcall MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 8 Apr 2002 08:54:00 +1000 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Robert Collins" To: "Danny Smith" , "cygwin-apps" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g37Ms4o00574 > -----Original Message----- > From: Danny Smith [mailto:danny_r_smith_2001 AT yahoo DOT co DOT nz] > Sent: Monday, April 08, 2002 8:29 AM > In order to get it into official sources, the ReactOS team > will need some support. What sort of support can we offer? I'm happy to vouch that 'it works for me'. We've been round this one before with the --auto-import patch after all. > For the fastcall to work, binutils support is also needed. > There is a big problem with binutils because of the vacuum > left by DJ stepping down as w32 maintainer. There are > currently bugs in binutils with respect to ld --shared (or > at least there was two weeks ago and has been since 17 [UTC] > December). > > Related frustrations: ReactOs team has submitted several > relatively non-intrusive patches for useful windres > improvements that have not been seriously reviewed. My patch > for --exclude-all-libs lingered into forgetfullness. Ditto > for a ReactOs patch for checksums in pe-executables. Which would be wonderful things to have. > Chris asked the question a while ago: "Wanna be a binutils > maintainer". Are you asking if someone here can step up? I'd love to, but I suspect I don't have the time to do a good job. I'm struggling to answer all setup.exe related questions at the moment. Also, I think the issue is needing the binutils w32 maintainer, not a cygwin port maintainer, and frankly, I've no idea what sort of time commitment that entails. If someone (perhaps DJ) can clarify that I'll consider stepping up for that maintainership - on the basis of someone being better than no-one, even if I'm a bit slow on response for them. Rob