← All tasks
cppceres-solver/ceres-solver #764Reported task

SuiteSparseQR.hpp: No such file or directory

envgap__ceres-solver__ceres-solver-764

01 / FAILURE SIGNATURE

Captured in a clean container

`/[//]/ceres-solver/internal/ceres/suitesparse.h:46:10: fatal error: SuiteSparseQR.hpp: No such file or directory 46

02 / ENVIRONMENT RECIPE

Base commit
817f5a068881a4aa7a2f11a135e9f2d1e1eb1a5c
Manifest
CMakeLists.txt
Reproduce
cmake --build build --target helloworld -j2 && ./build/bin/helloworld
Run under trace
./build/bin/helloworld

03 / ORIGINAL ISSUE TEXT

ceres-solver/ceres-solver #764 · read the original issue
(Possibly related to issue 400: https://github.com/ceres-solver/ceres-solver/issues/400)

Hello, I have an issue when I try to install ceres on a Ubuntu docker image. Here is the sequence of the install in the Dockerfile:



```

RUN apt-get install libgoogle-glog-dev libgflags-dev -y && \ 

apt-get install libatlas-base-dev -y && \ 

apt-get install libsuitesparse-dev -y && \ 

git clone https://github.com/ceres-solver/ceres-solver && \ 

cd ceres-solver && mkdir build && cd build && \ 

cmake .. && \ 

make -j$(nproc) && \ 

make install

```



and here is the error



`/[//]/ceres-solver/internal/ceres/suitesparse.h:46:10: fatal error: SuiteSparseQR.hpp: No such file or directory 46 | #include "SuiteSparseQR.hpp"`



Do you know why this file cannot be found? Where should it be?
Continue on GitHub ↗

04 / LABELS

Labels checked by running the task · assistant reviewed

No supported category has been assigned.

Label rules and the text that matched
[]

Historical install-only results are not EnvGap validation.

Original environment files are unchanged; this is a proposed already-working control, excluded from lite.

Ubuntu22 system dependencies are not reconstructed as of the issue date; the original reported distribution/version is incomplete.

Tests and benchmark targets are disabled for bounded execution; the upstream numerical solver example is compiled and executed.

Preparation uses current registries. Historical package availability is not enforced here; execution metadata records this limitation separately from the oracle's date-bounding policy.