Closed tasleson closed 3 months ago
Hi @tasleson, Thanks for reporting. Are you going to work on it? Is it just a issue you discovered, or you have 32bits setups you want to work on? I'm asking to determine the real priority.
To be clear 32 bit is not something we are targeting but I'm open to change my mind. In this case it is probably low effort.
Thanks for reporting. Are you going to work on it?
When I get a chance I can look into this a bit more.
Is it just a issue you discovered, or you have 32bits setups you want to work on?
I had a failure to compile for 32bit on a package I maintain that is using ledmon-lib. We'll want to address this, but I don't think it's super high priority. The get_uint64
looks like a real bug if we run into a string that has an integral value > 32 bit on any arch, I'm not sure at the moment about the shift warnings.
We are seeing the same build issue while building on MIPS64:
<command-line>: note: this is the location of the previous definition
utils.c: In function 'get_uint64':
utils.c:118:18: error: passing argument 1 of 'str_toul' from incompatible pointer type [-Wincompatible-pointer-types]
118 | str_toul(&defval, p, NULL, 16);
| ^~~~~~~
| |
| uint64_t * {aka long long unsigned int *}
See http://autobuild.buildroot.net/results/125/1256ff22e9e5a6f0359e2d6d813d9c511d7f27aa/build-end.log
I think it is fixed now. Thanks @tasleson!
I think it is fixed now. Thanks @tasleson!
You're welcome, but I don't see any fixes committed for this, so how is this resolved?
@tasleson yeah my bad. Now it is fixed :)
Description
Using a 32bit gcc tool chain I'm running into compiler error and warnings
Steps to reproduce bug
Compile using 32bit tool chain e.g.
Expected behavior
Clean compile
Actual behavior
Compile error
Possible fix for error:
Compile warnings
Environment
gcc (GCC) 14.0.1 20240411 (Red Hat 14.0.1-0)
Ledmon version
Latest main branch
Ledmon logs
NA
Ledctl logs
NA
Ledmon supported controllers
NA
Additional information
No response