Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#40152 closed defect (fixed)

liblo @0.27: build fails: error: expected value in expression

Reported by: ryandesign (Ryan Carsten Schmidt) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.2.0
Keywords: Cc: nomis52@…, larryv (Lawrence Velázquez)
Port: liblo

Description


Attachments (1)

main.log (17.8 KB) - added by ryandesign (Ryan Carsten Schmidt) 11 years ago.

Download all attachments as: .zip

Change History (7)

Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Attachment: main.log added

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

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'

comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

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.

comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Maybe their homepage is out of date. liblo 0.27 was announced as stable on the mailing list on 2013-05-22.

comment:4 in reply to:  3 ; Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Replying to 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. 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/

comment:5 in reply to:  4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)

Resolution: fixed
Status: newclosed

Replying to 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. 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.

comment:6 Changed 10 years ago by bennigraf@…

The Ticket #46538 tries to fix this by jumping to v0.28 which was released last year...

Last edited 10 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)
Note: See TracTickets for help on using tickets.