Activity for libtirpc
-
libtirpc released /libtirpc/1.3.7/libtirpc-1.3.7.tar.bz2
-
-
Finle modified a comment on discussion Open Discussion
Helpful thread issues with libtirpc can get tricky, especially when dealing with legacy systems. Appreciate the insights shared here. Also, for anyone in Pakistan needing to check their BISP PMT Score this link might help
-
Helpful thread issues with libtirpc can get tricky, especially when dealing with legacy systems. Appreciate the insights shared here. Also, for anyone in Pakistan needing to check their https://8171ehsaasprogram.net/176/pmt-score/ this link might help
-
-
-
-
-
Martin Hierholzer modified a comment on discussion Open Discussion
Hi, I am not sure how to report bugs properly, the ticket system does not allow to create new issues here... I (resp. LSAN) have found a small memory leak: rpc_uaddr2taddr_af() is allocating, depending on the address type, the buffer ret->buf, but when called e.g. via pmap_set(), only the outer buffer ls freed via "free(na)". There should be a "free(na->buf)" before... Cheers, Martin
-
Hi, I am not sure how to report bugs properly, the ticket system does not allow to create new issues here... I (resp. asan) have found a small memory leak: rpc_uaddr2taddr_af() is allocating, depending on the address type, the buffer ret->buf, but when called e.g. via pmap_set(), only the outer buffer ls freed via "free(na)". There should be a "free(na->buf)" before... Cheers, Martin
-
-
-
debbierodgers modified a comment on discussion Open Discussion
You've identified a typo in the src/libtirpc.map file: Original entry: key_secret_is_set; Corrected entry: key_secretkey_is_set; The typo is that key_secret_is_set should actually be key_secretkey_is_set. Solution Steps Identify the Patch You've provided a patch that shows the necessary change in the src/libtirpc.map file. Let's break down the patch: diff --- a/src/libtirpc.map +++ b/src/libtirpc.map @@ -298,7 +298,7 @@ key_gendes; key_get_conv; key_setsecret; - key_secret_is_set; + key_secretkey_is_set;...
-
You've identified a typo in the src/libtirpc.map file: Original entry: key_secret_is_set; Corrected entry: key_secretkey_is_set; The typo is that key_secret_is_set should actually be key_secretkey_is_set. Solution Steps Identify the Patch You've provided a patch that shows the necessary change in the src/libtirpc.map file. Let's break down the patch: diff --- a/src/libtirpc.map +++ b/src/libtirpc.map @@ -298,7 +298,7 @@ key_gendes; key_get_conv; key_setsecret; - key_secret_is_set; + key_secretkey_is_set;...
-
Neustradamus posted a comment on discussion Open Discussion
Dear @libtirpc team, @steved12345, @acharbon, @astrand, It is possible to have a GitHub organization/repository... Steve is here: https://github.com/stevedd astrand is here: https://github.com/astrand acharbon (not sure): https://github.com/acharbon Thanks in advance. Regards.
-
saim modified a comment on discussion Open Discussion
Hello dear You may need to update the Makefile to include the desired target or resolve the issue with the missing "check-recursive" target. It seems like I was also facing a similar issue for my website SRD STATUS CHECK . I used this method and it helped me a lot. Thanks.
-
Hello dear You may need to update the Makefile to include the desired target or resolve the issue with the missing "check-recursive" target. It seems like you were also facing a similar issue, and you contacted the website SRD STATUS CHECK for assistance. You can do the same, and they should be able to provide you with a solution to this problem.
-
-
-
NOAH posted a comment on discussion Open Discussion
Thank you for sharing this valuable information! It's great to know that updating libtirpc to version 1.2.6 resolves the issue with compiling on GCC 10 or newer. This kind of information can be very helpful for others who may run into the same problem. However, you could provide a bit more context for readers who might not be familiar with the specifics. For instance, you could briefly explain what libtirpc is used for or why upgrading the library is necessary for resolving the issue. But, I have...
-
Velma Richards posted a comment on discussion Open Discussion
LFS refers to the capability of operating systems and applications to handle files larger than 2 GB (32-bit limit). It's essential to note that, with the proliferation of multimedia content and large datasets, the need for LFS has become more prevalent in recent years. By mandating libraries to add LFS: Scalability: You prepare the system for working with significantly large files, a scenario which is increasingly common with the current data trends. Futureproofing: Ensuring that your software is...
-
Alan Duncan modified a comment on discussion Open Discussion
The issue you're facing with redundant redeclarations of the bindresvport function seems to stem from conflicting definitions of this function in different header files. This can often occur when using libraries or headers from different sources that define overlapping symbols. Check here the following step to solve this issue. Check for Updates: Libraries and projects like tirpc and glibc might release updates to address such conflicts and improve compatibility. Namespace Management: Ensure that...
-
The issue you're facing with redundant redeclarations of the bindresvport function seems to stem from conflicting definitions of this function in different header files. This can often occur when using libraries or headers from different sources that define overlapping symbols. To address this kind of issue, developers typically follow a few steps: [Check here](https://sassastatuscheck350.co.za/) for Updates: Libraries and projects like tirpc and glibc might release updates to address such conflicts...
-
Zi Lin posted a comment on discussion Open Discussion
At ChromiumOS, we have decided to mandate libraries to add LFS, making sure compilers utilizing 64-bit syscalls instead of 32-bit syscalls. We have found ways to maintain a small local patch to this goal, but it will be nice to push this upstream as well. Context, we have following QA output that fails libtirpc builds without LFS support: 12:19:12.151 * QA Notice: The following files were not built with LFS support: 12:19:12.247 * Please see https://issuetracker.google.com/201531268 for details....
-
Andrey Filipenkov posted a comment on discussion Open Discussion
Hi. I've tried building the latest version (1.3.3) with Apple clang 13 (Xcode 13.4.1) but there're errors. Is macOS no longer supported? I see that some macOS-specific code exists in the library. Described my attempt and errors in https://github.com/unfs3/unfs3/pull/25#issuecomment-1300402653
-
Maxwell Johnson posted a comment on discussion Open Discussion
libtirpc v1.1.4 has a know bug with compiling with > GCC-10 https://bugs.gentoo.org/705896 Returns error /usr/lib/gcc/x86_64-cros-linux-gnu/10.3.0/../../../../x86_64-cros-linux-gnu/bin/ld: /tmp/git/libnvidia-container/deps/usr/local/lib/libtirpc.a(libtirpc_la-rpc_generic.o):/tmp/git/libnvidia-container/deps/src/libtirpc-1.1.4/src/rpc_com.h:64: multiple definition of `__svc_xports'; Updating libtirpc to v1.2.6 corrects the issue
-
-
-
-
-
nathan owe posted a comment on discussion Open Discussion
I was hoping test/check could be added. Looked at the Makefile as it has check: check-recursive but that target does not exist.
-
-
-
-
-
-
-
Zhixiong Chi posted a comment on discussion Open Discussion
Hi all, When trying to compile the application using tirpc with the following compiling option "-Werror -Wredundant-decls" and including the header <rpc rpc.h="">, then we get the error output: usr/include/tirpc/rpc/rpc.h:83:12: error: redundant redeclaration of 'bindresvport' [-Wredundant-decls] extern int bindresvport(int, struct sockaddr_in ); Since the bindresvport is also implmented in glibc. usr/include/netinet/in.h:502:12: note: previous declaration of 'bindresvport' was here extern int bindresvport...
-
-
-
-
-
-
-
Valery Kartel posted a comment on discussion Open Discussion
Hi, I found a typo in src/libtirpc.map There is a key_secret_is_set but must be key_secretkey_is_set...
-
-
-
-
-
-
-
Juergen Daubert posted a comment on discussion Open Discussion
building of libtirpc doesn't work if kerberos is not installed. ./configure --disable-gssapi...
-
-
-
rahul shah posted a comment on discussion Open Discussion
I use rpcbind-0.1.7 and libtirpc -0.2.1 for arm. i use arm-linux gcc 3.3.2 toolchain...
-
-
1
