clib3r.lib(setefg): undefined symbol _EFG_Format_

I’m trying to port OpenSSL v0.9.7f.

If I use Watcom C v10.6B - it fails because of some "long long"s in the
new sources (0.9.7e did not mention them).
I dug out Watcom C v11.0beta, this one goes much further with building the
package but fails too. This time when linking, I see the message:
“clib3r.lib(setefg): undefined symbol EFG_Format

What’s wrong with it?
Am I doomed?

Tony.

“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsn69oun5o93ri4@mobile.wst.quantum.ru

I’m trying to port OpenSSL v0.9.7f.

If I use Watcom C v10.6B - it fails because of some "long long"s in the
new sources (0.9.7e did not mention them).
I dug out Watcom C v11.0beta, this one goes much further with building the
package but fails too. This time when linking, I see the message:
“clib3r.lib(setefg): undefined symbol EFG_Format

What’s wrong with it?
Am I doomed?

I think you were doomed the day you started to try to get a 10 year old
piece of software to behave like a 1 year old piece of software, lol!

I been told long long under Watcom 11 is broken, although I have use it with
success during evaluation.

Legaly you cannot use Watcom 11 beta to create commercial product.

I don’t know about OpenSSL, maybe it’s possible to go around the long long
type and simply not use it.

Sorry I couldn’t be of much help, good luck.

Tony.

Tony <mts.spb.suxx@mail.ru> wrote:

If I use Watcom C v10.6B - it fails because of some "long long"s in the

long long is NOT supported in any versions (beta or released)
of Watcom for QNX 4. Don’t waste your time on it.

On 25 Mar 2005 22:09:15 GMT, Frank Liu <fliu@usdjmp1.eng.vodafone-us.com>
wrote:

long long is NOT supported in any versions (beta or released) of Watcom
for QNX 4. Don’t waste your time on it.

Yes, I know. I just tryed to play and see…
I’ve asked OpenSSL people if they could help me to get around int64.
Roumors are OpenSSL will move their big number engine to GMP, which is
portable to QNX4.

Tony.

PS
What IS that EFG_Format ? Should it be in the clib or did I miss some
library to include?

“Tony” <mts.spb.suxx@mail.ru> wrote in message
news:opsn8mrisgo93ri4@mobile…

On 25 Mar 2005 22:09:15 GMT, Frank Liu <> fliu@usdjmp1.eng.vodafone-us.com
wrote:
long long is NOT supported in any versions (beta or released) of Watcom
for QNX 4. Don’t waste your time on it.

Yes, I know. I just tryed to play and see…
I’ve asked OpenSSL people if they could help me to get around int64.
Roumors are OpenSSL will move their big number engine to GMP, which is
portable to QNX4.

Tony.

PS
What IS that EFG_Format ? Should it be in the clib or did I miss some
library to include?

A wild guess, EFG_Format seems to be related to %f %e %g of printf, what if
you include the math lib. -lm

On Sat, 26 Mar 2005 12:17:32 +0300, Tony <mts.spb.suxx@mail.ru> wrote:

What IS that EFG_Format ? Should it be in the clib or did I miss
some library to include?
OpenSSL v0.9.7f got compiled and works OK after I included math3r.lib as

well.
(The testsuite however does not compile - one source file drives wcc386
v11.0beta into a SIGSEGV)

Now I have to find a way to do it with v10.6B…

Tony.

On Sat, 26 Mar 2005 11:22:51 -0500, Mario Charest postmaster@127.0.0.1
wrote:

A wild guess, EFG_Format seems to be related to %f %e %g of printf, what
if you include the math lib. -lm
Thanks, Mario!

:slight_smile:
I’ve found that too by grep’ing through the available libraries…

Tony.

On Fri, 25 Mar 2005 16:09:52 -0500, Mario Charest postmaster@127.0.0.1
wrote:

Legaly you cannot use Watcom 11 beta to create commercial product.
Is it legal to use OpenWatcom on windows for cross-compiling for QNX4 with

QSSL’s headers and libraryes?

Tony.