Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] syslog-ng: Specify location of libesmtp
Date: Tue, 20 Oct 2015 21:32:57 +0200	[thread overview]
Message-ID: <877fmhl4ie.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20151020205728.6f2d2332@gmx.net> (Peter Seiderer's message of "Tue, 20 Oct 2015 20:57:28 +0200")

>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:

Hi,

 >> SYSLOG_NG_CONF_OPTS += --disable-smtp
 >> endif

 > The buildroot package libestmp provides a libesmtp-config script, but
 > it is installed into

 > 	host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/bin/libesmtp-config

 > where it is not found by the syslog-ng configure script... 

Yes, $(STAGING_DIR)/usr/bin, similar to the other *-config scripts.

 > Would a more portable solution be to add this search path (or fix the install
 > location of libestmp-config) for the syslog-ng configure call (libesmtp-config
 > --libs gives '-pthread -L[...]/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/lib
 > -lesmtp -lssl -lcrypto -ldl')?

$(STAGING_DIR)/usr/bin contains binaries for the target (and *-config
scripts), so it shouldn't be added to the path, but another approach is
indeed to fix the configure script to look elsewhere for the script,
similar to how a bunch of packages allow the path to sdl-config to be
overridden through the SDL_CONFIG environment variable.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2015-10-20 19:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20  8:16 [Buildroot] [PATCH] syslog-ng: Specify location of libesmtp Chris Packham
2015-10-20  9:36 ` Peter Korsgaard
2015-10-20  9:40   ` Chris Packham
2015-10-20 10:03     ` Peter Korsgaard
2015-10-20 18:57 ` Peter Seiderer
2015-10-20 19:32   ` Peter Korsgaard [this message]
2015-10-21  7:41     ` Chris Packham
2015-10-21  8:27       ` Thomas Petazzoni
2015-10-21  9:45         ` Peter Korsgaard

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=877fmhl4ie.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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