masterkorp ~ $ freecad
freecad: error while loading shared libraries: libboost_signals.so.1.52.0: cannot open shared object file: No such file or directory
masterkorp ~ $ pacman -Qs boost
local/boost 1.53.0-2
Free peer-reviewed portable C++ source libraries - Development
local/boost-libs 1.53.0-2
Free peer-reviewed portable C++ source libraries - Runtime
Yes, I've rebuilt freecad after the update. Still getting the error.
Search Criteria
Package Details: freecad-git 1.1.0.41361.g774ec2cc93-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/freecad-git.git (read-only, click to copy) |
---|---|
Package Base: | freecad-git |
Description: | A general purpose 3D CAD modeler - git checkout |
Upstream URL: | https://www.freecad.org/ |
Licenses: | LGPL |
Conflicts: | freecad, freecad-appimage, freecad-appimage-git |
Provides: | freecad |
Submitter: | gborzi |
Maintainer: | greyltc (adrianinsaval) |
Last Packager: | adrianinsaval |
Votes: | 107 |
Popularity: | 1.16 |
First Submitted: | 2012-03-03 13:46 (UTC) |
Last Updated: | 2025-04-22 00:51 (UTC) |
Dependencies (40)
- boost-libs
- coin (coin-gitAUR)
- fmt (fmt-gitAUR)
- glew (glew-libepoxyAUR, glew-wayland-gitAUR, glew-gitAUR)
- jsoncpp (jsoncpp-cmake-gitAUR, jsoncpp-cmakeAUR, jsoncpp-gitAUR)
- med (med-openmpi)
- netcdf (netcdf-openmpi)
- opencascade (opencascade-gitAUR)
- openmpi (openmpi-gitAUR)
- pybind11 (pybind11-gitAUR)
- pyside6
- pyside6-tools
- python-matplotlib (python-matplotlib-gitAUR)
- python-packaging
- python-pivy
- python-ply
- python-yaml (python-yaml-gitAUR)
- qt6-5compat
- qt6-base (qt6-base-gitAUR, qt6-base-headlessAUR)
- qt6-svg
- qt6-tools
- shared-mime-info
- verdict
- vtk (vtk-gitAUR, vtk93AUR)
- xerces-c
- yaml-cpp
- boost (boost-gitAUR) (make)
- cmake (cmake-gitAUR, cmake3AUR) (make)
- eigen (eigen-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- ninja (ninja-kitwareAUR, ninja-memAUR, ninja-fuchsia-gitAUR, ninja-gitAUR, ninja-jobserverAUR) (make)
- nlohmann-json (nlohmann-json-gitAUR) (make)
- shiboken6 (make)
- swig (swig-gitAUR) (make)
- pugixml (pugixml-gitAUR) (check)
- calculix-ccxAUR (optional) – FEM solver backend
- graphviz (optional) – dependency graph support
- libspnav (libspnav-gitAUR) (optional) – 3D mouse support
- openscad (openscad-objects-gitAUR, openscad-qt6-gitAUR, openscad-gitAUR) (optional) – OpenSCAD support
- python-pip (optional) – support installing python dependencies for addons
Required by (4)
- freecad-a2plus-git (requires freecad)
- freecad-cadquery-git (requires freecad)
- freecad-fcgear-git (requires freecad)
- openmc-git (requires freecad)
Sources (1)
Latest Comments
« First ‹ Previous 1 .. 38 39 40 41 42 43 44 45 46 47 48 .. 58 Next › Last »
masterkorp commented on 2013-05-02 10:36 (UTC)
gborzi commented on 2013-04-21 22:06 (UTC)
Updated.
Samsagax commented on 2013-04-21 16:52 (UTC)
@gborzi: You should update this PKGBUILD according to pacman's new feature for git packages: https://wiki.archlinux.org/index.php/VCS_PKGBUILD_Guidelines#VCS_sources
masterkorp commented on 2013-03-25 15:48 (UTC)
Hello, makepkg MAKEFLAGS doesn't seem to work,
wich is annoying to compile.
gborzi commented on 2013-03-08 17:48 (UTC)
@vinvin
I think that the problem reported by budulay only happens if qt5-base, which provides a /usr/bin/qmake, is installed.
vinvin commented on 2013-03-08 17:26 (UTC)
I successfully built the package yesterday without this fix.
gborzi commented on 2013-03-08 17:14 (UTC)
@budulay,
I missed the comment you made on March 5th, sorry. Thanks for the fix, the package is updated.
budulay commented on 2013-03-08 16:33 (UTC)
Adding
-DQT_QMAKE_EXECUTABLE=/usr/bin/qmake-qt4
to the cmake line fixes the problem I had below.
budulay commented on 2013-03-05 19:02 (UTC)
Wouldn't compile for me after the qt5 update. Qt4 is installed, but cmake can't find it:
CMake Error at /usr/share/cmake-2.8/Modules/FindQt4.cmake:1216 (message):
Found unsuitable Qt version "5.0.1" from /usr/bin/qmake, this code requires
Qt 4.x
gborzi commented on 2013-02-17 16:38 (UTC)
Updated.
Pinned Comments
adrianinsaval commented on 2023-03-12 14:50 (UTC)
If the check fails there is little I can do about it as it most likely needs to be fixed upstream, in such cases report those upstream (maybe wait a day or two as sometimes it's quickly solved upstream) or skip the check with
makepkg --nocheck
if you don't care about the functionality that is being reported as failing in the check.