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 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). That being said, however, I suppose I can still try updating it to a newer version anyways, seeing as livecheck says to do so as well... right now I am still trying to get the new version to fetch properly... you could open a ticket and assign it to me so we could have a more central place to work out this update...
On Tue, May 27, 2014 at 6:37 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > 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: this will be a hard error (cannot be downgraded to a > warning) in the future > > > > (hello.cob is from here: > http://www.opencobol.org/modules/bwiki/index.php?cmd=read&page=UserManual%2F1 > ) > > > > I have written a detailed report of the issue here: > > https://sourceforge.net/p/open-cobol/discussion/help/thread/e1b4af35/ > > > > Is the open-cobol package working for anyone? If yes, what is different > in your system configuration? If no, where can I file a bug report so that > this package is fixed eventually? > > It looks like at configure time, open-cobol decides that the "-R" flag > should be used. This and the compiler choice then get baked into cobc. The > "-R" flag should not be used when the compiler does not support it. The > developers of open-cobol should fix this. Or they may already have fixed it > in version 2, to which we should update the port. Actually it looks like > the project's name may have changed (or may be in the process of changing) > to gnu-cobol; the 2.0 update may be an opportunity for us to rename the > port. I'm Cc'ing Eric who maintains this port.
_______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users