Package Details: caffe-doc-git 1.0.r136.g9b8915401-1

Git Clone URL: https://aur.archlinux.org/caffe-git.git (read-only, click to copy)
Package Base: caffe-git
Description: A deep learning framework made with expression, speed, and modularity in mind (cpu only, documentation, git version)
Upstream URL: https://caffe.berkeleyvision.org/
Keywords: ai artificial cuda intelligence nvidia
Licenses: BSD
Conflicts: caffe-doc
Provides: caffe-doc
Submitter: jyantis
Maintainer: dbermond
Last Packager: dbermond
Votes: 23
Popularity: 0.000000
First Submitted: 2014-12-08 01:10 (UTC)
Last Updated: 2022-03-01 14:46 (UTC)

Latest Comments

1 2 3 4 5 6 Next › Last »

dbermond commented on 2019-11-21 15:22 (UTC)

@RonObvious Package is building fine. Uninstall the package when building it, or build in a clean chroot.

RonObvious commented on 2019-11-21 09:43 (UTC) (edited on 2019-11-21 11:47 (UTC) by RonObvious)

Update: If I remove the package, I can then build it. I cannot build it as long the previous version is still installed.

Does the new version (from 2019-11-21) compile for other people? Not for me. Tried it with yay, and then "by hand" (git clone ... makepkg), both fail. I updated everything first (hey, this IS arch, right?), so the problem is not any out-of-date dependencies. I suspect it's quite the opposite -- that it doesn't like my version of the boost-libs. It fails, ultimately, with a long list of undefined linker references, e.g.

/usr/bin/ld: /usr/lib/libcaffe.so: undefined reference to `boost::python::converter::detail::arg_to_python_base::arg_to_python_base(void const volatile*, boost::python::converter::registration const&)'
/usr/bin/ld: /usr/lib/libcaffe.so: undefined reference to `PyEval_CallFunction'

Up at the top of the build, there were a long list of warnings of the form: 

 CXX/LD -o .build_release/tools/upgrade_net_proto_binary.bin
 /usr/bin/ld: warning: libboost_python37.so.1.71.0, needed by /usr/lib/libcaffe.so, not found (try using -rpath or -rpath-link)
 /usr/bin/ld: warning: libpython3.7m.so.1.0, needed by /usr/lib/libcaffe.so, not found (try using -rpath or -rpath-link)

I have libboost_python38.so (not 37) in /lib. I'm not sure if the libcaffe.so mentioned is the old one (pre-update) or the one that was just built (chroot?). Note that I have caffee-git installed (but have experimented with other versions of caffee in the past).

More details on request. For the moment, I'd just like to know if it's "just me", or if other people are having this problem too.

dbermond commented on 2018-08-22 18:18 (UTC)

Important notice:

This package now provides the non-cuda version (as known as the 'cpu only' build).

If you want caffe (git) with cuda support, use package caffe-cuda-git. This new package naming schema will better reflect the package contents. This conforms to tensorflow package naming from the official repositories.

danlamanna commented on 2017-12-20 18:15 (UTC) (edited on 2017-12-20 18:16 (UTC) by danlamanna)

I'm getting a lot of errors when building with the newest cuda, similar to these:

/usr/lib/libcaffe.so: undefined reference to `cudaStreamCreateWithFlags@libcudart.so.9.0'

/usr/lib/libcaffe.so: undefined reference to `cublasDasum_v2@libcublas.so.9.0'

smllmn commented on 2017-10-18 18:39 (UTC) (edited on 2017-10-18 18:41 (UTC) by smllmn)

I'm struggling to get this to compile. I get an error that CUDA only supports gcc versions up to 5, but this package requires (and uses) gcc 6. I'm aware that the cuda package provides a version of gcc 5 in /opt/cuda/bin, but if I try and set the CUSTOM_CXX variable in the Makefile.config, caffe refuses.

dbermond commented on 2017-04-01 17:08 (UTC)

It's possible to get this apparently harmless warning during link time when rebuilding for cudnn 6.0: "warning: libcudnn.so.5, needed by /usr/lib/libcaffe.so, not found". To avoid it, clear your source tree before rebuilding. You can do this, for example, by using the makepkg '--cleanbuild' option.

dbermond commented on 2017-04-01 16:02 (UTC)

@petronny Thank you

petronny commented on 2017-03-28 08:44 (UTC)

Knowing you have run the tests is fine. I don't want to add tests to PKGBUILD by default either. Thanks

dbermond commented on 2017-03-27 18:25 (UTC)

@petronny Thanks for pointing the missing 'cuda' dependency. I've just added it. Regarding checks/tests, I think it's not a good idea to add it by default. It usually takes a lot of time to run and it will prevent the package to be built in case of failures. So I've added it as a comment block and users that need to make the tests should manually enable it. Currently I'm getting a 100% success tests, without hdf5 test errors.

petronny commented on 2017-03-27 10:35 (UTC) (edited on 2017-03-27 11:36 (UTC) by petronny)

And please run make test make runtest to check if all the functions work. Here I get some errors about hdf5 and cannot pass the tests.

1 2 3 4 5 6 Next › Last »