Re: Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

Thanks all for the help. I could resolve both the errors: Sun-Intel : using -Wl, -Bsymbolic and resolving few other linking errors. Sun-sparc : Re-building libstdc++ all the errors gone away. Thanks again Andy for pointing it out. Regards, Mrunal On Mon, Sep 15, 2014 at 12:40 AM, Andy Polyakov

Re: Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

> While fips build on soalris, I am getting variour errors: > > Sun-Intel: > > FIPSLD_CC=gcc FIPSLD_LINK=g++ > /unixhome/upg/Unix/SunOS/i386/OpenSource/ssl-1.0.1h/bin/fipsld -fPIC > -shared -g -O2 -o libImpl.so.10.0.0 -lcrypto > Text relocation remains referenced > a

Re: Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

I hate compiling stuff on Solaris 10. The gcc version in /usr/sfw/bin is so old. And it uses the Solaris linker in /usr/ccs/bin if if you use /usr/sfw/bin/gmake instead of /usr/ccs/bin/make. Sometimes I can work around issues by renaming /usr/ccs/bin/ld and creating a symlink ld-> /usr

Linking error on Soalris x86 and sparc using fips capable openssl 1.0.1h

Hi All, While fips build on soalris, I am getting variour errors: Sun-Intel: FIPSLD_CC=gcc FIPSLD_LINK=g++ /unixhome/upg/Unix/SunOS/i386/OpenSource/ssl-1.0.1h/bin/fipsld -fPIC -shared -g -O2 -o libImpl.so.10.0.0 -lcrypto Text relocation remains referenced against sy

RE: Linking error

-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Jevin Sonut Sent: Friday, March 22, 2013 2:07 PM To: openssl-users@openssl.org Subject: Linking error HI, can anyone understand what this error means:: libeay32.lib(cryptlib.obj) : error LNK2019: unresolved external symbol

Linking error

HI, can anyone understand what this error means:: libeay32.lib(cryptlib.obj) : error LNK2019: unresolved external symbol __imp__GetUserObjectInformationW@20 referenced in function _OPENSSL_isservice libeay32.lib(cryptlib.obj) : error LNK2019: unresolved external symbol __imp__GetProcessWindowStat

RE: linking error

> From: Priyaranjan Nayak [mailto:priyaranjan4...@gmail.com] > Sent: Thursday, November 22, 2012 2:36 PM > > While build the tls server I got this link error.Below I mentioned bild log . > Can any one help me ? > > Linking console executable: bin/Debug/dtlsServer > ../openssl-1.0.1c/libssl.a(ssl_a

linking error

I'm attempting to use OpenSSL to talk to an SSL server across campus. I obtained example OpenSSL client code written in C from http://www.rtfm.com/openssl-examples and modified this code slightly to fit my needs. ssl_stuff.o is my version of the file that one time included the "main" program

Re: Linking Error.

> From: "Gisle Vanem" <[EMAIL PROTECTED]> > Date: Wed, 28 Jul 2004 20:45:38 +0200 > > "Ken Goldman" <[EMAIL PROTECTED]> said: > > > Note that both the makefile and nmake.exe are MS proprietary. You > > can't use standard makefiles with nmake, and you can't use the MS > > makefiles with a standar

Re: Linking Error.

"Ken Goldman" <[EMAIL PROTECTED]> said: > Note that both the makefile and nmake.exe are MS proprietary. You > can't use standard makefiles with nmake, and you can't use the MS > makefiles with a standard make.exe like gnu make. But you can use a GNU makefile with MS tools like cl.exe. There is

Re: Linking Error.

Ken, Thank you.Ken Goldman <[EMAIL PROTECTED]> wrote: > Thank you SO much! :) that certainly solved the linking problem> using the graphical user interface of MS visual studio, but would> you know why isn't it compiling or linking from the command line? is> there something that I must run first? an

RE: Linking Error.

[mailto:[EMAIL PROTECTED] On Behalf Of LaylaSent: Wednesday, July 28, 2004 11:59 AMTo: [EMAIL PROTECTED]Subject: RE: Linking Error. Anuj: Thank  you SO much! :) that certainly solved the linking problem using the graphical user interface of MS visual studio, but would you know why isn't it comp

Re: Linking Error.

Layla <mailto:[EMAIL PROTECTED]> *To:* [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> *Sent:* Wednesday, July 28, 2004 11:10 AM *Subject:* Re: Linking Error. Thanks for the response Vio, Actually I'm not familiar with the method you've

Re: Linking Error.

> Thank you SO much! :) that certainly solved the linking problem > using the graphical user interface of MS visual studio, but would > you know why isn't it compiling or linking from the command line? is > there something that I must run first? and does it really make any > difference whether I co

RE: Linking Error.

aSent: Wednesday, July 28, 2004 11:59 AMTo: [EMAIL PROTECTED]Subject: RE: Linking Error. Anuj: Thank  you SO much! :) that certainly solved the linking problem using the graphical user interface of MS visual studio, but would you know why isn't it compiling or linking from the command l

RE: Linking Error.

: owner-[EMAIL PROTECTED] [mailto:owner-[EMAIL PROTECTED]] On Behalf Of Layla Sent: Wednesday, July 28, 2004 8:52 AM To: [EMAIL PROTECTED] Subject: Re: Linking Error.   Weijie, Thank you for replying, does it make any difference if I compile from the command line or GUI? cause as I&#x

RE: Linking Error.

; in the end of the list of libs add the two OpenSSL libraries "libeay32.lib ssleay32.lib". I hope this helps. --Anuj -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LaylaSent: Wednesday, July 28, 2004 1:24 AMTo: [EMAIL PROTECTED]Subject: RE: Li

Re: Linking Error.

th which define where linker goes to find your lib etc. I believe the VC++ can show you somewhere of the enviornment set. You can get clues by examing the difference too.   Weijie - Original Message - From: Layla To: [EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 11:10 AM Subjec

RE: Linking Error.

j -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of LaylaSent: Wednesday, July 28, 2004 1:24 AMTo: [EMAIL PROTECTED]Subject: RE: Linking Error. David, Thanks for responding. "didn't work" is actually missing a word :), what

Re: Linking Error.

I'm not saying VC++ is failing, I'm just saying there has got to be something wrong that I'm doing which I'm hoping that someone can point out. after following the steps in the INSTALL.win32 file I ran the test as instructed and it worked fine without generating any error message, doesn't that mea

Re: Linking Error.

clues by examing the difference too.   Weijie - Original Message - From: Layla To: [EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 11:10 AM Subject: Re: Linking Error. Thanks for the response Vio, Actually I'm not familiar with the method you've prop

Re: Linking Error.

I think VC++ has a command-line tool (something like cmake, or something). If VC++ fails, maybe try DevC++. VC++/DevC++ docs are your friend :) Vio Layla wrote: Thanks for the response Vio, Actually I'm not familiar with the method you've proposed. but I tried to compile the program from comman

Re: Linking Error.

Thanks for the response Vio, Actually I'm not familiar with the method you've proposed. but I tried to compile the program from command line and It failed! I can't understand why its compiling by using GUI but not from the command prompt. I'm so new to this and this project is really very important