Werror flag is making impossible to compile in Linux (Manjaro) about physx HOT 11 CLOSED

A better fix would be to remove the unused variable or ignore that specific warning: -Wno-unused-but-set-variable

from physx.

There are many such places with unused variables. Trying to fix them all would be a chore. Needs a fix upstream or allowing to disable this warning for release builds.

Opting for proper fix though. I always build with Wall Werror and just can't understand how such things can end up in a release.

from physx.

There were recent changes to the behavior of unused-but-set-variable, to warn in additional cases, so maybe they only tested PhysX with an older compiler version.

from physx.

Please see https://github.com/NVIDIA-Omniverse/PhysX/blob/release/104.1/physx/documentation/platformreadme/linux/README_LINUX.md for supported platforms and compiler versions, in your case that would be

    Ubuntu 20.04 LTS with gcc 9 or clang 10
    Ubuntu 22.04 LTS with gcc 11 or clang 14

For anything newer I'm afraid we can't guarantee that it just works out of the box. As @Zeblote mentions, you're free to disable the warning.

from physx.

Using "gcc 11.3.1" here and it causes many warnings failing to build. According to your statement gcc 11 is supported and should work so in my opinion this is a clear bug then... unless I'm misunderstanding something here.

from physx.

@LordOfDragons It should build, yes. Can you share some more details about your setup, and the build log that shows the compiler invocation and the error?

from physx.

Which file are you looking for?

from physx.

Similar to the information that was provided in #25, i.e., the exact error message and the gcc command that make is calling so we can see all the flags passed to it.
I think you should be able to read all that in the console log if you run make VERBOSE=1

from physx.

I can't find any file mentioned there to post so I piped the console output into a file: https://pastebin.com/1t4CFGJA . I do though not see the compile parameters in there so is there some kind of log file written which contains this information? As you can see I've modified the build files to not raise an error for each warning which is why you can see all of the problems.

And output of "g++ --version"
g++ (Gentoo 11.3.1_p20221209 p3) 11.3.1 20221209

from physx.

interesting, it appears that the same minor version of gcc behaves differently on different linux flavors (?!).
I just checked again and can confirm that we're testing on gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0

from physx.

Well... there is a small difference (11.3.1 -> 11.3.0) but I don't think that's to blame.

from physx.