All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] exim: use a more standard build-time configuration
Date: Sat, 12 Apr 2014 18:06:35 +0200	[thread overview]
Message-ID: <20140412180635.29eae3bb@skate> (raw)
In-Reply-To: <1396816157-1828-1-git-send-email-luca@lucaceresoli.net>

Dear Luca Ceresoli,

On Sun,  6 Apr 2014 22:29:17 +0200, Luca Ceresoli wrote:
> Buildroot currently ships a very minimal build configuration file for exim,
> which disables most optional features. This is not coherent with the runtime
> configuration file, taken verbatim from the exim distribution, which enables
> some of these features.
> 
> The visible symptom is an error during boot that prevents exim from starting:
> 
>   Exim configuration error in line 541 of /etc/exim/configure:
>     router dnslookup: cannot find router driver "dnslookup"
> 
> In order to fix this problem, we change the way exim is configured at build
> time. Instead of blindly copying a minimal Buildroot-provided configuration
> file, we now copy the exim-provided one and then tweak it to change the needed
> options. This actually makes the configuration closer to standard exim.
> As the amount of tweaking is remarkable, we also define a few macros to make
> it easier and more readable.
> 
> This new approach was suggested by Bernd Kuhls.
> 
> Reported-By: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> Cc: Bernd Kuhls <bernd.kuhls@t-online.de>

Applied, thanks.

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

      reply	other threads:[~2014-04-12 16:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-06 20:29 [Buildroot] [PATCH] exim: use a more standard build-time configuration Luca Ceresoli
2014-04-12 16:06 ` Thomas Petazzoni [this message]

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=20140412180635.29eae3bb@skate \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.