<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2018-09-02, at 1:10 PM, Riccardo Mottola wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div text="#000000" bgcolor="#FFFFFF"><p>Hi Ken,<br>
</p>
<br>
I did not "force" this configuration at all - I am just upgrading,
so port selected this heade/compiler combination by itself!<br>
<br>
Riccardo<br>
</div>
</blockquote><br></div><div>You're right. I was mistakenly thinking you had done that.</div><div><br></div><div>I think at some point you followed at least some of the "LibcxxOnOlderSystems" instructions, and then along the way undid some of it (like unsetting the default compiler, perhaps). So you have an inconsistency there.</div><div><br></div><div><br></div><div>For what it's worth, to run 10.6.8 successfully, I think following the LibcxxOnOlderSystems instructions is the way to go. My 10.6.8 system is absolutely trouble free. I NEVER need to worry about the cxx11 1.1 PG, and many software build issues just never come to me because this system is very similar to the current macOS releases.</div><div><br></div><div><br></div><div>I stick with 10.6.8 for some uses because a lot of things are set up on this system that just cannot be done on a current macOS system -- for example, I have a "file printer" that reads in a print job piped from stdin, finds fax numbers in the job, and automatically generates faxes for hylafax that sends them out on a networked fax printer. I tried to set this up on 10.12 and 10.13, and it just won't allow it. </div><div><br></div><div>And other similar idiosyncracies that just work for me.</div><br><div>Best,</div><div><br></div><div>Ken</div></body></html>