DevHeads.net

Postings by Orion Poplawski

documentation issue

<a href="http://www.postfix.org/TLS_README.html#client_tls_reuse" title="http://www.postfix.org/TLS_README.html#client_tls_reuse">http://www.postfix.org/TLS_README.html#client_tls_reuse</a> contains this:

To enable multiple deliveries per TLS connection, specify:

/etc/postfix/main.cf:
smtp_tls_connection_reuse = yes

However, that does not appear to be a valid postfix option.

plplot 5.13.0 soname bump

I'll be buiding plplot 5.13 and dependencies shortly. This has a soname
bump.

Intent to retire StarCluster and python-iptools

I'm going to be retiring StarCluster and its dependency python-iptools
shortly. Upstream is dead and I'm not using it.

libdap 3.19.1 soname bump

I'll be building libdap 3.19.1 soon in rawhide. This includes a soname
bump so dependencies will be rebuilt as well.

Help with strict-aliasing warning

I'm getting:

/builddir/build/BUILD/gdl-0.9.8/src/basic_pro_jmg.cpp: In function 'void
lib::linkimage(EnvT*)':
/builddir/build/BUILD/gdl-0.9.8/src/basic_pro_jmg.cpp:159:36: warning:
dereferencing type-punned pointer will break strict-aliasing rules
[-Wstrict-aliasing]
(BaseGDL* &) dynFun[count_fun] =
~~~~~~~~~~~~~~~~^
(BaseGDL*) dlsym(module[count], entryName.c_str());

dynFun is defined as:

BaseGDL*(*dynFun[MAXNDLL/2])( EnvT* e);

This is all beyond me. Missing the function pointer argument specification?

Thanks.

New gdl segfaults with gcc 8 in antlr

I've just discovered that gdl appears to be segfaulting a lot now deep
in the antlr c++ generated parser code with the switch to gcc 8. Has
anyone else run into similar issues?