ubuntu - Guacamole Deprecated-Declarations issues on Make

Collectives™ on Stack Overflow

Find centralized, trusted content and collaborate around the technologies you use most.

Learn more about Collectives

Teams

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Learn more about Teams

I'm trying to install Guacamole 1.4.0 on a 22.04 Ubuntu (running from a Virtual Machine) according to the following tutorial : Install and Use Guacamole on Ubuntu .

I'm stuck on Step 3: Build the Guacamole Server From Source , at the 6th Step .

When running the command make :

I encounter a


    all warning being treated as errors

Those warnings are -WError=deprecated-declarations

They appear in


    libguac_common_ssh_la-key.lo


    Since OpenSSL 3.0 rsa_key is deprecated

I tried:


    -Wno-deprecated

: Doesn't change anything

Modifying the


    ./configure

file

Checking for more updated versions (1.4.0 is the latest)

The solution seems to be here:

The GUACAMOLE-1602 is the same thing as I have

It is said "This has already been resolved. The line of code in question doesn't exist in the current source on git"

Questions:

How can I get the version that corrects this issue? I can't find it.

Do you have another solution to help?

You should add the


    -Wno-error

option to the compile line. This will turn warnings back into warnings, and not errors. It's pretty much always wrong to ship officially released packages with


    -Werror

enabled. That's great for development, but it just causes pain for users of the release. – MadScientist Jan 3 at 19:22 I said "to the compile line" not to the make line.


    -Wno-error

is an option to the compiler (GCC), not to make. You have to figure out what make variable(s) contain the compiler options. I don't know anything about this project, but if it follows the usual rules and conventions for source code releases, you should be able to use something like


    make CFLAGS='-O2 -Wno-error'

. If it doesn't follow the usual conventions you'll have to either examine the makefile yourself to figure it out, or get advice from someone who knows about this particular source code (it's not a makefile issue). – MadScientist Jan 3 at 20:33

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question . Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.
Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers .