I followed the build instructions at https://help.dropbox.com/installs-integrations/desktop/linux-commands#build , changing only the name of the source file. The source file I downloaded is the latest, nautilus-dropbox-2020.03.04.tar.bz2.
I am building on CentOS 8 (sure wish I didn't have to and that the rpm build worked for CentOS as well as Fedora).
When I ran the ./configure; make; make install command, the build failed. The output received is shown below. Scroll to the bottom of the block to see the missing config/variables/etc.; I didn't want to leave out the long list of checks in case there's something important there.
Any thoughts on nexst steps? I'm finding a lot of problem using DropBox on anything other than Windows.
[dale@dpcent801 nautilus-dropbox-2020.03.04]$ ./configure; make; make install; configure: loading site script /usr/share/config.site checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /usr/bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether make supports nested variables... yes 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 whether gcc understands -c and -o together... yes checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking build system type... x86_64-pc-linux-gnu checking host system type... x86_64-pc-linux-gnu checking how to print strings... printf checking for a sed that does not truncate output... /usr/bin/sed checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for fgrep... /usr/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 how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop checking how to convert x86_64-pc-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 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 a working dd... /usr/bin/dd checking how to truncate binary pipes... /usr/bin/dd bs=4096 count=1 checking for mt... no checking if : 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... no 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 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... yes checking for pkg-config... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for NAUTILUS... no configure: error: Package requirements (libnautilus-extension >= 2.16.0) were not met: Package 'libnautilus-extension', required by 'virtual:world', not 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 NAUTILUS_CFLAGS and NAUTILUS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** No targets specified and no makefile found. Stop. make: *** No rule to make target 'install'. Stop.
Hi @dalepres; how are you today?
I'm sorry to hear you're having an issue with installing our desktop app on your CentOs machine. Let's take a look at your error log now!
I can see towards the end of the log that some package requirements for nautilus were not met. Can you try installing the libatomic package and then attempt to re-compile from source?
Let me know how you get on!
If you have received similar (or same) message, just install corresponding development package (containing header files and package config description file - extension '.pc'). 😉 Note that package name according to pkg-config and official OS package manager usually match, but it's not mandatory to be the same!
In the case, described by @dalepres, missing package name is 'libnautilus-extension' (pkg-config name) accrding to:
configure: error: Package requirements (libnautilus-extension >= 2.16.0) were not met: Package 'libnautilus-extension', required by 'virtual:world', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix.
For Fedora (and similar) system package name is nautilus-devel; for Ubuntu (and similar) system package name is libnautilus-extension-dev. In the both cases there is 'libnautilus-extension.pc' file on appropriate place. In similar way, other packages, needed according to the corresponding error message, could be found.
Good luck with the build! 🙂
Hope this helps.
The way we work is changing. Share and discover new ways to work smarter with Dropbox in our community.Sound good? Let's get started.
For more info on available support options, see this article.
If you found the answer to your question, please 'like' the post to say thanks to the user!