From: Neil Gruending <neil@gruending.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: openssl failing to compile
Date: Wed, 28 Dec 2011 17:36:36 -0800 [thread overview]
Message-ID: <CACj0d1jmq+XG=ksy5QTr9DsNs7xRZKVCtKwiSqXcJ=UGWDD_Pw@mail.gmail.com> (raw)
In-Reply-To: <CAOy7-nOSQ1-SjHjYqKo4t-N=ZDo7FPoEGBdTbabtTBSd78Cczw@mail.gmail.com>
I have the same issue. After some Googling it appears to only affect
Ubuntu 11.10?
Neil
On Wed, Dec 28, 2011 at 5:23 PM, James <angweiyang@gmail.com> wrote:
> Hi all,
>
> On Wed, Dec 21, 2011 at 11:09 PM, George Alexandru Dorobantu
> <gdalex@gmail.com> wrote:
>> Hello list,
>>
>> 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.
>>
>> Does anyone know if libdeps-first.patch is really needed?
>> If not, could it be removed?
>>
>>
>> Thank you
>> George A. Dorobantu
>
> I'm too experiencing this issue with my overo board too and is
> currently using the same hack to get pass openssl compilation problem.
>
> Please backport openssl from oe-core to oe-classic to solve this once
> and for all?
>
> Thanks.
>
> --
> Regards,
> James
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2011-12-29 1:43 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 [this message]
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
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='CACj0d1jmq+XG=ksy5QTr9DsNs7xRZKVCtKwiSqXcJ=UGWDD_Pw@mail.gmail.com' \
--to=neil@gruending.net \
--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.