#36572: cuneiform 1.1.0 build failure -----------------------------------+-------------------------------- Reporter: benjamin_steinberg@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Resolution: | Keywords: Port: cuneiform | -----------------------------------+-------------------------------- Old description:
I'm running Mac OS X 10.8.2 and XCode 4.5.1 (4G1004) -- cuneiform build fails. I'll attach /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_cuneiform/cuneiform/main.log
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. However, I see other people have obviously built this version of cuneiform: http://trac.macports.org/ticket/33708
New description: I'm running Mac OS X 10.8.2 and XCode 4.5.1 (4G1004) -- cuneiform build fails. I'll attach /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_cuneiform/cuneiform/main.log 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. However, I see other people have obviously built this version of cuneiform: #33708 -- Comment (by ryandesign@…): This was not a clean build attempt. Please "sudo port clean cuneiform", then try again, then attach the new main.log file. -- Ticket URL: <https://trac.macports.org/ticket/36572#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS