[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Nano-devel] 2.5.1 little fry
From: |
frank |
Subject: |
Re: [Nano-devel] 2.5.1 little fry |
Date: |
Mon, 18 Jan 2016 14:12:37 +0000 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
On 17/01/2016 16:28, Benno Schulenberg wrote:
>> >(2) non existing option in configure script: --enable-altrcname
> What do you mean, non-existent? It exists.
A search for 'altrcname' in the source 2.5.1 and in the documentation draws a
blank. However, the configure script has this snippet:
# Check whether --enable-altrcname was given.
if test "${enable_altrcname+set}" = set; then :
enableval=$enable_altrcname; if test x$enableval != no; then
cat >>confdefs.h <<_ACEOF
#define RCFILE_NAME "$enableval"
_ACEOF
rcfilename=$enableval
fi
fi
In the end, it must be a documentation problem, as you say. The option didn't
make sense to me and if the entire documentation is
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
...well, let me skip my comment.
Regards
frank
- [Nano-devel] not a GPL violation?, (continued)
- Re: [Nano-devel] 2.5.1 little fry, frank, 2016/01/20
- Re: [Nano-devel] 2.5.1 little fry, Chris Allegretta, 2016/01/20
- Re: [Nano-devel] 2.5.1 little fry, frank, 2016/01/21
- Re: [Nano-devel] 2.5.1 little fry, Richard Kolb II, 2016/01/21
- Re: [Nano-devel] 2.5.1 little fry, Mike Frysinger, 2016/01/21
- Re: [Nano-devel] 2.5.1 little fry, frank, 2016/01/22
Re: [Nano-devel] 2.5.1 little fry,
frank <=