2
4
Fork
You've already forked libssc
8

Warnings when building libssc on recent Debian #71

Open
opened 2025年05月12日 15:37:49 +02:00 by lumag · 10 comments

Building libssc on a recent Debian/testing produces the following warnings:

ninja: Entering directory `build/'
[1/68] Generating data/ssc-sensor-suid_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[5/68] Generating data/ssc-sensor-light_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[6/68] Generating data/ssc-sensor-proximity_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[8/68] Generating data/ssc-sensor-accelerometer_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[11/68] Generating data/ssc-sensor-rotationvector_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[12/68] Generating data/ssc-common_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[14/68] Generating data/ssc-sensor-magnetometer_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[16/68] Generating data/ssc-sensor-gyroscope_c with a custom command
[libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead!
[66/68] Generating src/SSC-1.gir with a custom command (wrapped by meson to set env)
../src/libssc-sensor-proximity.h:69: Warning: SSC: symbol='ProximityDataDavinci': Unknown namespace for identifier 'ProximityDataDavinci'
[68/68] Generating src/libssc.vapi with a custom command
Qmi-1.0.gir:10064.7-10067.72: warning: Signal `QMI.ClientLoc.delete_assistance_data' conflicts with method of the same name
Qmi-1.0.gir:10162.7-10165.58: warning: Signal `QMI.ClientLoc.get_engine_lock' conflicts with method of the same name
Qmi-1.0.gir:10262.7-10265.56: warning: Signal `QMI.ClientLoc.get_nmea_types' conflicts with method of the same name
Qmi-1.0.gir:10362.7-10365.64: warning: Signal `QMI.ClientLoc.get_operation_mode' conflicts with method of the same name
Qmi-1.0.gir:10462.7-10465.92: warning: Signal `QMI.ClientLoc.get_predicted_orbits_data_source' conflicts with method of the same name
Qmi-1.0.gir:10562.7-10565.48: warning: Signal `QMI.ClientLoc.get_server' conflicts with method of the same name
Qmi-1.0.gir:10660.7-10663.84: warning: Signal `QMI.ClientLoc.inject_predicted_orbits_data' conflicts with method of the same name
Qmi-1.0.gir:10758.7-10761.60: warning: Signal `QMI.ClientLoc.inject_xtra_data' conflicts with method of the same name
Qmi-1.0.gir:10954.7-10957.58: warning: Signal `QMI.ClientLoc.set_engine_lock' conflicts with method of the same name
Qmi-1.0.gir:11052.7-11055.56: warning: Signal `QMI.ClientLoc.set_nmea_types' conflicts with method of the same name
Qmi-1.0.gir:11150.7-11153.64: warning: Signal `QMI.ClientLoc.set_operation_mode' conflicts with method of the same name
Qmi-1.0.gir:11248.7-11251.48: warning: Signal `QMI.ClientLoc.set_server' conflicts with method of the same name
Qmi-1.0.gir:16233.7-16236.58: warning: Signal `QMI.ClientPdc.activate_config' conflicts with method of the same name
Qmi-1.0.gir:16429.7-16432.62: warning: Signal `QMI.ClientPdc.deactivate_config' conflicts with method of the same name
Qmi-1.0.gir:16625.7-16628.58: warning: Signal `QMI.ClientPdc.get_config_info' conflicts with method of the same name
Qmi-1.0.gir:16919.7-16922.66: warning: Signal `QMI.ClientPdc.get_selected_config' conflicts with method of the same name
Qmi-1.0.gir:17017.7-17020.52: warning: Signal `QMI.ClientPdc.list_configs' conflicts with method of the same name
Qmi-1.0.gir:17115.7-17118.50: warning: Signal `QMI.ClientPdc.load_config' conflicts with method of the same name
Qmi-1.0.gir:17411.7-17414.66: warning: Signal `QMI.ClientPdc.set_selected_config' conflicts with method of the same name
Qmi-1.0.gir:23377.7-23380.72: warning: Signal `QMI.ClientVoice.originate_ussd_no_wait' conflicts with method of the same name
Qmi-1.0.gir:24069.7-24072.72: warning: Signal `QMI.ClientWda.loopback_configuration' conflicts with method of the same name
Qmi-1.0.gir:27375.7-27378.74: warning: Signal `QMI.ClientWds.set_lte_attach_pdn_list' conflicts with method of the same name
Qmi-1.0.gir:29420.7-29422.22: warning: Instance methods are not supported in error domains yet
Qmi-1.0.gir:177379.7-177381.22: warning: Instance methods are not supported in error domains yet
Building libssc on a recent Debian/testing produces the following warnings: ``` ninja: Entering directory `build/' [1/68] Generating data/ssc-sensor-suid_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [5/68] Generating data/ssc-sensor-light_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [6/68] Generating data/ssc-sensor-proximity_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [8/68] Generating data/ssc-sensor-accelerometer_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [11/68] Generating data/ssc-sensor-rotationvector_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [12/68] Generating data/ssc-common_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [14/68] Generating data/ssc-sensor-magnetometer_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [16/68] Generating data/ssc-sensor-gyroscope_c with a custom command [libprotobuf WARNING protoc-gen-c/main.cc:44] `protoc-c` is deprecated. Please use `protoc` instead! [66/68] Generating src/SSC-1.gir with a custom command (wrapped by meson to set env) ../src/libssc-sensor-proximity.h:69: Warning: SSC: symbol='ProximityDataDavinci': Unknown namespace for identifier 'ProximityDataDavinci' [68/68] Generating src/libssc.vapi with a custom command Qmi-1.0.gir:10064.7-10067.72: warning: Signal `QMI.ClientLoc.delete_assistance_data' conflicts with method of the same name Qmi-1.0.gir:10162.7-10165.58: warning: Signal `QMI.ClientLoc.get_engine_lock' conflicts with method of the same name Qmi-1.0.gir:10262.7-10265.56: warning: Signal `QMI.ClientLoc.get_nmea_types' conflicts with method of the same name Qmi-1.0.gir:10362.7-10365.64: warning: Signal `QMI.ClientLoc.get_operation_mode' conflicts with method of the same name Qmi-1.0.gir:10462.7-10465.92: warning: Signal `QMI.ClientLoc.get_predicted_orbits_data_source' conflicts with method of the same name Qmi-1.0.gir:10562.7-10565.48: warning: Signal `QMI.ClientLoc.get_server' conflicts with method of the same name Qmi-1.0.gir:10660.7-10663.84: warning: Signal `QMI.ClientLoc.inject_predicted_orbits_data' conflicts with method of the same name Qmi-1.0.gir:10758.7-10761.60: warning: Signal `QMI.ClientLoc.inject_xtra_data' conflicts with method of the same name Qmi-1.0.gir:10954.7-10957.58: warning: Signal `QMI.ClientLoc.set_engine_lock' conflicts with method of the same name Qmi-1.0.gir:11052.7-11055.56: warning: Signal `QMI.ClientLoc.set_nmea_types' conflicts with method of the same name Qmi-1.0.gir:11150.7-11153.64: warning: Signal `QMI.ClientLoc.set_operation_mode' conflicts with method of the same name Qmi-1.0.gir:11248.7-11251.48: warning: Signal `QMI.ClientLoc.set_server' conflicts with method of the same name Qmi-1.0.gir:16233.7-16236.58: warning: Signal `QMI.ClientPdc.activate_config' conflicts with method of the same name Qmi-1.0.gir:16429.7-16432.62: warning: Signal `QMI.ClientPdc.deactivate_config' conflicts with method of the same name Qmi-1.0.gir:16625.7-16628.58: warning: Signal `QMI.ClientPdc.get_config_info' conflicts with method of the same name Qmi-1.0.gir:16919.7-16922.66: warning: Signal `QMI.ClientPdc.get_selected_config' conflicts with method of the same name Qmi-1.0.gir:17017.7-17020.52: warning: Signal `QMI.ClientPdc.list_configs' conflicts with method of the same name Qmi-1.0.gir:17115.7-17118.50: warning: Signal `QMI.ClientPdc.load_config' conflicts with method of the same name Qmi-1.0.gir:17411.7-17414.66: warning: Signal `QMI.ClientPdc.set_selected_config' conflicts with method of the same name Qmi-1.0.gir:23377.7-23380.72: warning: Signal `QMI.ClientVoice.originate_ussd_no_wait' conflicts with method of the same name Qmi-1.0.gir:24069.7-24072.72: warning: Signal `QMI.ClientWda.loopback_configuration' conflicts with method of the same name Qmi-1.0.gir:27375.7-27378.74: warning: Signal `QMI.ClientWds.set_lte_attach_pdn_list' conflicts with method of the same name Qmi-1.0.gir:29420.7-29422.22: warning: Instance methods are not supported in error domains yet Qmi-1.0.gir:177379.7-177381.22: warning: Instance methods are not supported in error domains yet ```

I don't have a Debian install currently so I will have to see how to reproduce this. Although, if you find a fix, feel free to send a PR :)

I don't have a Debian install currently so I will have to see how to reproduce this. Although, if you find a fix, feel free to send a PR :)
Author
Copy link

Docker image?

Docker image?

Should be fixed with #73

Should be fixed with https://codeberg.org/DylanVanAssche/libssc/pulls/73
Author
Copy link

@DylanVanAssche wrote in #71 (comment):

Should be fixed with #73

It fixes only the tool name warning. There are other warnings about the signal names, etc.

@DylanVanAssche wrote in https://codeberg.org/DylanVanAssche/libssc/issues/71#issuecomment-4861800: > Should be fixed with #73 It fixes only the tool name warning. There are other warnings about the signal names, etc.

Those are from libqmi I'm afraid. Seems a bug in there.

Those are from `libqmi` I'm afraid. Seems a bug in there.

Could also be from VAPI generation, but I'm no expert in that I'm afraid, maybe @NekoCWD knows?

Could also be from VAPI generation, but I'm no expert in that I'm afraid, maybe @NekoCWD knows?
Contributor
Copy link

Yep. This is warnings from libqmi vapigen. You can ignore it

Yep. This is warnings from libqmi vapigen. You can ignore it

@NekoCWD Is this something to report with libqmi upstream?

@NekoCWD Is this something to report with libqmi upstream?

The VAPIGEN warnings are still there, reopened.

The VAPIGEN warnings are still there, reopened.
Created an issue upstream: https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/issues/128
Sign in to join this conversation.
No Branch/Tag specified
main
pages
v0.4.4
v0.4.3
v0.4.2
v0.4.1
v0.4.0
v0.3.0
v0.2.2
v0.2.1
v0.2.0
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
v0.0.1
No labels
Bug
Feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
DylanVanAssche/libssc#71
Reference in a new issue
DylanVanAssche/libssc
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?