Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#29840 closed defect (fixed)

fontforge: cvexportdlg.c:251: error: initializer element is not constant

Reported by: terrydemco@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: lion Cc: cooljeanius (Eric Gallager)
Port: fontforge

Description (last modified by ryandesign (Ryan Schmidt))

when installing font forge by:

sudo port install fontforge

I get

Error: Status 1 encountered during processing.

main.log file is attached.

Attachments (1)

main.log (66.4 KB) - added by terrydemco@… 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by terrydemco@…

Attachment: main.log added

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

Description: modified (diff)
Keywords: lion added
Priority: HighNormal
Summary: FontForge Installationfontforge: cvexportdlg.c:251: error: initializer element is not constant

Let's not overlook that you're running a pre-release version of Mac OS X Lion.

comment:2 Changed 10 years ago by mojca (Mojca Miklavec)

See http://llvm.org/bugs/show_bug.cgi?id=2951

It seems to be a bug in llvm-gcc that the team refuses to fix. If I use clang for compiling the same command that is failing works fine, but I didn't yet figure out how to do reconfigure macports to use clang.

comment:3 Changed 10 years ago by mojca (Mojca Miklavec)

Using the same patch as wine package does

if {${configure.compiler} == "llvm-gcc-4.2" ||
    ${configure.compiler} == "clang"} {
    configure.compiler gcc-4.2
}

solves the problem for me.

comment:4 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Well since you said clang works for you in your comment above, you should try using clang instead of gcc-4.2 ...

comment:5 Changed 10 years ago by jeremyhu (Jeremy Huddleston Sequoia)

Resolution: fixed
Status: newclosed

Built it fine with clang, r80372

comment:6 Changed 8 years ago by cooljeanius (Eric Gallager)

Cc: egall@… added

Cc Me!

Note: See TracTickets for help on using tickets.