From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: missing 64bit ports
Date: Fri, 17 Jul 2015 12:53:00 -0000 [thread overview]
Message-ID: <55A8FAA0.9020206@cornell.edu> (raw)
In-Reply-To: <20150717073222.GA3864@calimero.vinschen.de>
On 7/17/2015 3:32 AM, Corinna Vinschen wrote:
> On Jul 15 16:12, Ken Brown wrote:
>> On 7/15/2015 2:28 PM, Corinna Vinschen wrote:
>>> On Jul 15 16:24, Marco Atzeri wrote:
>>>> Dear All,
>>>> I spent a bit of time checking the real situation of the packages
>>>> still missing as 64 bit port.
>>>> After xdelta, bsdiff and iperf porting, without counting the few mingw ones,
>>>> the duplicates we are down to ~44.
>>>>
>>>> Please see here the analysis :
>>>> https://docs.google.com/spreadsheets/d/1Hn7Eaq6djEN9X0jS_AM8-DH_LvP43G9_DXnpTt09Asc/edit#gid=0
>>>> Feel free to insert comments on the cells.
>>>>
>>>> For what I found :
>>>>
>>>> - half of them are dead upstream so we can directly
>>>> obsolete and don't worry anynore.
>>>>
>>>> - Few are Jary's scripts, so the only porting issue is Jary's time.
>>>>
>>>> - Very few have real porting issue
>>>>
>>>> The only one really interesting for me is Mathomatic and eventually catdoc
>>>> if works with latest word documents.
>>>> (of course I will port pure-ftpd)
>>>
>>> Thanks for looking into this.
>>>
>>> Two points:
>>>
>>> - Shall we remove all 32b-bit only orphaned packages for which we don't
>>> get a maintainer until, say, end of August?
>>
>> That seems reasonable, as long as there are exceptions for packages where
>> the lack of a 64-bit package is due to genuine porting difficulties.
>> libsigsegv was in that category until yesterday. Another one I'm aware of
>> is ffcall.
>
> I understand, but they are unmaintained. So, who's going to check
> if they are buildable as 64 bit packages?
Good point. In that case, I volunteer to maintain ffcall, just to protect it.
I have an interest in it because it's used by clisp (and probably nothing else).
I already looked into the possibility of a 64-bit port, starting here:
https://cygwin.com/ml/cygwin-apps/2015-02/msg00245.html
And Reini made a start (https://github.com/rurban/ffcall/tree/win64), but I
don't know when/if he'll have time to finish it.
Ken
next prev parent reply other threads:[~2015-07-17 12:53 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 14:24 Marco Atzeri
2015-07-15 17:39 ` Marcos Vives Del Sol
2015-07-15 17:48 ` Warren Young
2015-09-26 9:51 ` Marco Atzeri
[not found] ` <CABKfh3ywLyGB1gAkjwTFv0HXQc+kp4SiRHFu1ymWj=Qn4_hxcw@mail.gmail.com>
2015-09-28 7:24 ` Marco Atzeri
2015-07-15 17:47 ` Warren Young
2015-07-15 18:28 ` Corinna Vinschen
2015-07-15 19:32 ` Warren Young
2015-07-15 20:12 ` Ken Brown
2015-07-16 8:07 ` jari
2015-07-16 8:10 ` Marco Atzeri
2015-07-16 8:17 ` missing 64bit ports (xdelta3 vs xdelta and pristine-tar) jari
2015-07-16 18:35 ` Achim Gratz
2015-07-16 18:43 ` Marco Atzeri
2015-07-16 23:52 ` jari
2015-07-17 5:32 ` Marco Atzeri
2015-07-17 7:22 ` jari
2015-07-17 8:22 ` Marco Atzeri
2015-07-17 18:17 ` Achim Gratz
2015-07-18 8:11 ` jari
2015-07-18 19:00 ` Achim Gratz
2015-07-18 19:46 ` Marco Atzeri
2015-07-19 11:05 ` jari
2015-07-19 14:47 ` Marco Atzeri
2015-07-17 7:32 ` missing 64bit ports Corinna Vinschen
2015-07-17 8:39 ` Marco Atzeri
2015-07-17 9:50 ` Corinna Vinschen
2015-07-17 9:59 ` Marco Atzeri
2015-07-19 5:40 ` Marco Atzeri
2015-07-19 7:05 ` Corinna Vinschen
2015-07-19 7:18 ` Marco Atzeri
2015-07-19 8:46 ` Corinna Vinschen
2015-07-19 11:02 ` jari
2015-07-20 7:29 ` Corinna Vinschen
2015-09-03 13:58 ` Marco Atzeri
2015-09-27 15:09 ` Marco Atzeri
2015-07-17 12:53 ` Ken Brown [this message]
2015-07-17 16:35 ` Marco Atzeri
2015-07-16 8:18 ` missing 64bit ports (edit Gdocs problem) jari
2015-07-16 9:25 ` Marco Atzeri
2015-07-20 18:17 ` missing 64bit ports Jon TURNEY
2015-07-20 19:00 ` Corinna Vinschen
2015-07-22 9:08 ` Marco Atzeri
2015-09-03 13:55 ` Marco Atzeri
2015-09-03 15:45 ` Corinna Vinschen
2015-09-04 13:56 ` Jon TURNEY
2015-09-04 14:03 ` Corinna Vinschen
2015-09-07 14:01 ` Jon TURNEY
2015-09-07 15:11 ` Corinna Vinschen
2015-09-17 17:19 ` Yaakov Selkowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55A8FAA0.9020206@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).