<div dir="ltr"><div class="gmail_extra">On Wed, Jun 4, 2014 at 4:18 PM, "René J.V. Bertin" <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=""><br>
On Jun 04, 2014, at 20:21, Eric Gallager wrote:<br>
<br>
> Wow, that looks a lot simpler than I thought that it would be... I was expecting something like this would have to be fixed upstream by gcc, because that is how they handle the GNU vs. NeXT Objective C runtime issues, but if all it takes in this case is this script, it seems like just using this script would be easier... the main thing I worry about would be how the version numbers are hardcoded, but that seems like it should be easy enough to fix.<br>
<br>
</div>Does gcc still support spec files (cf. gcc -dumpspecs)? </blockquote><div><br></div><div>Yes.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">If so, one could probably patch in the information via that mechanism, and not add a series of library specifications regardless of whether you're linking or not ...<br>
<br>
In any case I'd invoke the system clang compiler.<br><font class="Apple-style-span" color="#888888"><br></font></blockquote><div>...this is just to get the version number, right? If we include this script in a port (such as the one ryandesign is working on in <a href="https://trac.macports.org/ticket/44413" rel="noreferrer">https://trac.macports.org/ticket/44413</a> for example), we could avoid having to actually invoke the compiler by just using the `configure.compiler` setting, and then `reinplace`-ing that into the script.</div>
</div><br></div></div>