[MacPorts] #36572: cuneiform: character too large for enclosing character literal type
MacPorts
noreply at macports.org
Mon Oct 15 04:29:11 PDT 2012
#36572: cuneiform: character too large for enclosing character literal type
-----------------------------------+--------------------------------
Reporter: benjamin_steinberg@… | Owner: macports-tickets@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.1.2
Resolution: fixed | Keywords:
Port: cuneiform |
-----------------------------------+--------------------------------
Changes (by ryandesign@…):
* status: new => closed
* cc: ryandesign@… (added)
* resolution: => fixed
Comment:
Replying to [ticket:36572 benjamin_steinberg@…]:
> The errors are "character too large for enclosing character literal
type" -- I wonder if the strings in question need to be prefixed with an
L, something like this:
>
> https://github.com/TheLevelUp/ZXingObjC/issues/3
>
> though that might be an issue for upstream.
Indeed please report the problem to the developers so that they can fix
it. I'm not a C programmer and don't understand the significance of
prefixing a string with "L" so I don't feel comfortable making that change
on my own.
> However, I see other people have obviously built this version of
cuneiform: #33708
Yes but that's on Lion, which is a different OS. They're probably also
using a different version of Xcode, which means a different version of
clang, or if Xcode < 4.2, then they wouldn't even have been using clang;
they'd've been using llvm-gcc-4.2.
On the hunch that this, like so [wiki:ProblemHotlist#compiler many other
problems] we've seen, is because clang is a bit different, I tried
blacklisting it and using llvm-gcc-4.2 instead. That worked, so I
committed that workaround in r98766.
--
Ticket URL: <https://trac.macports.org/ticket/36572#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list