19 Jun
2017
19 Jun
'17
12:26 p.m.
Hello all,
I guess one way to handle this would also be:
* add the LIBS=... workaround to the release notes * add the code to the master perl detect.pl script after the release as a bugfix (which it is) * wait a week for things to fail catastrophically * backport to release branch
Yours, Roland
On Mon, Jun 19, 2017 at 12:04:44PM -0400, Erik Schnetter wrote:
I am viewing this as a work-around -- the user would set LIBS >appropriately in their option list. I am not describing an automated >mechanism here.
Doing these things by hand correctly always works. What I want is a workaround for the automation. This ought to work for something central as MPI and something wide-spread as Linux.
Frank
--
My email is as private as my paper mail. I therefore support encrypting
and signing email messages. Get my PGP key from http://pgp.mit.edu .