client_theming icon indicating copy to clipboard operation
client_theming copied to clipboard

linux build fails

Open JR1994 opened this issue 8 years ago • 11 comments

I am trying to build the client in Antergos. I am receiving the following error

/tmp/yaourt-tmp-rican-linux/aur-nextcloud-client-git/src/nextcloud-client/client/src/libsync/theme.cpp:33:39: fatal error: /tmp/yaourt-tmp-rican-1/aur-nextcloud-client-git/src/nextcloud-client/nextcloudtheme/nextcloudtheme.h: No such file or directory
 #  include INCLUDE_FILE(THEME_INCLUDE)
                                       ^
compilation terminated.
make[2]: *** [src/libsync/CMakeFiles/nextcloudsync.dir/build.make:735: src/libsync/CMakeFiles/nextcloudsync.dir/theme.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:243: src/libsync/CMakeFiles/nextcloudsync.dir/all] Error 2
make: *** [Makefile:152: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
==> ERROR: Makepkg was unable to build nextcloud-client-git.
==> Restart building nextcloud-client-git ? [y/N]
==> ---------------------------------------------
==> n

JR1994 avatar May 26 '17 22:05 JR1994

cc @ivaradi

enoch85 avatar May 29 '17 12:05 enoch85

I am not familiar with makepkg, but I noticed that your source seems to be in

/tmp/yaourt-tmp-rican-linux/aur-nextcloud-client-git/src/

whereas the build procedure tries to look for the header in:

/tmp/yaourt-tmp-rican-1/aur-nextcloud-client-git/src/

Where does the second path come from? Could it be some leftover from an earlier build attempt?

ivaradi avatar May 29 '17 16:05 ivaradi

Hi Guys - we've been having the same issue in our office for a week now across all our new machines - and it's really causing us problems. Cannot complete the nextcloud-client build via the AUR no matter what we try. Please help!

missioncontrolceo avatar Jun 02 '17 19:06 missioncontrolceo

@JR1994 @entropylabs , Why not use the PPA? Are you not on UBuntu or Debian?

enoch85 avatar Jun 02 '17 19:06 enoch85

No - on Arch on all our machines.

missioncontrolceo avatar Jun 02 '17 19:06 missioncontrolceo

This error occurs while building on Arch Linux and the current fix is to downgrade python-sphinx to version 1.5.1-2 via Arch Archive (currently in the AUR Version 1.5.1-1 of python-sphinx is recommended, but this failed the installation for me, Version 1.5.1-2 did the job).

Sources: AUR Arch Archive Repository for Phyton-Sphinx Direct Download Link for Version 1.5.1-2

rippin93 avatar Jun 03 '17 22:06 rippin93

@rippin93

currently in the AUR Version 1.5.1-1 of python-sphinx is recommended

It is actually version 1.5.5-1 which is recommended (cf. lerux's comment in the AUR). It works for me.

sylph1o avatar Jun 04 '17 13:06 sylph1o

Version 1.5.1-2 did the job

It works for me.

So this issue is solved?

enoch85 avatar Jun 04 '17 16:06 enoch85

@enoch85 : In my opinion, it is only a workaround. Although I have no other need of python-sphinx and can keep it at this older version, others may depend on a later version. Additionnally, if any Arch Linux user with a system up to date has to research this error and find this workaround before he can build successfully, it still seems to be an unsolved issue.

sylph1o avatar Jun 05 '17 14:06 sylph1o

@sylph1o Thanks for pointing out my mistake, didn't even realize o.O

@enoch85 No this is just an arch workaround, you should update your code which uses python-sphinx to the current version which is 1.6.3 afaik.

rippin93 avatar Jun 05 '17 20:06 rippin93

@rippin93 Do you mean the code in the client itself, or do you mean the code in the instructions to build it?

enoch85 avatar Jun 05 '17 20:06 enoch85