<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I don't think you comment is related to this problem. Command Line Tools were also updated. The "right order" is quite simple with Spack, obviously I had whole lot of things re-compiled, including GCC, OpenMPI as well as third party packages used in Petsc.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Regards,</div><div id="AppleMailSignature">Denis<br></div><div><br>2 апр. 2017 г., в 13:43, Unal <<a href="mailto:sospinar@unal.edu.co">sospinar@unal.edu.co</a>> написал(а):<br><br></div><blockquote type="cite"><div>In my experience, each time you update Xcode, you also have to update the Command Line Tools (<a href="https://developer.apple.com/downloads/index.action?=command line tools" class="">https://developer.apple.com/downloads/index.action?=command%20line%20tools</a>), and reinstall everything again in the right order; in my case, I have to reinstall Fortran, MPI, HDF5 and PETSc. When one doesn't do it in the right order, it appears problems like what you reported.<div class=""><br class=""></div><div class="">Santiago</div><div class=""><br class=""><blockquote type="cite" class="">On 29 Mar 2017, at 07:26, Denis Davydov <<a href="mailto:davydden@gmail.com" class="">davydden@gmail.com</a>> wrote:<br class=""><br class="">Thanks Barry, I can confirm that an adaptation of your patch to 3.7.5 allows to compile PETSc.<br class=""><br class="">Regads,<br class="">Denis.<br class=""><br class=""><br class=""><blockquote type="cite" class="">On 29 Mar 2017, at 06:23, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov" class="">bsmith@mcs.anl.gov</a>> wrote:<br class=""><br class=""><br class="">I have added the commit <a href="https://bitbucket.org/petsc/petsc/commits/4f290403fdd060d09d5cb07345cbfd52670e3cbc" class="">https://bitbucket.org/petsc/petsc/commits/4f290403fdd060d09d5cb07345cbfd52670e3cbc</a> to the maint, master and next branch that allows ./configure to to go through in this situation. If the change does not break other tests it will be included in the next patch release.<br class=""><br class=""> Thanks for reporting the problem,<br class=""><br class=""> Barry<br class=""><br class="">This patch does not directly deal with the problem (which i don't understand but seems to be an Apple Xcode problem) but works around the problem on my machine.<br class=""></blockquote><br class=""></blockquote><br class=""></div></div></blockquote></body></html>