This is the mail archive of the
mailing list for the Cygwin project.
Re: building 64 bit packages
- From: Andy Koppe <andy dot koppe at gmail dot com>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 28 Mar 2013 20:51:58 +0000
- Subject: Re: building 64 bit packages
- References: <20130328133625 dot GL11431 at calimero dot vinschen dot de> <CAHWeT-Z9i1RVcxsZg3ms25z4LGPgSthq2AZcM6owvyfwf0UZ3g at mail dot gmail dot com> <20130328140953 dot GO11431 at calimero dot vinschen dot de> <20130328141252 dot GP11431 at calimero dot vinschen dot de>
On 28 March 2013 14:12, Corinna Vinschen wrote:
> On Mar 28 15:09, Corinna Vinschen wrote:
>> On Mar 28 14:05, Andy Koppe wrote:
>> > On 28 March 2013 13:36, Corinna Vinschen wrote:
>> > > Hi guys,
>> > >
>> > >
>> > > right now it's only possible to build a 64 bit package using the native
>> > > toolchain. Yaakov is working on a 32 bit cross toolchain, but this
>> > > may take another couple of days.
>> > >
>> > > Anyway, the latest 64 bit Cygwin DLL seems to be stable enough to call
>> > > it post-alpha or pre-beta or something like that. So I'd like to invite
>> > > all of you maintainers to participate in building 64 bit packages,
>> > > foremost those packages other packages rely upon, like libraries.
>> > > If you have a 64 bit machine, please try the test release and see if
>> > > you can build your packages. For the time being, just download
>> > > ftp://cygwin.com/pub/cygwin/64bit/setup64.exe, install the test distro
>> > > (what's already existing of it) and do your worst ;)
>> > Great stuff. Thanks to the kind person who contributed a mintty package.
>> That's your package ;) I just added a source package for licensing
> To be more clear, I simply took the mintty binary you provided a couple
> of days ago and tar'ed it up. It's not *really* a serious mintty binary
I've now uploaded a cygport-built mintty 1.2-beta1-1 package.
(I've also run ./GEN-sware in
/sourceware/ftp/anonftp/pub/cygwin/64bit. This threw a bunch of errors
such as "not enough package files in 64bit/release/gcc", but the
resulting setup.ini looks ok, so I guess those errors are expected?)