public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Harold L Hunt II <huntharo@msu.edu>
To: discuss@nedit.org
Cc: cygx <cygwin-xfree@cygwin.com>
Subject: Re: Cygwin/X NEdit package maintainership
Date: Fri, 02 Jan 2004 22:15:00 -0000	[thread overview]
Message-ID: <3FF5ED47.2040009@msu.edu> (raw)
In-Reply-To: <009EE30A-3D64-11D8-B615-000A95A518CC@caltech.edu>

Nathan,

Nathan Gray wrote:

> On Jan 1, 2004, at 9:29 PM, Harold L Hunt II wrote:
> 
>> It might be wise if someone from the NEdit project would review the 
>> Cygwin/X NEdit package.  The goal would be to determine if the 
>> Cygwin/X NEdit package has any common or easily detectable 
>> platform-dependent bugs.
>>
> 
> I don't use windows/cygwin so I can't really comment on 
> platform-dependent bugs, but I can comment on platform *independent* 
> bugs, namely building with the wrong version of Lesstif/Open Motif.  As 
> long as you aren't bypassing any warnings when building NEdit 5.4 (e.g. 
> defining BUILD_BROKEN_NEDIT) things should be fine on this account.

I didn't have to define BUILD_BROKEN_NEDIT, but I don't think that 
check_lin_tif was being built in the default build for Cygwin, so the 
version of LessTif is not being checked.  When I built it manually it 
showed that 0.93.91 is an untested version, but not a version explicitly 
known to be broken.

> P.S.  Props to you for keeping your cool when dealing with the XFree86 
> project.  Very professional.  Too bad the same can't be said for them.

I think it would probably be unprofessional to comment on that publicly.  ;)

Harold



  reply	other threads:[~2004-01-02 22:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  5:29 Harold L Hunt II
2004-01-02 20:41 ` Nathan Gray
2004-01-02 22:15   ` Harold L Hunt II [this message]
2004-01-02 23:39     ` Nathan Gray
2004-01-03  3:29       ` Harold L Hunt II

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=3FF5ED47.2040009@msu.edu \
    --to=huntharo@msu.edu \
    --cc=cygwin-xfree@cygwin.com \
    --cc=discuss@nedit.org \
    /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).