From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] ceres-solver-devel cmake files wrong lib path
Date: Sat, 22 Jul 2023 08:20:13 +0200 [thread overview]
Message-ID: <20230722062013.ylZ_zZ9PjUX117ST4TFBq53SlRZw76r4-2Fu9eZtigI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45166@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
Closed issue by OliveThePuffin on void-packages repository
https://github.com/void-linux/void-packages/issues/45166
Description:
### Is this a new report?
Yes
### System Info
Void 5.15.72_1 aarch64-musl
### Package(s) Affected
ceres-solver-devel-2.0.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
I haven't found any
### Expected behaviour
the cmake files in the ceres-solver-devel package point to real folders and files like
`/usr/lib/include`
`/usr/lib/libglog.so`
### Actual behaviour
the cmake files actually point to non-existant files and folders like this:
`/usr/aarch64-linux-musl/usr/lib/include`
`/usr/aarch64-linux-musl/usr/lib/libglog.so`
for some reason this bug does not exist on x86_64-glibc (the only other platform I tested)
### Steps to reproduce
look at
`/usr/lib/cmake/Ceres/CeresConfig.cmake` and
`/usr/lib/cmake/Ceres/CeresTargets.cmake`
search for the string "aarch64-linux-musl"
or just try to compile
https://ceres-solver.googlesource.com/ceres-solver/+/master/examples/helloworld.cc
against the library on aarch64-musl
prev parent reply other threads:[~2023-07-22 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 6:32 [ISSUE] " OliveThePuffin
2023-07-22 0:31 ` OliveThePuffin
2023-07-22 0:32 ` OliveThePuffin
2023-07-22 6:20 ` sgn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230722062013.ylZ_zZ9PjUX117ST4TFBq53SlRZw76r4-2Fu9eZtigI@z \
--to=sgn@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).