Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/mutt: specify the mailpath
Date: Sun, 30 Nov 2014 15:15:15 +0100	[thread overview]
Message-ID: <20141130151515.3af7e775@free-electrons.com> (raw)
In-Reply-To: <1417258556-16797-1-git-send-email-yann.morin.1998@free.fr>

Dear Yann E. MORIN,

On Sat, 29 Nov 2014 11:55:56 +0100, Yann E. MORIN wrote:
> mutt's ./configure looks for different paths for where to look for
> incoming mails.
> 
> This is absolutely worng in the case of cross-compilation, because the
> path it may find on the host may not exist on the target.
> 
> Not only that, but some host may not even have any of the paths
> ./configure looks for.
> 
> Fix that by specifying the mailpath, and set it to the value documented
> in the FHS [0]
> 
> Since Buildroot only guarantees /tmp to be writable, make /var/mail a
> symlink to /tmp .
> 
> [0] http://refspecs.linuxfoundation.org/FHS_2.3/fhs-2.3.html#VARMAILUSERMAILBOXFILES
> 
> Reported-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> ---
>  package/mutt/mutt.mk | 7 +++++++
>  1 file changed, 7 insertions(+)

At this point, I'm not sure if this is still material for master
(2014.11) or for next.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-11-30 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-29 10:55 [Buildroot] [PATCH] package/mutt: specify the mailpath Yann E. MORIN
2014-11-30 14:15 ` Thomas Petazzoni [this message]
2014-11-30 14:25   ` Yann E. MORIN
2014-12-07 23:05 ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141130151515.3af7e775@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox