<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Welcome to our world!</div><div><br></div><div>How to fix this?...</div><div><br></div><div>you could try using sundials in octave (change the dependency in the Portfile). Maybe sundials2 was just an oversight. If that works, come up with a variant.</div><div><br></div><div>you could disable sundials in octave if you don't want or need it (again, maybe a variant).</div><div><br></div><div><br></div><div>... </div><div><br></div><br><div><div>On 2018-06-04, at 5:49 AM, Adam Dershowitz wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I’m in the same situation (I have openmodelica-devel installed and want to upgrade octave). The odd thing is that octave 4.2.2 was working fine with sundials (which is version 3.1.0_1). But, the upgrade of octave to 4.4 requires the sundials2 port (2.7.0). So, somehow it seems that upgrading octaves requires downgrading sundials. But, that is not compatible with openmodelica). <div class=""><br class=""><div class=""><div class="">
<div class=""><br class="khtml-block-placeholder"></div><div class="">--Adam</div><div class=""><br class="khtml-block-placeholder"></div><div class=""><br class="khtml-block-placeholder"></div>
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Jun 3, 2018, at 10:17 PM, Ken Cunningham <<a href="mailto:ken.cunningham.webuse@gmail.com" class="">ken.cunningham.webuse@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><div class="">The two sundials ports don't have exactly identical file names, but there is too much overlap to try a simple naming trick for installing them both it appears.</div><div class=""><br class=""></div><div class="">If one of the ports you want to install has a bundled copy of sundials that you can statically link in, you might get away with that as a quick one-off solution. Not a great general solution, but it is done.</div><div class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">More commonly, you would have to come up with a scheme to install them in non-conflicting locations where they can coexist without crashing into each other, and then direct the ports that need them to the location.</div><div class=""><br class=""></div><div class="">e.g.</div><div class=""><br class=""></div><div class="">/opt/local/libexec/sundials/*</div><div class="">/opt/local/libexec/sundials2*</div><div class=""><br class=""></div><div class="">or sometimes this pattern is chosen</div><div class=""><br class=""></div><div class="">/opt/local/include/sundials/*</div><div class="">/opt/local/include/sundials2/*</div><div class="">/opt/local/lib/sundials/*</div><div class="">/opt/local/lib/sundials2/*</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Sometimes, if one version is far more favoured than the other, the favoured version gets the default install location, and the less commonly used one gets an alternate location. This can be easier as most ports don't need to be modified, but also can generate hassles if the wrong library or header collection is found.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">And then, each and every port that uses sundials* needs to be checked and/or modified to make sure they find and use the correct versions of the headers and libraries.</div><div class=""><br class=""></div><div class="">A fair bit of work, to be sure...usually takes a dedicated dev who needs them both to work to dive in on this kind of project.</div><div class=""><br class=""></div><div class="">Updating ports to all use the latest version of the library is often a simpler and better solution, eg the recent ffmpeg project...</div><div class=""><br class=""></div><div class="">Ken</div><div class=""><br class=""></div><div class=""><br class=""><div class=""><div class="">On 2018-06-03, at 2:51 PM, Murray Eisenberg wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite" class=""><meta http-equiv="Content-Type" content="text/html; charset=us-ascii" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">The current octave (<span style="font-family: Menlo; font-size: 12px; background-color: rgb(255, 255, 255);" class="">@4.4.0_2+accelerate+app+docs+gfortran+graphicsmagick+qt5+sound)</span> epends on sundials2.<div class="">openmodelica-dvel depends on sundials. And sundials cannot be installed because it conflicts with sundials2.</div><div class=""><br class=""></div><div class="">Any way to resolve this?</div><div class=""><br class=""></div><div class=""><br class=""><div class="">
---<br class="">Murray Eisenberg<span class="Apple-tab-span" style="white-space: pre;"> </span><a href="mailto:murrayeisenberg@gmail.com" class="">murrayeisenberg@gmail.com</a><br class="">503 King Farm Blvd #101<span class="Apple-tab-span" style="white-space: pre;"> </span>Home (240)-246-7240<br class="">Rockville, MD 20850-6667<span class="Apple-tab-span" style="white-space: pre;"> </span>Mobile (413)-427-5334<br class=""><br class="">
</div>
<br class=""></div></div></blockquote></div><br class=""></div></div></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br></body></html>