<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Ok, I changed the topic to reflect the new attempt. MacPorts has been uninstalled as per <a href="https://guide.macports.org/chunked/installing.macports.uninstalling.html">instructions</a>, and reinstalled. I am now attempting to run <a href="https://trac.macports.org/wiki/LibcxxOnOlderSystems">https://trac.macports.org/wiki/LibcxxOnOlderSystems</a> in order to support software that may be written according to C++11 standard.</div><div><br></div><div>I ran <b>step 2</b> as corrected. No error reported.</div><div>I ran <b>step 3.1</b>. No error reported at either step (3.1.1 and 3.1.2).</div><div>Edited <i>/opt/local/etc/macports/macports.conf</i> as per <b>step 3.2</b>:</div><div>The beginning of the file now looks like:</div><div><span class="Apple-style-span" style="font-family: Courier; ">cxx_stdlib libc++</span></div><div><div><font class="Apple-style-span" face="Courier">buildfromsource always</font></div><div><font class="Apple-style-span" face="Courier">delete_la_files yes</font></div><div><font class="Apple-style-span" face="Courier">default_compilers macports-clang-3.4 macports-clang-3.3 gcc-4.2 apple-gcc-4.2 gcc-4.0</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier"># $Id: macports.conf.in 117120 2014-02-17 00:55:33Z <a href="mailto:jmr@macports.org">jmr@macports.org</a> $ […]</font></div></div><div><br></div><div>Then <b>step 3.3</b>. Received:</div><div><div><font class="Apple-style-span" face="Courier">Error: No ports matched the given expression</font></div></div><div>I assumed it was normal since this is a fresh installation, no port has been inactivated by step 3.1.1.</div><div><br></div><div>Then <b>step 3.4</b>: was long and noisy, but received no error.</div><div>Then <b>step 3.5</b>: no error</div><div>Then <b>step 3.6</b>: no error</div><div>Then <b>step 3.7</b>: It says to edit /opt/local/etc/macports/macports.conf again ; mine now looks like</div><div><div><font class="Apple-style-span" face="Courier">cxx_stdlib libc++</font></div><div><font class="Apple-style-span" face="Courier">buildfromsource always</font></div><div><font class="Apple-style-span" face="Courier">delete_la_files yes</font></div><div><font class="Apple-style-span" face="Courier">default_compilers macports-clang-3.7 macports-clang-3.4 macports-clang-3.3 gcc-4.2 apple-gcc-4.2 gcc-4.0</font></div><div><font class="Apple-style-span" face="Courier"><br></font></div><div><font class="Apple-style-span" face="Courier"># $Id: macports.conf.in 117120 2014-02-17 00:55:33Z <a href="mailto:jmr@macports.org">jmr@macports.org</a> $</font></div></div><div><br></div><div>As I understand it, this is the last step.</div><div><br></div><div>Then I tried to install Xsane, but it failed; I will open another thread so as to keep this one clean.</div><div><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br><div><div>El 2016-03-15, a las 01:49, Ryan Schmidt escribió:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br><blockquote type="cite">On Mar 15, 2016, at 12:46 AM, [ftp83plus] <<a href="mailto:gestos@ftp83plus.net">gestos@ftp83plus.net</a>> wrote:<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">Thanks all for your advices,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I see contradictions here: should I start afresh and bear hours of whining fans like Christopher suggests to make the topic easier to follow, or try to add precision to my former request like Ryan tries to tell?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">The main concern is of course the fan noise and the fact I have to rely on a much slower backup Mac should I need to leave home. I try to bear in mind that you guys aren't in fort of my screen, and its not easy to follow who said what and when.<br></blockquote><br>If you're stuck on the bootstrapping 2 step, starting over and following the newly edited instructions, without the -s flag on that step, should be very quick, since you'll be getting a precompiled archive from our server rather than having to compile it on your system.<br><br>For subsequent steps, there will still be compiling involved, since we don't yet have a naming convention for distinguishing libc++ packages from libstdc++ packages, so we don't provide libc++ packages for older OSes.<br><br><br><br><br></div></blockquote></div><br></body></html>