Compile Error in Open (GNU) Cobol when compiling in OS 10.9 Mavericks ( New Install )

[gregthrower@…]

macbook-pro:tmp macbook$ cobc -x 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.

Hard error. Does not create executable. Should I forget running this on my MAC and just create a Linux partition?

[cooljeanius (Eric Gallager)]

This was brought up on the mailing list previously: ​https://lists.macosforge.org/pipermail/macports-users/2014-May/035518.html
Because the mailing list archives do not follow threads over month boundaries, the June portion of it starts here: ​https://lists.macosforge.org/pipermail/macports-users/2014-June/035556.html

I am working on fixing this as part of an update of the open-cobol package to version 2.0, but then I ran into this bug which I filed upstream: ​https://sourceforge.net/p/open-cobol/bugs/73/ (which apparently has received some comments since I last checked it... but that is something else)

Anyways, in the meantime, I fix the issue of clang being too strict by adding this block of code to the open-cobol Portfile:

# https://lists.macosforge.org/pipermail/macports-users/2014-May/035518.html
if {[string match *clang* ${configure.compiler}]} {
    configure.args-append --disable-rpath
    configure.cppflags-append -std=gnu89
    pre-configure {
        ui_warn "${name} has issues with clang"
    }
}

I am not sure if the --disable-rpath flag was around in the current version or if it was added in the version to which I am updating it though...

(also, since I am the maintainer of this port, you should have cc-ed me on it, but as I saw this in time, I will just cc myself. I would appreciate it if a committer could change that cc to an assignment...)

[cooljeanius (Eric Gallager)]

Cc Me!

[mf2k (Frank Schima)]

In the future, also use WikiFormatting and fill in the Port field.

[cooljeanius (Eric Gallager)]

I have an update ticket open that should fix this: #44501

[mf2k (Frank Schima)]

See #56907

[chrstphrchvz (Christopher Chavez)]

open-cobol has since been renamed to gnucobol and updated to 2.2. Is this issue still present?

[mf2k (Frank Schima)]

Please open a new ticket against the current port if this issue still exists.