All of lore.kernel.org
 help / color / mirror / Atom feed
From: James <angweiyang@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openssl failing to compile
Date: Sun, 8 Jan 2012 19:27:47 +0800	[thread overview]
Message-ID: <CAOy7-nNYwu4ZSuh_eWeGG15J-vW_2O3g9BqfT8e4iHpeHLu+RA@mail.gmail.com> (raw)
In-Reply-To: <1434677.NeCVNTM8Up@sencha>

Hi,

On Jan 5, 2012 4:37 PM, "Roman Khimov" <khimov@altell.ru> wrote:
>
> On 5 января 2012 09:50:28 James wrote:
> > >>> <gdalex@gmail.com> wrote:
> > >>>> bulding a console-image for beagleboard, openssl fails to compile.
> > >>>>
> > >>>> The log shows this:
> > >>>>
> > >>>> openssl.o: In function `main':
> > >>>> openssl.c:(.text+0x1eb): undefined reference to `BIO_s_file'
> > >>>> openssl.c:(.text+0x1f3): undefined reference to `BIO_new'
> > >>>> openssl.c:(.text+0x235): undefined reference to `BIO_ctrl'
> > >>>> .....
> > >>>>
> > >>>> Removing libdeps-first.patch solved the issue.
> > Can anyone advise on this?
>
> As written in the patch itself:
> =========
> Links to previously staged 0.9.8* easily otherwise
> =========
>
> Without this patch openssl links to any previously staged
libssl/libcrypto, if
> that was 0.9.8smth it won't work at all. I have no idea how this patch
could
> break the build. You need to carefully review the build log and especially
> compare it between different hosts, as it seems like only Ubuntu 11.10
has the
> problem.
>

Maybe a new recipe for openssl backported from current oe-core is needed in
2011.03-maintenance?

James


  reply	other threads:[~2012-01-08 11:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-21 15:09 openssl failing to compile George Alexandru Dorobantu
2011-12-29  1:23 ` James
2011-12-29  1:36   ` Neil Gruending
2011-12-29  2:17     ` James
2012-01-05  1:50       ` James
2012-01-05  8:31         ` Roman Khimov
2012-01-08 11:27           ` James [this message]
2012-01-05 14:07         ` George Alexandru Dorobantu

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=CAOy7-nNYwu4ZSuh_eWeGG15J-vW_2O3g9BqfT8e4iHpeHLu+RA@mail.gmail.com \
    --to=angweiyang@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.