0002379: openssl issue: openssl version mismatch

(0009372)
codemastr (reporter)
2005-02-28 20:16

Have you tried recompiling Unreal? (make clean && make)

(0009373)
ron330 (reporter)
2005-03-01 03:40

yup still does it i had to disable the ssl to get rid of the message

(0009375)
crazy (reporter)
2005-03-01 04:26
edited on: 2005-03-01 04:37

I know that warning :) (whit openssl and ziplib headers).Don't ask me why but you need to : make clean && ./Config (or ./Config -q) && make

*EDIT *blind* Don't do ./Config -q you have ssl disabled :o just ./Config *EDIT

(0009380)
syzop (administrator)
2005-03-01 12:46
edited on: 2005-03-01 12:46

(I typed a similar msg yesterday, but mantis was down and my browser did not let me resubmit my text)
Well..
'OpenSSL 0.9.7c 30 Sep 2003'
'OpenSSL 0.9.7c-p1 30 Sep 2003'
is not the same, hence the warning.

But *IN THIS PARTICULAR CASE* it is probably a harmless warning because the difference is at patch level (the -p1) there shouldn't be any binary incompatibilities introduced.
Of course, if you get something like 0.9.7c vs 0.9.7d, it's a different story and you should recompile then.
[I know, perhaps we should parse the version thing, but.. blah :P]

(0009381)
ron330 (reporter)
2005-03-01 13:01

yeah that's what i ended up doing was just disabling the sssl till i found out how to fix it right. i'll have to try the make clean && tonight and see if that fixes it.

(0016213)
ohnobinki (developer)
2010-07-16 18:43

So... the ``fix'' to this would be ignoring ``-p1'' from ssl's versioning values? Has anyone else ever encountered this problem recently?

From the number of years of no activity on this bug, I think that a change isn't needed.

Issue History
Date Modified	Username	Field	Change
2005-02-28 19:45	ron330	New Issue
2005-02-28 20:16	codemastr	Note Added: 0009372
2005-03-01 03:40	ron330	Note Added: 0009373
2005-03-01 03:40	ron330	Issue Monitored: ron330
2005-03-01 04:26	crazy	Note Added: 0009375
2005-03-01 04:27	crazy	Issue Monitored: crazy
2005-03-01 04:37	crazy	Note Edited: 0009375
2005-03-01 12:46	syzop	Note Added: 0009380
2005-03-01 12:46	syzop	Note Edited: 0009380
2005-03-01 13:01	ron330	Note Added: 0009381
2005-03-01 16:13	syzop	Severity	major => tweak
2005-03-01 16:13	syzop	Summary	major openssl issue => openssl issue: openssl version mismatch
2006-11-12 14:34	syzop	Status	new => acknowledged
2006-11-12 14:34	syzop	Relationship added	child of 0003111
2006-11-16 15:21	aquanight	Category	documentation => ircd
2007-09-06 10:10	syzop	Relationship added	child of 0003454
2008-12-23 15:54	syzop	Relationship deleted	child of 0003454
2010-07-14 20:46	syzop	Relationship added	child of 0003776
2010-07-16 18:43	ohnobinki	Note Added: 0016213
2010-09-06 10:19	syzop	Relationship deleted	child of 0003776

Notes
(0009372) codemastr (reporter) 2005-02-28 20:16	Have you tried recompiling Unreal? (make clean && make)

(0009373) ron330 (reporter) 2005-03-01 03:40	yup still does it i had to disable the ssl to get rid of the message

(0009375) crazy (reporter) 2005-03-01 04:26 edited on: 2005-03-01 04:37	I know that warning :) (whit openssl and ziplib headers).Don't ask me why but you need to : make clean && ./Config (or ./Config -q) && make EDIT blind* Don't do ./Config -q you have ssl disabled :o just ./Config *EDIT

(0009380) syzop (administrator) 2005-03-01 12:46 edited on: 2005-03-01 12:46	(I typed a similar msg yesterday, but mantis was down and my browser did not let me resubmit my text) Well.. 'OpenSSL 0.9.7c 30 Sep 2003' 'OpenSSL 0.9.7c-p1 30 Sep 2003' is not the same, hence the warning. But IN THIS PARTICULAR CASE it is probably a harmless warning because the difference is at patch level (the -p1) there shouldn't be any binary incompatibilities introduced. Of course, if you get something like 0.9.7c vs 0.9.7d, it's a different story and you should recompile then. [I know, perhaps we should parse the version thing, but.. blah :P]

(0009381) ron330 (reporter) 2005-03-01 13:01	yeah that's what i ended up doing was just disabling the sssl till i found out how to fix it right. i'll have to try the make clean && tonight and see if that fixes it.

(0016213) ohnobinki (developer) 2010-07-16 18:43	So... the ``fix'' to this would be ignoring ``-p1'' from ssl's versioning values? Has anyone else ever encountered this problem recently? From the number of years of no activity on this bug, I think that a change isn't needed.