From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] ssmtp: bugfix for linking error
Date: Thu, 29 Oct 2015 12:54:31 +0100 [thread overview]
Message-ID: <20151029115431.GT29389@pengutronix.de> (raw)
In-Reply-To: <1444659821-26626-1-git-send-email-oliver.graute@neuhaus.de>
On Mon, Oct 12, 2015 at 04:23:41PM +0200, Oliver Graute wrote:
> this fixes a linking error if ssl is enabled
>
> Signed-off-by: Oliver Graute <oliver.graute@neuhaus.de>
> ---
> .../0005-added-lcrypto-in-configure.patch | 21 ++++++++++++++++++++
> patches/ssmtp-2.64/series | 1 +
> 2 files changed, 22 insertions(+)
> create mode 100644 patches/ssmtp-2.64/0005-added-lcrypto-in-configure.patch
>
> diff --git a/patches/ssmtp-2.64/0005-added-lcrypto-in-configure.patch b/patches/ssmtp-2.64/0005-added-lcrypto-in-configure.patch
> new file mode 100644
> index 0000000..9d4af9a
> --- /dev/null
> +++ b/patches/ssmtp-2.64/0005-added-lcrypto-in-configure.patch
> @@ -0,0 +1,21 @@
> +From: OGR <oliver.graute@neuhaus.de>
> +Date: Mon, 12 Oct 2015 16:11:43 +0200
> +Subject: [PATCH] added -lcrypto in configure
> +
> +---
> + configure | 2 +-
> + 1 file changed, 1 insertion(+), 1 deletion(-)
> +
> +diff --git a/configure b/configure
> +index 5b6e2c7..7146fdf 100755
> +--- a/configure
> ++++ b/configure
> +@@ -1562,7 +1562,7 @@ if test x$enableval = xyes ; then
> + #define HAVE_SSL 1
> + EOF
> +
> +- LIBS="$LIBS -lssl"
> ++ LIBS="$LIBS -lssl -lcrypto"
This should not be necessary:
0004-configure-if-using-ssl-link-against-libcrypto-too.patch makes this
change for configure.in and autogen.sh should generate configure from this.
Maybe you copied the patches to a BSP and got a broken autogen.sh?
Michael
> + fi
> + enableval=""
> +
> diff --git a/patches/ssmtp-2.64/series b/patches/ssmtp-2.64/series
> index b89ac63..9428329 100644
> --- a/patches/ssmtp-2.64/series
> +++ b/patches/ssmtp-2.64/series
> @@ -4,4 +4,5 @@
> 0002-use-DESTDIR-when-installing.patch
> 0003-make-installing-non-interactive.patch
> 0004-configure-if-using-ssl-link-against-libcrypto-too.patch
> +0005-added-lcrypto-in-configure.patch
> # 4ac054ecac57de7c903a18a4dfcd2270 - git-ptx-patches magic
> --
> 1.7.9.5
>
>
> --
> ptxdist mailing list
> ptxdist@pengutronix.de
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-10-29 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 14:23 Oliver Graute
2015-10-29 11:54 ` Michael Olbrich [this message]
2015-10-29 12:16 ` Oliver Graute
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=20151029115431.GT29389@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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