This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Seg fault in home-built mutt
- From: news at garydjones dot mailshell dot com
- To: cygwin at cygwin dot com
- Date: Thu, 20 Feb 2003 18:43:54 +0100
- Subject: Re: Seg fault in home-built mutt
- References: <03Feb18.233048-0800_pst.294445-7528+101@lmg.ahnet.net> <20030220145004.GI1744@tishler.net>
On 20 Feb 2003, Jason Tishler <jason at tishler dot net> wrote:
> On Tue, Feb 18, 2003 at 09:01:20PM +0100,
> news at garydjones dot mailshell dot com wrote:
>> I managed to get mutt built at the weekend such that
>> the dotlock stuff was external. The build I made was
>> as follows:
>> Mutt 1.4i (2002-05-29)
>> [snip]
>> System: CYGWIN_98-4.10 1.3.20(0.73/3/2) (i686) [using
>> ncurses 5.2] Compile options:
>> -DOMAIN
>> -DEBUG
>> -HOMESPOOL -USE_SETGID -USE_DOTLOCK +DL_STANDALONE
>> ^^^^^^^^^^^^
>
> Shouldn't the above be +USE_DOTLOCK?
I'm not sure. I said:
$ ./configure --enable-external-dotlock --enable-buffy-size --enable-locales-fix
(the first option per your email at
http://www.cygwin.com/ml/cygwin/2002-09/msg00816.html, as
it happens :) and that's what the resulting 'make install'
produced.
> I have a private mutt build with the following
> configuration:
[snip]
> Do you want me to send it to you to see if it works with
> your testcase?
TBH I would prefer to know what the config was that Gary R.
Van Sickle used so that I can include/exclude features
until I find out what feature is responsible. Otherwise I
(might) get a mutt which works but whatever bug might be
lying around in the code would remain. Thanks though, I
appreciate the thought.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/