Ticket #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: | egall@… |
| Port: | fontforge |
Description (last modified by ryandesign@…) (diff)
when installing font forge by:
sudo port install fontforge
I get
Error: Status 1 encountered during processing.
main.log file is attached.
Attachments
Change History
comment:1 Changed 2 years ago by ryandesign@…
- Keywords lion added
- Priority changed from High to Normal
- Description modified (diff)
- Summary changed from FontForge Installation to fontforge: 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 23 months ago by mojca.miklavec.lists@…
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 23 months ago by mojca.miklavec.lists@…
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 23 months ago by jeremyhu@…
Well since you said clang works for you in your comment above, you should try using clang instead of gcc-4.2 ...
Note: See
TracTickets for help on using
tickets.

