<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Matt,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>This is not as simple as you try to make it out to be. Just moving a -l upstream does not resolve all the issues. There are other considerations as well.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>-Ross<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Matthew Knepley [mailto:knepley@gmail.com] <br><b>Sent:</b> Friday, November 22, 2013 1:37 PM<br><b>To:</b> Bartlett, Roscoe A.<br><b>Cc:</b> Jed Brown; Barry Smith; petsc-trilinos-discussion@lists.mcs.anl.gov<br><b>Subject:</b> Re: [Petsc-trilinos-discussion] Scope and requirements<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><div><div><div><p class=MsoNormal>On Fri, Nov 22, 2013 at 12:32 PM, Bartlett, Roscoe A. <<a href="mailto:bartlettra@ornl.gov" target="_blank">bartlettra@ornl.gov</a>> wrote:<o:p></o:p></p><div><p class=MsoNormal style='margin-bottom:12.0pt'>> > 3) Before Hydra-TH get coupled into any other code, we need to remove<br>> > the direct insertion of ML support in the PETSc lib and defer it to<br>> > Hydra-TH or some other downstream lib that uses dependency injection<br>> > to overcome the link order issue.<br>><br>> What is the "link order issue"? AFAIK, ML never depends on PETSc, so<br>> there is no dependency loop. In any case, registering the ML plugin<br>> later is a pure build system issue (no source code changes).<o:p></o:p></p></div><p class=MsoNormal>[Bartlett, Roscoe A.]<br><br>ML gets built along with the rest of Trilinos as a TriBITS package in VERA where PETSc is treated as a pre-built static TPL. This is done because changes are being made to Trilinos to drive CASL work but not for PETSc. Building PETSc downstream from Trilinos would mean wrapping PETSc as a TriBITS package and we don't want to go there unless we are forced to do so. There are a lot of complexities and regrets when you have to do this (as our experience with MOOSE is showing).<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Thats a lot of jargon, but it does not answer the question. ML has no symbol dependence on PETSc, so just stick -lpetsc up<o:p></o:p></p></div><div><p class=MsoNormal>front. If the build system cannot handle that, its time for an overhaul.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal> Matt<o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>-Ross<o:p></o:p></p><div><div><p class=MsoNormal><br><br>_______________________________________________<br>Petsc-trilinos-discussion mailing list<br><a href="mailto:Petsc-trilinos-discussion@lists.mcs.anl.gov">Petsc-trilinos-discussion@lists.mcs.anl.gov</a><br><a href="https://lists.mcs.anl.gov/mailman/listinfo/petsc-trilinos-discussion" target="_blank">https://lists.mcs.anl.gov/mailman/listinfo/petsc-trilinos-discussion</a><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener <o:p></o:p></p></div></div></div></div></body></html>