From: Robert Yang <liezhi.yang@windriver.com>
To: Saul Wold <sgw@linux.intel.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] openssl: Upgrade to 1.0.2
Date: Mon, 16 Mar 2015 14:21:56 +0800 [thread overview]
Message-ID: <55067684.7080409@windriver.com> (raw)
In-Reply-To: <5501E65D.3010107@linux.intel.com>
On 03/13/2015 03:17 AM, Saul Wold wrote:
> On 03/11/2015 11:18 PM, Robert Yang wrote:
>>
>> I met this error when building openflow in meta-networking, I guess it
>> maybe
>> related to the upgraded:
>>
>> x86_64-wrs-linux-gcc -m64 -march=core2 -mtune=core2 -msse3 -mfpmath=sse
>> --sysroot=/buildarea/lyang1/test_qemux86-64/bitbake_build/tmp/sysroots/qemux86-64
>> -Wstrict-prototypes -O2 -pipe -g -feliminate-unused-debug-types -Wall
>> -Wno-sign-compare -Wpointer-arith -Wdeclaration-after-statement
>> -Wformat-security -Wswitch-enum -Wunused-parameter -Wstrict-aliasing
>> -Wbad-function-cast -Wcast-align -Wstrict-prototypes
>> -Wold-style-definition -Wmissing-prototypes -Wmissing-field-initializers
>> -Wno-override-init -export-dynamic -Wl,-O1 -Wl,--hash-style=gnu
>> -Wl,--as-needed -o secchan/ofprotocol secchan/discovery.o
>> secchan/emerg-flow.o secchan/fail-open.o secchan/failover.o
>> secchan/in-band.o secchan/port-watcher.o secchan/protocol-stat.o
>> secchan/ratelimit.o secchan/secchan.o secchan/status.o
>> secchan/stp-secchan.o lib/libopenflow.a -ldl
>> -L/buildarea/lyang1/test_qemux86-64/bitbake_build/tmp/sysroots/qemux86-64/usr/lib64
>>
>> -lssl
>> /buildarea/lyang1/test_qemux86-64/bitbake_build/tmp/sysroots/x86_64-linux/usr/libexec/x86_64-wrs-linux/gcc/x86_64-wrs-linux/4.9.2/ld:
>>
>> lib/libopenflow.a(vconn-ssl.o): undefined reference to symbol
>> 'ERR_error_string@@OPENSSL_1.0.0'
>> /buildarea/lyang1/test_qemux86-64/bitbake_build/tmp/sysroots/qemux86-64/lib64/libcrypto.so.1.0.0:
>>
>> error adding symbols: DSO missing from command line
>> collect2: error: ld returned 1 exit status
>>
> Robert, I am not sure about this, I just verified that ERR_error_string is a
> valid symbol in libcrypto.so, maybe you nbeed to have -lcrypto in addition to
> the -lssl on the command line for building openflow? I don't see it explicitly
> and maybe that's needed.
Yes, add -lcrypto works.
// Robert
>
> Sau!
>
>
>
next prev parent reply other threads:[~2015-03-16 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-04 17:46 [PATCH] openssl: Upgrade to 1.0.2 Saul Wold
2015-03-12 6:18 ` Robert Yang
2015-03-12 19:17 ` Saul Wold
2015-03-16 6:21 ` Robert Yang [this message]
2015-03-13 13:46 ` Martin Jansa
2015-03-16 5:41 ` Saul Wold
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=55067684.7080409@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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