Opened 11 years ago

Closed 11 years ago

#41521 closed defect (fixed)

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

Reported by: em36@… Owned by: ryandesign (Ryan Carsten Schmidt)
Priority: Normal Milestone:
Component: ports Version: 2.2.1
Keywords: mavericks Cc: askbal@…, m.takahashi.public@…, foinux@…, pavel.hlavnicka@…
Port: libgsf

Description

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

Attachments (4)

main.log (65.5 KB) - added by em36@… 11 years ago.
log file
main.2.log (89.1 KB) - added by askbal@… 11 years ago.
main.log for libgsf build error
main3.log (90.3 KB) - added by em36@… 11 years ago.
logfile - failure to build libgsf (after cleaning libgsf)
main-foxiness.log (91.0 KB) - added by foinux@… 11 years ago.
Error: org.macports.build for port libgsf returned: command execution failed

Download all attachments as: .zip

Change History (18)

Changed 11 years ago by em36@…

Attachment: main.log added

log file

comment:1 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Keywords: mavericks added
Port: libgsf added

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

Changed 11 years ago by askbal@…

Attachment: main.2.log added

main.log for libgsf build error

comment:2 Changed 11 years ago by askbal@…

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

comment:3 Changed 11 years ago by askbal@…

Cc: askbal@… added

Cc Me!

comment:4 Changed 11 years ago by 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

comment:5 Changed 11 years ago by 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.

comment:6 Changed 11 years ago by m.takahashi.public@…

Cc: m.takahashi.public@… added

Cc Me!

Changed 11 years ago by em36@…

Attachment: main3.log added

logfile - failure to build libgsf (after cleaning libgsf)

comment:7 in reply to:  1 Changed 11 years ago by 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.

Changed 11 years ago by foinux@…

Attachment: main-foxiness.log added

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

comment:8 Changed 11 years ago by 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.
Last edited 11 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:9 Changed 11 years ago by foinux@…

Cc: foinux@… added

Cc Me!

comment:10 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Owner: changed from macports-tickets@… to ryandesign@…
Status: newassigned
Summary: libgsf won't install under Maverickslibgsf @1.14.28: error: format string is not a string literal

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.

comment:11 in reply to:  4 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Cc: pavel.hlavnicka@… added

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.

comment:12 in reply to:  10 Changed 11 years ago by 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.

comment:13 in reply to:  11 Changed 11 years ago by 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.

comment:14 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: assignedclosed

Great!

Note: See TracTickets for help on using tickets.