<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi again :-D<br>
<br>
So... I compile with gcc -O1 instead of -O2 (not mentioned in
INSTALL file anyway) and got it compiled !<br>
There was a lot of warnings but seems to be normal ... some about
#pragma push ... some others but it works.<br>
I do this only for stunnel-stunnel.o/stunnel.c then for others left
files I do normal makefile gcc -O2 ... all goes right (except for
warnings) !<br>
Seems good ... wanted to do "make check" to be sure ... but "nothing
to do" each time.<br>
<br>
Seems good but not sure at all ... should test a bit more ...<br>
<br>
No clues ? No idea ? Also, I could stick with stunnel 3.22 sure it
will be enough for what I need ...<br>
Alex.<br>
<br>
<div class="moz-cite-prefix">Le 30/01/2015 16:45, amontaron wrote :<br>
</div>
<blockquote cite="mid:54CBA72B.1090405@wanadoo.fr" type="cite">Hi
everybody !
<br>
<br>
I tried to compile stunnel 5.10 (latest) on my old Suse 7 Linux
distrib and got "a fatal signal 11 error message" when doing the
make command.
<br>
<br>
Just before, openssl 1.0.2 (latest) compile fine with no errors.
<br>
Also, I add some stuffs like xemacs 21.4.22 (latest) just to say
that that rather old distrib is able to do all that :-D
<br>
<br>
So, here is the latest messages from make I got :
<br>
<blockquote type="cite">Making all in src
<br>
make[1]: Entering directory `/root/stunnel-5.10/src'
<br>
make all-am
<br>
make[2]: Entering directory `/root/stunnel-5.10/src'
<br>
source='stunnel.c' object='stunnel-stunnel.o' libtool=no \
<br>
DEPDIR=.deps depmode=gcc /bin/sh ../auto/depcomp \
<br>
gcc -DHAVE_CONFIG_H -I. -I/usr/kerberos/include
-I/usr/local/ssl/include -DLIBDIR='"/usr/local/lib/stunnel"'
-DCONFDIR='"/usr/local/etc/stunnel"' -g <font color="#ff0000">-O2</font>
-pthread -Wall -Wformat=2 -Wconversion -Wno-long-long
-Wno-deprecated-declarations -D_FORTIFY_SOURCE=2 -c -o
stunnel-stunnel.o `test -f 'stunnel.c' || echo './'`stunnel.c
<br>
In file included from /usr/include/string.h:346,
<br>
from common.h:201,
<br>
from stunnel.c:38:
<br>
/usr/include/bits/string2.h: In function `__strsep_g':
<br>
/usr/include/bits/string2.h:1171: warning: passing arg 2 of
`__strpbrk_c2' with different width due to prototype
<br>
/usr/include/bits/string2.h:1171: warning: passing arg 3 of
`__strpbrk_c2' with different width due to prototype
<br>
/usr/include/bits/string2.h:1171: warning: passing arg 2 of
`__strpbrk_c3' with different width due to prototype
<br>
/usr/include/bits/string2.h:1171: warning: passing arg 3 of
`__strpbrk_c3' with different width due to prototype
<br>
/usr/include/bits/string2.h:1171: warning: passing arg 4 of
`__strpbrk_c3' with different width due to prototype
<br>
<font color="#ff0000">gcc: Internal compiler error: program cc1
got fatal signal 11
</font><br>
make[2]: *** [stunnel-stunnel.o] Error 1
<br>
make[2]: Leaving directory `/root/stunnel-5.10/src'
<br>
make[1]: *** [all] Error 2
<br>
make[1]: Leaving directory `/root/stunnel-5.10/src'
<br>
make: *** [all-recursive] Error 1
<br>
</blockquote>
Previously got lots of warning messages. Perhaps need "make
report" also ?
<br>
<br>
I've look at <a class="moz-txt-link-abbreviated" href="mailto:stunnel-users@stunnel.org">stunnel-users@stunnel.org</a> mail archive up to July
2011 with no success. So, that's why I'm writting to you there...
<br>
<br>
Then, I tried different versions of stunnel 4.xx like 4.00, 4.56,
4.28 and more. All simply don't compile with differents errors
messages.
<br>
The only one I could compile completly is stunnel 3.22 (so latest
3.xx)
<br>
Note that I'm happy with that because I was running stunnel 3.3
just before and that everything works with the latest openssl
version I download and everything works fine for what I would !
<br>
<br>
Remark: Suse7 distrib (not OpenSuse) is Linux 2.2.16 kernel (not
latest :-D)
<br>
<br>
Alex.
<br>
PS: Another things, on the same machine I ran stunnel 4.56 on
(old) Windows 98 with no problems.
<br>
<br>
</blockquote>
<br>
<br /><br />
<hr style='border:none; color:#909090; background-color:#B0B0B0; height: 1px; width: 99%;' />
<table style='border-collapse:collapse;border:none;'>
<tr>
<td style='border:none;padding:0px 15px 0px 8px'>
<a href="http://www.avast.com/">
<img border=0 src="http://static.avast.com/emails/avast-mail-stamp.png" />
</a>
</td>
<td>
<p style='color:#3d4d5a; font-family:"Calibri","Verdana","Arial","Helvetica"; font-size:12pt;'>
Ce courrier électronique ne contient aucun virus ou logiciel malveillant parce que la protection <a href="http://www.avast.com/">Antivirus avast!</a> est active.
</p>
</td>
</tr>
</table>
<br />
</body>
</html>