'configure: error: You need the boost signals library to compile Ekiga' - what can I try to fix this error?

8 respostas [Última entrada]
Staircase
Desconectado
Joined: 02/24/2022

I am trying to install Ekiga but I get this error message:


user@x220: ~/ekiga-4.0.1$ ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking target system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking how to create a ustar tar archive... gnutar
checking whether to enable maintainer-specific portions of Makefiles... yes
checking whether make supports nested variables... yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... no
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking how to run the C++ preprocessor... g++ -E
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... (cached) GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for gcc option to accept ISO C99... unsupported
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking for library containing strerror... none required
checking for ANSI C header files... (cached) yes
checking whether OS type is supported... yes
checking Byte order... checking whether byte ordering is bigendian... no
little endian
checking whether NLS is requested... yes
checking for intltool >= 0.35.0... 0.51.0 found
checking for intltool-update... /usr/bin/intltool-update
checking for intltool-merge... /usr/bin/intltool-merge
checking for intltool-extract... /usr/bin/intltool-extract
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for perl... /usr/bin/perl
checking for perl >= 5.8.1... 5.30.0
checking for XML::Parser... ok
checking for GTK... yes
checking for GLIB... yes
checking for boostlib >= 1.34... yes
checking whether the Boost::Signals library is available... no
configure: error: You need the boost signals library to compile Ekiga
user@x220:~/ekiga-4.0.1$

I queried 'configure: error: You need the boost signals library to compile' on this forum and in a search engine but I could not find any answer.

What can I try to install Ekiga?

FYI I want to install Ekiga so that I can make calls via JMP (https://jmp.chat/).

I got Ekiga from https://download.gnome.org/sources/ekiga/4.0/

Magic Banana

I am a member!

Desconectado
Joined: 07/24/2010

I would try again after installing from Trisquel's repository the package named "libboost-dev".

eric23
Desconectado
Joined: 06/30/2017

I believe you would have to install this:

libboost-signals1.67-dev

Magic Banana

I am a member!

Desconectado
Joined: 07/24/2010

I had not seen that one: it is indeed certainly the package to install.

Staircase
Desconectado
Joined: 02/24/2022

Thank you Magic Banana and eric23. "sudo apt install libboost1.67-dev" and "sudo apt install libboost-signals1.67-dev" fixed the error.

I have another question though. I ran "$ ./configure" again and encountered the following errors:


checking whether the Boost::Signals library is available... yes
configure: error: Could not find a version of the library!

Then I ran:


$ ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu/

And the output was:


checking for boostlib >= 1.34... yes
checking whether the Boost::Signals library is available... yes
checking for exit in -lboost_signals... yes
checking for XML... no
configure: error: Package requirements (libxml-2.0) were not met:

No package 'libxml-2.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables XML_CFLAGS
and XML_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

So I ran:


$ sudo apt install libxml2-dev

Then I tried "$ ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu/" again and got:


checking whether the Boost::Signals library is available... yes
checking for exit in -lboost_signals... yes
checking for XML... yes
checking for GCONF... no
configure: error: Package requirements (gconf-2.0 >= 2.6.0) were not met:

No package 'gconf-2.0' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GCONF_CFLAGS
and GCONF_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

So I ran:


sudo apt install libgconf2-dev

Then I tried "$ ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu/" again and got:

And I got:


checking whether the Boost::Signals library is available... yes
checking for exit in -lboost_signals... yes
checking for XML... yes
checking for GCONF... yes
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for EDS... no
configure: error: Package requirements (libebook-1.2) were not met:

No package 'libebook-1.2' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables EDS_CFLAGS
and EDS_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

So I ran:


$ sudo apt install libebook1.2-dev

Then I tried "$ ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu/" again and got:


checking whether the Boost::Signals library is available... yes
checking for exit in -lboost_signals... yes
checking for XML... yes
checking for GCONF... yes
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for EDS... yes
checking for NOTIFY... no
checking for LDAP includes in /usr/include/...
configure: error: You need the LDAP headers to compile Ekiga with LDAP support

Then I tried "$ ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu/" once more and got:


checking for boostlib >= 1.34... yes
checking whether the Boost::Signals library is available... yes
checking for exit in -lboost_signals... yes
checking for XML... yes
checking for GCONF... yes
Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation
Using $(sysconfdir)/gconf/schemas as install directory for schema files
checking for EDS... yes
checking for NOTIFY... no
checking for LDAP includes in /usr/include/...
checking for main in -lldap... yes
checking for LIBSASL2 includes in /usr/include/...
configure: error: You need the SASL2 library to compile Ekiga

I don't mind continuing iterating as per the error messages - although, I would like to know:

am I missing something that there are some many missing libraries? Or shall I just carry on installing what the error messages suggest?

Thank you for you help again earlier.

Ark74

I am a member!

I am a translator!

Desconectado
Joined: 07/15/2009

To avoid minimize the guessing, use

sudo apt-get build-dep ekiga

that will avoid or minimize the packages you'll require to manually install.

Another path would be to use guix repository, as they provide binaries not tied to the system, so they can be up-to-date with the current project.
Cheers.

eric23
Desconectado
Joined: 06/30/2017

I tried this command but it responds there is no ekiga source package. That is because there is no package ekiga in the repositories. Ekiga has been abandoned upstream.

Ark74

I am a member!

I am a translator!

Desconectado
Joined: 07/15/2009

Oh! that's correct, I had no idea.
Sorry, then my yeah my suggestion will not help.

Cheers!

Staircase
Desconectado
Joined: 02/24/2022

"Ekiga has been abandoned upstream."

Thanks Eric23. I was not too sure what to think of the maintenance status of Ekiga; some still seem to be using Ekiga fine - I looked again and found this in the list of Ekiga:

>Hi,
>
>Unfortunately, ekiga has not been maintained for several years now, sorry...

https://mail.gnome.org/archives/ekiga-list/2022-April/msg00001.html

The message was signed by a "regulate contributor", listed on https://www.ekiga.org/community.html.

I am sharing the information in case others seek to install Ekiga.

JMP's support mentioned to me Dino 3.0 as an alternative; I will try to install that.

P.-S.: Ark74, thank you for the tip anyway.