libgsf @1.14.28: error: format string is not a string literal

[em36@…]

I've attached the log file; I don't have any further details.

[em36@…]

log file

[ryandesign (Ryan Carsten Schmidt)]

This was not a clean attempt. Please ​clean and try again. It builds fine for me on Mavericks.

[askbal@…]

main.log for libgsf build error

[askbal@…]

I have the same issue with libgsf. Attached main.log file as main.2.log

[askbal@…]

Cc Me!

[askbal@…]

Seems to build fine with configure.compiler = macports-gcc-4.8. I am am noob with port files and stuff, so I am not sure what this means. Is this a clang issue? I have the following clang:-

clang --version
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix

[pavel.hlavnicka@…]

Tis is for sure not the proper way to fix it, but disabling format-security warnings helps. Changing Portfile to

configure.args          --enable-introspection \
                        --enable-compile-warnings=no

and removing -Werror=format-security from configure.ac helps. Code calls triggering this error should be fixed indeed.

[m.takahashi.public@…]

Cc Me!

[em36@…]

logfile - failure to build libgsf (after cleaning libgsf)

[em36@…]

Replying to ryandesign@…:

This was not a clean attempt. Please ​clean and try again. It builds fine for me on Mavericks.

I cleaned and tried again, with no success. I've added Main3.log to the attachments list.

[foinux@…]

Error: org.macports.build for port libgsf returned: command execution failed

[foinux@…]

I have the same issue

What i did trying to fix it

• following the migration docs wiki:Migration
• uninstalled with clean
• then build macport from source
• i have xcode-tools installed agreed to licences.

[foinux@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

I don't understand why this works for me and not for you, but I've made a change that may help: r113841. Please wait 30 minutes, then run "sudo port selfupdate" and try again.

[ryandesign (Ryan Carsten Schmidt)]

Replying to askbal@…:

Seems to build fine with configure.compiler = macports-gcc-4.8.

Building with FSF GCC on Mavericks can have unintended consequences, due to a difference in C++ runtimes, so you should not do this. If you've already done this, please re-try with clang.

[em36@…]

Replying to ryandesign@…:

I don't understand why this works for me and not for you, but I've made a change that may help: r113841. Please wait 30 minutes, then run "sudo port selfupdate" and try again.

Your fix seems to work perfectly. Thank you.

[askbal@…]

Replying to ryandesign@…:

Building with FSF GCC on Mavericks can have unintended consequences, due to a difference in C++ runtimes, so you should not do this. If you've already done this, please re-try with clang.

Thanks! This works for me.

[ryandesign (Ryan Carsten Schmidt)]

Great!