<div dir="ltr">After seeing <a href="https://trac.macports.org/ticket/44485" rel="noreferrer">https://trac.macports.org/ticket/44485</a> filed against open-cobol about this same issue, I decided to check up on the upstream bug I had filed that was blocking my update to version 2.0, and found that it had some new responses: <a href="https://sourceforge.net/p/open-cobol/bugs/73/" rel="noreferrer">https://sourceforge.net/p/open-cobol/bugs/73/</a><div>
<br></div><div>Could someone who is more well-versed in the history of MacPorts help me to better explain to upstream why we install to a destroot and prevent writes outside of it?</div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, Jun 4, 2014 at 3:26 PM, Michael Peternell <span dir="ltr"><<a href="mailto:michael.peternell@gmx.at" target="_blank">michael.peternell@gmx.at</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Maybe important: clang is used on OSX, because it has no gcc installed anymore. But clang is the new gcc.<br>
<br>
To clarify:<br>
<br>
--- on the command line ---<br>
$ gcc<br>
clang: error: no input files<br>
--- end of command line ---<br>
<br>
(my system: OSX 10.8.5)<br>
<br>
Regards,<br>
Michael<br>
<br>
Am 04.06.2014 um 18:38 schrieb Eric Gallager <<a href="mailto:egall@gwmail.gwu.edu" rel="noreferrer">egall@gwmail.gwu.edu</a>>:<br>
<div class="HOEnZb"><div class="h5"><br>
> Maybe I'll install clang 3.4 and 3.5 once I have some spare cycles; my computer just finished rebuilding llvm 3.3 and gcc 4.7 and 4.8 due to the recent updates, and those all took a long time on their own... Anyways, doing the latter of the things you suggested, I seem to have managed to remove the flag from cobc-config, so I will attach a patch once I am done...<br>
><br>
><br>
><br>
> On Wed, Jun 4, 2014 at 2:44 AM, Ryan Schmidt <<a href="mailto:ryandesign@macports.org" rel="noreferrer">ryandesign@macports.org</a>> wrote:<br>
><br>
> On Jun 3, 2014, at 8:24 PM, Eric Gallager wrote:<br>
><br>
>> open-cobol is actually a source-to-source compiler (or "transpiler") that compiles to C code, and then uses the host C compiler to compile the generated C code, which means that something that looks like an open-cobol error might actually be an error with your host compiler. By the error message, it looks like OP is using the clang that comes with Mavericks/Xcode 5, which has gotten overly strict about what it accepts recently, and which I do not use anyways (because I am still on Snow Leopard), so I will not be able to reproduce your error (my /opt/local/bin/cobc successfully compiles the example source file into a runnable executable on my machine).<br>
><br>
> You might be able to reproduce the problem on Snow Leopard if you rebuild open-cobol with configure.compiler=macports-clang-3.5 (or -3.4). Even without doing so, you can confirm that the file /opt/local/bin/cob-config installed by open-cobol contain the -R argument, which as I understand it is never used on OS X.<br>
><br>
><br>
><br>
<br>
</div></div></blockquote></div><br></div></div>