All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frank Hunleth <fhunleth@troodon-software.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] ejabberd: new package
Date: Wed, 13 Aug 2014 17:23:39 -0400	[thread overview]
Message-ID: <CA+-urNTFkncEkOxKbyBiqLGAHP=94sfbaz-b-27LnkcvJpkh0g@mail.gmail.com> (raw)
In-Reply-To: <20140813204443.GH3939@free.fr>

Yann, All,

On Wed, Aug 13, 2014 at 4:44 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
>
> Frank, All,
>
> On 2014-08-13 14:48 -0400, Frank Hunleth spake thusly:
> > On Mon, Aug 11, 2014 at 6:50 AM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > > Johan, All,
> > >
> > > On 2014-08-11 12:33 +0200, Yann E. MORIN spake thusly:
> > >> On 2014-08-11 11:36 +0200, Johan Oudinet spake thusly:
> > >> > On Wed, Aug 6, 2014 at 10:23 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> > > [--SNIP--]
> > >> > > And it fails at build time, with a lengthy error message, that I do not
> > >> > > completely grasp:
> > >> > >
> > >> > >     /home/ymorin/dev/buildroot/O/host/usr/lib/erlang/bin/escript rebar
> > >> > > get-deps && :> deps/.got
> > >> > >     ==> rel (get-deps)
> > >> > >     Uncaught error in rebar_core: {'EXIT',
> > >> > >                                    {badarg,
> > >> >
> > >> > Very strange. It looks like the rebar script didn't accept the
> > >> > get-deps argument.
> > >> > Could you try with the same defconfig as mine to see if the problem
> > >> > comes from there.
> > > [--SNIP--]
> > >> I'll check in a 32-bit chroot to see if the error is the same.
> > >
> > > OK, here's what it has to say when run in a 32-bit sueeze chroot:
> > >
> > >     ---8<---
> > >     /home/ymorin/dev/buildroot/O/host/usr/lib/erlang/bin/escript rebar get-deps && :> deps/.got
> > >     Uncaught error in rebar_core: {'EXIT',
> > >                                    {undef,
> > >                                     [{crypto,start,[],[]},
> > >                                      {rebar,run_aux,2,
> > >                                       [{file,"src/rebar.erl"},{line,143}]},
> > >                                      {rebar,main,1,
> > >                                       [{file,"src/rebar.erl"},{line,58}]},
> > >                                      {escript,run,2,
> > >                                       [{file,"escript.erl"},{line,752}]},
> > >                                      {escript,start,1,
> > >                                       [{file,"escript.erl"},{line,276}]},
> > >                                      {init,start_it,1,[]},
> > >                                      {init,start_em,1,[]}]}}
> > >     make[2]: *** [deps/.got] Error 1
> > >     ---8<---
> >
> > I think that you can get this error if host erlang is compiled without
> > openssl. Maybe you don't have the openssl headers installed on your
> > system and Johan does?
>
> Alas, no better luck.
>
> I did de-install my libssl-dev package, so I only get the runtime from
> openssl, and not the development files.
>
> Then, I did three tests, all starting afresh from a clean tree, with the
> ejabberd patch applied on top of master (e3bb4ac: fbv: fix typo in
> pkg-config variable):
>
>   - with just the patch;
>   - then with a modified erlang.mk to compile our host erlang without ssl;
>   - then with a modified erlang.mk to compile our host erlang with ssl.
>
> All three build failed in the exact same way.

Do you have an output/host/usr/lib/erlang/lib/crypto-3.3/priv/lib
directory with a couple shared libraries in it? I assume not based on
the failure, but wanted to check.

Also, does the log from Erlang's ./configure provide any clues?

FWIW, everything that you're doing sounds good to me. I've only seen
the "crypto" undef error on targets when I've forgotten to enable
openssl. I've never seen it on the host, but my host has a lot of
header files, so it's probably not a good test.

>
> To disable ssl, I did:
>     HOST_ERLANG_CONF_OPT += --without-ssl
>
> To enable ssl, I did:
>     HOST_ERLANG_CONF_OPT += --with-ssl
>     HOST_ERLANG_DEPENDENCIES += host-openssl
>
> 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-13 21:23 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 12:33 [Buildroot] [PATCH v3] ejabberd: new package Johan Oudinet
2014-07-18 21:35 ` Yann E. MORIN
2014-07-18 23:58   ` Johan Oudinet
2014-07-19  9:17     ` Yann E. MORIN
2014-07-20  9:33 ` Thomas Petazzoni
2014-08-06 10:30   ` Johan Oudinet
2014-08-06 19:40     ` Yann E. MORIN
2014-08-06 20:23 ` Yann E. MORIN
2014-08-11  9:36   ` Johan Oudinet
2014-08-11 10:07     ` Johan Oudinet
2014-08-11 10:13       ` Yann E. MORIN
2014-08-11 10:33     ` Yann E. MORIN
2014-08-11 10:50       ` Yann E. MORIN
2014-08-13 18:48         ` Frank Hunleth
2014-08-13 19:51           ` Yann E. MORIN
2014-08-13 20:44           ` Yann E. MORIN
2014-08-13 21:23             ` Frank Hunleth [this message]
2014-08-13 21:49               ` Yann E. MORIN
2014-08-13 22:18                 ` Yann E. MORIN
2014-08-14 12:40                   ` Frank Hunleth
2014-08-14 22:36                     ` Yann E. MORIN
2014-08-11 13:13       ` Johan Oudinet
2014-08-12 15:13         ` Yann E. MORIN
2014-10-11 16:21 ` Yann E. MORIN
2014-10-16 12:38   ` Johan Oudinet
2014-10-17 20:18     ` Yann E. MORIN
2014-10-17 23:06     ` Arnout Vandecappelle
2014-10-18 10:00       ` Yann E. MORIN
2014-10-18 10:31         ` Johan Oudinet
2014-10-27 14:42           ` Johan Oudinet
2014-10-27 14:47             ` 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='CA+-urNTFkncEkOxKbyBiqLGAHP=94sfbaz-b-27LnkcvJpkh0g@mail.gmail.com' \
    --to=fhunleth@troodon-software.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.