Mailing-List:	contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe:	<mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-apps/>
List-Post:	<mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To:	mailing list cygwin-apps AT sources DOT redhat DOT com
X-Originating-IP:	[198.142.165.96]
From:	"Gareth Pearce" <tilps AT hotmail DOT com>
To:	"Gerrit P. Haase" <cygwin-apps AT cygwin DOT com>
References:	<OE16MBhe3WYIgoFT3kM000118d1 AT hotmail DOT com> <1054255839 DOT 20011115124558 AT familiehaase DOT de>
Subject:	Re: choices (nano)
Date:	Thu, 15 Nov 2001 23:16:47 +1100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
Message-ID:	<OE36EMOISkPCn0WBocN00011c00@hotmail.com>
X-OriginalArrivalTime:	15 Nov 2001 12:16:47.0891 (UTC) FILETIME=[65EF1630:01C16DCF]

> > Seems my experiences with nano not compiling OOTB are somewhat less then
I
> > was expecting ... I guess the stable branch really is more stable then
CVS
> > ... :P
> Since it is no library where changes in the API make problems for the
> applications that use it, I think it is not so critical if it is stable.
> It should work as expected for this app.
I might investigate porting the CVS maybe ... but probably not. Its what I
run on my machine ... but I dont think everyones going to be begging for the
new features in the CVS just yet...
The CVS would sort of need patching
>
> >  I could manually 'hack' the makefile.in so that it uses -lintl, but
thats
> > messy, and is certainly not a patch I could send back upstream.  So I
>
> What about:
> LIBS=-lintl ./configure --prefix=...
> ?

umm that works... - the ./configure contains sed thingies which
replace -lintl with blank in LIBS ... which I thought was what was causing
the problem in the first place... but I guess that rules that out... -
unless sed s/-lintl// only replaces one occurence... hmmm i really should
learn some of these things sometime...

guess I might try that next time - but think I will leave it as is for the
moment. - unless I need to make a significant amount of change to make it
acceptable anyway ...

Gareth

- Raw text -