<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi Cory and Ben,</p>
<p><br>
</p>
<p>After your email, I updated my PVSB 5.2 version, <span>recompiled from a clean build directory and reinstalled to a fresh directory.</span></p>
<p><span>Unfortunately, I can still observe the same behavior as before so the latest changes you mentioned in your email did not fix this issue.</span><br>
</p>
<p><span style="font-size:12pt">If this can help, my new sha key </span><span style="font-size:12pt">is </span><span style="font-size:12pt">ba573eace90abaeb79247e570ff4509a54e75b76.</span></p>
<p>Has anybody already tested successfully PVSB 5.2 from the install directory without loosing plugins and other module down the road?</p>
<p>Thanks.</p>
<p><br>
</p>
<p>Best regards,</p>
<p><br>
</p>
<p>Michel</p>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> Ben Boeckel <ben.boeckel@kitware.com><br>
<b>Sent:</b> Monday, February 13, 2017 3:23:41 PM<br>
<b>To:</b> Cory Quammen<br>
<b>Cc:</b> Michel Rasquin; paraview@paraview.org<br>
<b>Subject:</b> Re: [Paraview] PVSB 5.2: missing modules and plugins after "make install"</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On Sat, Feb 11, 2017 at 17:48:27 -0500, Cory Quammen wrote:<br>
> Will updating to the current superbuild master address the missing<br>
> plugins issue Michel is seeing? It looks like there have been some<br>
> minor changes on plugin handling in linux since<br>
> 4ec37480a6f1ad39c9aa3168c2f0e6a1b0147b16.<br>
<br>
Yes, it's possible. If you look at the output of the packaging step,<br>
there is probably some set of system libraries being pulled into the<br>
package which should not be there.<br>
<br>
--Ben<br>
</div>
</span></font>
</body>
</html>