Matthias Apitz schrieb am Mittwoch, den 05. August 2015:
> I digged into this and the reason is in the source tree of mutt itself.
>
> The option (...) strings get punched into a file conststrings.c and if you
> build mutt
> with 'make' it gives an error due to a gmake'ish construct in the Make
- Forwarded message from Matthias Apitz -
Date: Wed, 5 Aug 2015 08:15:29 +0200
From: Matthias Apitz
To: freebsd-po...@freebsd.org
Subject: Re: broken strings compiled-in into mutt
El día Tuesday, August 04, 2015 a las 09:48:24PM +0200, Kurt Jaeger escribió:
> Hi!
>
> > H
El día Tuesday, August 04, 2015 a las 04:54:58PM +0200, Matthias Apitz escribió:
> Hello,
>
> I have compiled on FreeBSD CURRENT some 1660 ports, among them my
> beloved mutt, and all went fine. I wanted to check mutt if it has used the
> correct compiler options and configure value and have run
(sorry, if this comes twice; I used the wrong From addr)
Hello,
I have compiled on FreeBSD CURRENT some 1660 ports, among them my
beloved mutt, and all went fine. I wanted to check mutt if it has used the
correct compiler options and configure value and have run
$ mutt -v
The output is broken
