-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Casting warnings in GCC5 #5570
Comments
I just tried to build open62541 on a similar system with Ubuntu 16.04 and ran into a similar error. Also no problems with it on e.g. Ubuntu 22.04 |
Thanks janfelixklein for your quickly test and feed-back, at least it means I am not a single case so far. |
Hey @eziosella @janfelixklein, These look like pretty bening warnings that get amplified by our warning==error compiler flags. If you can contribute a bit the solution can be integrated much faster. Three possible fixes in increasing order of effort:
|
Hey @jpfr, Thanks for your reply, it is exactly as you suggested. As you wrote, this is just one of the possible solutions, probably the easiest way. I would like to contribute trying the solve with the better way in my opinion, resolving the cast warnings. For the third solution, I am not sure of what you meant ('cause my poor technical english, sorry). So, at the end, the quickly solution was: cmake -DCMAKE_INSTALL_PREFIX=/opt/open62541 -DCMAKE_BUILD_TYPE=RelWithDebInfo -DUA_NAMESPACE_ZERO=Full -DBUILD_SHARED_LIBS=On -DUA_MULTITHREADING=0 -DUA_FORCE_WERROR=Off .. I am not an expert in this kind of staff, should I close the issue, or in case I would like to add an extra solution it will be better keep it opened? Thanks. |
I will adjust the title and we can keep it open. But community members might be interested to pick this up and provide a code-level solution that adds more casting. |
@eziosella may I ask why you are using Using this in the GitHub and Azure CIs is already no longer possible, even |
I was just wondering if the project was re-usable in some older machines we have, without be forced to O.S upgrading. |
I have a similar problem while compiling in a emulator (qemu) with pi3 [ 86%] Building C object CMakeFiles/open62541-object.dir/deps/itoa.c.o [ 86%] Building C object CMakeFiles/open62541-object.dir/src/server/ua_subscription_monitoreditem.c.o [ 88%] Building C object CMakeFiles/open62541-object.dir/src/server/ua_subscription_events_filter.c.o [ 90%] Building C object CMakeFiles/open62541-object.dir/src/server/ua_subscription.c.o [ 90%] Building C object CMakeFiles/open62541-object.dir/deps/parse_num.c.o Later it will be a kernel bug [ 4930.094347] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP [ 4930.108195] Modules linked in: cfg80211 rfkill 8021q garp stp llc cdc_ether cdc_subset [ 4930.259473] Hardware name: Raspberry Pi 3 Model B+ (DT) [ 4930.272350] pstate: 80000085 (Nzcv daIf -PAN -UAO -TCO BTYPE=--) [ 4930.273420] pc : bcm2835_sdhost_finish_data+0xec/0xf0 This never shows up before. Any stable branch i can use now? |
I don’t think whatever we do can be responsible for a kernel panic. Sounds like a problem with the emulated peripherals… |
Dear all, I attach on this previous issue because I am following my implementation on this same machine. Now my application is runnin as server as Euromap77 (not fully implementented on xml instances). Anyway as described on my CMAKE parameters the server is running with -DUA_MULTITHREADING=0.
Which is a simple UA_Server_writeValue where a node has been updated from a callback.onRead function. My doubt is, could it depends from multithreading disable? Or from the backtrace do you read any other reasons? Thanks, |
Description
Hi all and thanks for your wonderful project.
I am trying to compile it without success on a lubuntu 16.04.7 LTS but I get the error below:
Background Information / Reproduction Steps
theese are my steps:
what I obtain is:
I have already compile the same commit project with success on a Ubuntu 22.04 64bit, on a Lubuntu 18.04 64bit
Used CMake options:
Checklist
Please provide the following information:
UA_LOGLEVEL
set as low as necessary) attachedThe text was updated successfully, but these errors were encountered: