Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/erlang: build host-erlang with support for openssl
Date: Sun, 17 Aug 2014 11:01:26 +0200	[thread overview]
Message-ID: <20140817090126.GA5274@free.fr> (raw)
In-Reply-To: <87a973zj6w.fsf@dell.be.48ers.dk>

Peter, All,

On 2014-08-17 09:09 +0200, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> 
>  > Erlang uses openssl for all things crypto.
>  > Since there are host Erlang tools that use crypto (such as rebar), we
>  > need to build host-erlang with support for crypto, and thus it shall
>  > depends on openssl.
> 
>  > Suggested-by: Frank Hunleth <fhunleth@troodon-software.com>
>  > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
>  > Cc: Frank Hunleth <fhunleth@troodon-software.com>
>  > Cc: Johan Oudinet <johan.oudinet@gmail.com>
> 
>  > ---
>  > Note: I am not sure whether this is the correct solution, to match the
>  > host SSL support to the target SSL support. I'll let the erlang experts
>  > enhance that patch if need be. ;-)

(Sorry, I should have removed this post-comit note in this v2)
 
> Sorry, I must have missed the discussion about this. What exactly does
> it fix?

Some Erlang packages (like ejabberd) use an Erlang script to do part of
the configure and build steps, thus we need a host Erlang.

This script may need to do some crypto stuff (e.g. to compute hashes,
or do https). In the Erlang world, all crypto stuff is implemented by
using oppenssl as the crypto backend.

So, we need a host Erlang with crypto support, and thus linked with
openssl.

> Do we need it for 2014.08?

Well, it can well wait for after the release, if you're not at ease with
it. Currently, we have no package that require Erlang, not even the host
Erlang.

However, since our host-erlang not being ssl-aware, it means no one is
really using it, and thus bumping should not cause a regressiopn for
anyone.

No one, but me, has complained so far. ;-)

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-08-17  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-15 15:49 [Buildroot] [PATCH] package/erlang: build host-erlang with support for openssl Yann E. MORIN
2014-08-17  7:09 ` Peter Korsgaard
2014-08-17  9:01   ` Yann E. MORIN [this message]
2014-08-17 12:18     ` Frank Hunleth
2014-10-06 15:40 ` 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=20140817090126.GA5274@free.fr \
    --to=yann.morin.1998@free.fr \
    --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