Attention is currently required from: neels.
Hello Jenkins Builder, pespin, fixeria,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/c/libosmo-pfcp/+/31761
to look at the new patch set (#2).
Change subject: build: drop COVERAGE
......................................................................
build: drop COVERAGE
There isn't even an --enable-coverage in the configure.ac, so drop the
always empty COVERAGE_CFLAGS and COVERAGE_LDFLAGS.
Change-Id: Ib256ce7d979aec5c368b19ac2c145f75a9dab0fc
---
M src/libosmo-gtlv/Makefile.am
M src/libosmo-pfcp/Makefile.am
2 files changed, 12 insertions(+), 5 deletions(-)
git pull ssh://gerrit.osmocom.org:29418/libosmo-pfcp refs/changes/61/31761/2
--
To view, visit https://gerrit.osmocom.org/c/libosmo-pfcp/+/31761
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-pfcp
Gerrit-Branch: master
Gerrit-Change-Id: Ib256ce7d979aec5c368b19ac2c145f75a9dab0fc
Gerrit-Change-Number: 31761
Gerrit-PatchSet: 2
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-MessageType: newpatchset
Attention is currently required from: neels.
laforge has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-pfcp/+/31760 )
Change subject: libosmo-pfcp.pc: move libosmogsm to Requires
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> No: […]
I would like to know how and why something fails before blindly doing workarounds. Like what does pkg-config --libs etc. return for libosmogsm; how does the constructed linker command look like when the test is built, etc.
--
To view, visit https://gerrit.osmocom.org/c/libosmo-pfcp/+/31760
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-pfcp
Gerrit-Branch: master
Gerrit-Change-Id: I319173c1fab068dfe1361ae6cd02f729461d4cf8
Gerrit-Change-Number: 31760
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 14 Mar 2023 18:47:54 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: neels <nhofmeyr(a)sysmocom.de>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: laforge.
neels has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmo-pfcp/+/31760 )
Change subject: libosmo-pfcp.pc: move libosmogsm to Requires
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> oh, i see. so your unique_ids_test is a binary you build locally in this respository here. […]
No:
We are in libosmo-pfcp.git here,
unique_ids_test lives in osmo-upf.git.
This here *installs* libosmo-pfcp.so, with pkgconfig info.
Then osmo-upf.git builds unique_ids_test, uses the installed libosmo-pfcp.so, which via installed pkgconfig is supposed to pull in libosmogsm.so.
It works for libosmo-gtlv.so but not for libosmogsm.so.
So I am trying to find out why. This here is one attempt that somehow fixed things for me locally, but it might only have been confusing side effects from rebuilding.
If we get Requires.private to work then ok, if not then I really don't care enough to grind my soul over this, just to have a lib in Requires.private instead of in Requires. I'm sure we hardly ever cared about this before.
Maybe we can first put it in Requires, then if the build works go back to Requires.private and see if that still works, just to not stall the osmo-upf patches any longer?
--
To view, visit https://gerrit.osmocom.org/c/libosmo-pfcp/+/31760
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmo-pfcp
Gerrit-Branch: master
Gerrit-Change-Id: I319173c1fab068dfe1361ae6cd02f729461d4cf8
Gerrit-Change-Number: 31760
Gerrit-PatchSet: 1
Gerrit-Owner: neels <nhofmeyr(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Tue, 14 Mar 2023 18:21:12 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
Attention is currently required from: laforge.
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/31914 )
Change subject: {context,select}: cosmetic: use OTC_SELECT instead of osmo_ctx->select
......................................................................
Patch Set 2:
(1 comment)
Patchset:
PS2:
> I don't really see the improvement here. […]
I was seeking for consistency, because in some places within libosmocore.git we use `OTC_{SELECT,GLOBAL}`, in some we use `osmo_ctx->{select,global}`. I am fine with using `osmo_ctx->{select,global}` in libosmocore and can submit a patch replacing macros.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/31914
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: I2aa03c7c68b7cca17eebbf858ada7c42f0d0a1da
Gerrit-Change-Number: 31914
Gerrit-PatchSet: 2
Gerrit-Owner: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-CC: pespin <pespin(a)sysmocom.de>
Gerrit-Attention: laforge <laforge(a)osmocom.org>
Gerrit-Comment-Date: Tue, 14 Mar 2023 15:37:58 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Gerrit-MessageType: comment
fixeria has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/31911 )
Change subject: on_dso_load_select: run after on_dso_load_ctx
......................................................................
Patch Set 4:
(1 comment)
Commit Message:
https://gerrit.osmocom.org/c/libosmocore/+/31911/comment/3c87dfe9_a177a211
PS3, Line 10: Otherwise osmo_ctx->global (used via define OTC_GLOBAL) points to NULL
It would be more correct to say: "Otherwise `osmo_ctx` is NULL, so by using `OTC_GLOBAL` defined as `osmo_ctx->global` we're dereferencing NULL". But LGTM, not critical at all.
--
To view, visit https://gerrit.osmocom.org/c/libosmocore/+/31911
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Ia2518e82530b93c535f8f5105513e21559b895ba
Gerrit-Change-Number: 31911
Gerrit-PatchSet: 4
Gerrit-Owner: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: osmith <osmith(a)sysmocom.de>
Gerrit-Reviewer: pespin <pespin(a)sysmocom.de>
Gerrit-Comment-Date: Tue, 14 Mar 2023 15:28:35 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Gerrit-MessageType: comment