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

2014-07-29 Thread Eric Gallager
After seeing https://trac.macports.org/ticket/44485 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: https://sourceforge.net/p/open-cobol/bugs/73/ Could

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

2014-07-29 Thread Ryan Schmidt
On Jul 29, 2014, at 11:38 AM, Eric Gallager eg...@gwmail.gwu.edu wrote: After seeing https://trac.macports.org/ticket/44485 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

Re: Package open-cobol not working for me

2014-06-04 Thread Ryan Schmidt
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

Re: Package open-cobol not working for me

2014-06-04 Thread Eric Gallager
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

Re: Package open-cobol not working for me

2014-06-04 Thread Michael Peternell
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

Re: Package open-cobol not working for me

2014-06-03 Thread Eric Gallager
Sorry for not replying sooner, I was away for a Memorial Day vacation last weekend, and once I got back, I was still trying to debug some kernel panics that my computer had been experiencing, which meant I couldn't really use it for email... anyway, on to the issue... open-cobol is actually a

Package open-cobol not working for me

2014-05-27 Thread Michael Peternell
Hi, I installed the open-cobol package but when I try to compile a program with it, it does not work: $ cobc hello.cob clang: error: unknown argument: '-R/opt/local/lib' [-Wunused-command-line-argument-hard-error-in-future] clang: note: this will be a hard error (cannot be downgraded to a

Re: Package open-cobol not working for me

2014-05-27 Thread Ryan Schmidt
On May 27, 2014, at 5:00 PM, Michael Peternell wrote: I installed the open-cobol package but when I try to compile a program with it, it does not work: $ cobc hello.cob clang: error: unknown argument: '-R/opt/local/lib' [-Wunused-command-line-argument-hard-error-in-future] clang: note: