[MacPorts] #40152: liblo @0.27: build fails: error: expected value in expression
#40152: liblo @0.27: build fails: error: expected value in expression --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Keywords: | Port: liblo --------------------------+-------------------------------- -- Ticket URL: <https://trac.macports.org/ticket/40152> MacPorts <http://www.macports.org/> Ports system for OS X
#40152: liblo @0.27: build fails: error: expected value in expression ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: liblo | ---------------------------+-------------------------------- Comment (by ryandesign@…): That was with +universal. Without it, failure is earlier, in the configure phase: {{{ checking how to print long long int... configure: error: printf doesn't support long long int }}} The config.log shows an unnecessary flag being used, about which clang prints a warning, and the `-Werror` flag being used, which turns the warning into a fatal error: {{{ configure:11936: ccache /usr/bin/clang -c -pipe -Os -arch x86_64 -Werror -Wall -I/opt/local/include conftest.c >&5 clang: error: argument unused during compilation: '-I /opt/local/include' }}} -- Ticket URL: <https://trac.macports.org/ticket/40152#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#40152: liblo @0.27: build fails: error: expected value in expression ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: liblo | ---------------------------+-------------------------------- Comment (by ryandesign@…): Should liblo even have been updated to 0.27? According to the homepage 0.27 is a testing release; 0.26 is still the latest stable. -- Ticket URL: <https://trac.macports.org/ticket/40152#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#40152: liblo @0.27: build fails: error: expected value in expression ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: liblo | ---------------------------+-------------------------------- Comment (by ryandesign@…): Maybe their homepage is out of date. [http://sourceforge.net/mailarchive/forum.php?thread_name=CADopUHas3DDEh %3D69o4LEEiVXYRUbbwoZKNQtL-4PQs0BuH4dQQ%40mail.gmail.com&forum_name=liblo- devel liblo 0.27 was announced as stable] on the mailing list on 2013-05-22. -- Ticket URL: <https://trac.macports.org/ticket/40152#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#40152: liblo @0.27: build fails: error: expected value in expression ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: | Keywords: Port: liblo | ---------------------------+-------------------------------- Comment (by ryandesign@…): Replying to [comment:1 ryandesign@…]:
{{{ checking how to print long long int... configure: error: printf doesn't support long long int }}}
Worked around this in r109546. Filed upstream bug report: https://sourceforge.net/p/liblo/bugs/34/
Should liblo even have been updated to 0.27? According to the homepage 0.27 is a testing release; 0.26 is still the latest stable.
Maybe their homepage is out of date. [http://sourceforge.net/mailarchive/forum.php?thread_name=CADopUHas3DDEh %3D69o4LEEiVXYRUbbwoZKNQtL-4PQs0BuH4dQQ%40mail.gmail.com&forum_name=liblo- devel liblo 0.27 was announced as stable] on the mailing list on 2013-05-22.
Filed an upstream bug report about this: https://sourceforge.net/p/liblo/bugs/33/
error: expected value in expression
Filed an upstream bug report about this: https://sourceforge.net/p/liblo/bugs/35/ -- Ticket URL: <https://trac.macports.org/ticket/40152#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#40152: liblo @0.27: build fails: error: expected value in expression ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.0 Resolution: fixed | Keywords: Port: liblo | ---------------------------+-------------------------------- Changes (by ryandesign@…): * status: new => closed * resolution: => fixed Comment: Replying to [comment:4 ryandesign@…]:
Should liblo even have been updated to 0.27? According to the homepage 0.27 is a testing release; 0.26 is still the latest stable.
Maybe their homepage is out of date. [http://sourceforge.net/mailarchive/forum.php?thread_name=CADopUHas3DDEh %3D69o4LEEiVXYRUbbwoZKNQtL-4PQs0BuH4dQQ%40mail.gmail.com&forum_name=liblo- devel liblo 0.27 was announced as stable] on the mailing list on 2013-05-22.
Filed an upstream bug report about this: https://sourceforge.net/p/liblo/bugs/33/
The developer replied:
After release, several bugs were reported that had not been reported previous to release. At least one of these was serious enough that I can't recommend 0.27 as stable. Several bugs only appeared on the x86_64 architecture. Many of these have now been fixed in master but are awaiting further testing.
Reverted to 0.26 in r109548. -- Ticket URL: <https://trac.macports.org/ticket/40152#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts