On Tue, 28 Aug 2007 06:18:57 -0400 (EDT), Thomas Dickey wrote:
It doesn't _overwrite_ userdefs.h, but many of the definitions in
userdefs.h are ignored in favor of the definitions generated (by the
configure script) in lynx_cfg.h
Sorry my English is not precise, and yes, what I intended
Hi Sébastien,
On Mon, 27 Aug 2007 21:18:30 +0200, Sébastien Hinderer wrote:
However: I am not sure that adding exim4-daemon-light to the build deps
is the right way to solve the problem.
Yes, very suspicious. I first tried to use userdefs.h but
failed to fix the problem. It seems configure
On Tue, 28 Aug 2007, Atsuhito Kohda wrote:
Hi Sébastien,
On Mon, 27 Aug 2007 21:18:30 +0200, Sébastien Hinderer wrote:
However: I am not sure that adding exim4-daemon-light to the build deps
is the right way to solve the problem.
Yes, very suspicious. I first tried to use userdefs.h but
Hi Atsuhito,
Thanks for having replied so quickly.
I didn't think it was the best way but I wanted to fix
this bug rapidly for non-i386 architecture which should be
built by buildd.
Thanks for that.
This indeed enforces the use of
exim4 as MTA, where as things will, I guess, also work
Hello everybody,
I changed a packaging since 2.8.7dev5-1 to build with pbuilder
but this means the package was built under the smallest basic
system, i.e. without sendmail, bzip2 etc. so configure failed to
find sendmail, so you was encountered this bug.
I'll fix this and the same kind of
Hi all,
On Tue, 17 Jul 2007 06:24:38 -0400 (EDT), Thomas Dickey wrote:
For example, on one of my shell accounts, following
View the file lynx.cfg.
to
See also
* compile time options
shows (just searching for mail):
system_mail_flags '-t -oi'
and
On Tue, 17 Jul 2007, Sébastien Hinderer wrote:
Hi,
Thomas Dickey :
I don't see where the problem lies: the configure script finds the same
value as the one you want to uncomment. The compiled-in value (which
you can inspect by looking at LYNXCOMPILEOPTS:/) shows this string.
I noticed the
Hi,
Thomas Dickey :
I don't see where the problem lies: the configure script finds the same
value as the one you want to uncomment. The compiled-in value (which
you can inspect by looking at LYNXCOMPILEOPTS:/) shows this string.
I noticed the very same problem on my system, and uncommenting
I don't see where the problem lies: the configure script finds the same
value as the one you want to uncomment. The compiled-in value (which
you can inspect by looking at LYNXCOMPILEOPTS:/) shows this string.
None of my configs require uncommenting the value, since it's been
working as designed
9 matches
Mail list logo
