Created attachment 593415 [details] Sample C++ code using BDADDR_ANY, BDADDR_LOCAL defines from bluetooth.h Description of problem: Unable to compile C++ code using BDADDR_ANY, BDADDR_LOCAL defines from bluetooth.h Version-Release number of selected component (if applicable): gcc-c++-4.7.0-5.fc17.i686 bluez-libs-devel-4.99-1.fc17.i686 How reproducible: Tried to use BDADDR_ANY, BDADDR_LOCAL defines from bluetooth.h in C++. Steps to Reproduce: 1. Compile sample C++ program Actual results: Compilation fails with error messages: /tmp/asd.cpp: In constructor 'sdp_compile_test::sdp_compile_test()' /tmp/asd.cpp:11:28: error: taking address of temporary [-fpermissive] /tmp/asd.cpp:11:40: error: taking address of temporary [-fpermissive] Expected results: C++ program compiles without errors. Additional info: Perhaps it would be better, it there were something like bluez-c++-devel with C++ classes for bluetooth functionality.
Created attachment 593418 [details] Sample C++ code using BDADDR_ANY, BDADDR_LOCAL defines from bluetooth.h
The call to sdp function is taken from SmartCam: http://smartcam.sourceforge.net That is V4L wrapper getting video stream from a remote server installed on a smartphone, via bluetooth, WiFi of USB. The desktop Linux part is divided into the V4L C driver, and control GTK UI with streaming proxy that is a C++ application. There were several successful builds, if not mistaken, up to Fedora 16. But when rebuilding in Fedora 17, because of GTK and C++ updates, this error occured.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.