Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/exim: bump version to 4.90
Date: Mon, 26 Mar 2018 23:17:01 +0200	[thread overview]
Message-ID: <20180326231701.3ec7d95d@windsurf.home> (raw)
In-Reply-To: <20180129232524.5fadcbd8@windsurf.lan>

Hello Bernd,

Ping ? If you don't answer the review comments, we can't really move
forward with merging this patch :-/

Thomas

On Mon, 29 Jan 2018 23:25:24 +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Sat, 27 Jan 2018 23:51:23 +0100, Bernd Kuhls wrote:
> 
> >  ifeq ($(BR2_PACKAGE_OPENSSL),y)
> > -EXIM_DEPENDENCIES += openssl
> > +EXIM_DEPENDENCIES += host-openssl openssl  
> 
> This looks suspicious. Why are you bringing host-openssl when target
> OpenSSL support is enabled ? Is the OpenSSL support in the macro_predef
> program needed for target SSL support to work ? What does OpenSSL
> support in macro_predef actually brings ?
> 
> >  define EXIM_USE_DEFAULT_CONFIG_FILE_OPENSSL
> >  	$(call exim-config-change,SUPPORT_TLS,yes)
> >  	$(call exim-config-change,USE_OPENSSL_PC,openssl)
> > @@ -120,9 +120,17 @@ ifeq ($(BR2_STATIC_LIBS),y)
> >  EXIM_STATIC_FLAGS = LFLAGS="-pthread --static"
> >  endif
> >  
> > +# We need the host version of macro_predef during the build, before
> > +# building it we need to prepare the makefile.
> >  # "The -j (parallel) flag must not be used with make"
> >  # (http://www.exim.org/exim-html-current/doc/html/spec_html/ch04.html)
> >  define EXIM_BUILD_CMDS
> > +	$(TARGET_MAKE_ENV) build=br $(MAKE1) -C $(@D) makefile
> > +	$(HOST_MAKE_ENV) $(MAKE1) -C $(@D)/build-br macro_predef \
> > +		CC=$(HOSTCC) \
> > +		LNCC=$(HOSTCC) \
> > +		CFLAGS="$(HOST_CFLAGS)" \
> > +		LFLAGS="-fPIC $(HOST_LDFLAGS)"  
> 
> Meh, this is not nice. Perhaps we could submit a patch upstream that
> adds support for CC_FOR_BUILD, CFLAGS_FOR_BUILD, LFLAGS_FOR_BUILD, so
> that we don't need a separate build step. This could be useful for
> other projects.
> 
> Best regards,
> 
> Thomas



-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-03-26 21:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27 22:51 [Buildroot] [PATCH 1/2] package/berkeleydb: add host variant Bernd Kuhls
2018-01-27 22:51 ` [Buildroot] [PATCH 2/2] package/exim: bump version to 4.90 Bernd Kuhls
2018-01-29 22:25   ` Thomas Petazzoni
2018-03-26 21:17     ` Thomas Petazzoni [this message]
2019-07-23 17:26     ` Bernd Kuhls

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=20180326231701.3ec7d95d@windsurf.home \
    --to=thomas.petazzoni@bootlin.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