open-cobol update and destroot sandbox violations (was Re: Package open-cobol not working for me)

Eric Gallager egall at
Tue Jul 29 09:38:25 PDT 2014

After seeing 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:

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?

On Wed, Jun 4, 2014 at 3:26 PM, Michael Peternell <michael.peternell at>

> Maybe important: clang is used on OSX, because it has no gcc installed
> anymore. But clang is the new gcc.
> To clarify:
> --- on the command line ---
> $ gcc
> clang: error: no input files
> --- end of command line ---
> (my system: OSX 10.8.5)
> Regards,
> Michael
> Am 04.06.2014 um 18:38 schrieb Eric Gallager <egall at>:
> > 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...
> >
> >
> >
> > On Wed, Jun 4, 2014 at 2:44 AM, Ryan Schmidt <ryandesign at>
> wrote:
> >
> > On Jun 3, 2014, at 8:24 PM, Eric Gallager wrote:
> >
> >> 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).
> >
> > 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.
> >
> >
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-dev mailing list