unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Raghav Gururajan <raghavgururajan@disroot.org>
Cc: guix-devel@gnu.org
Subject: Re: Linphone
Date: Wed, 25 Mar 2020 23:29:50 +0100	[thread overview]
Message-ID: <20200325232950.59dd1b1e@scratchpost.org> (raw)
In-Reply-To: <7aa517d42c2bd7b527712c73ca5eac58@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Hi,

I tried

guix build -K linphone-desktop

then waited until it told me the build directory (which was
/tmp/guix-build-linux-libre-5.5.10.drv-0), then

$ which strace
<remember that name>
$ cd /tmp/guix-build-linux-libre-5.5.10.drv-0
$ source environment-variables
$ cd source
$ .....strace -f cmake . 2>&1 |grep -i bctoolbox |grep -i cmake
It says, among other things, that it can't open
/gnu/store/m92m6bg0xcl28djxg8h97sszf3gdl42r-bctoolbox-4.3.1/share/bctoolbox/cmake/BcToolboxConfig.cmake
.

So I checked that directory and it indeed does not have that file.

But it does have
/gnu/store/m92m6bg0xcl28djxg8h97sszf3gdl42r-bctoolbox-4.3.1/share/bctoolbox/cmake/bctoolboxConfig.cmake
-- note the different case of the name.

So I'd say either linphone-desktop or bctoolbox has the case wrong in some cmake file.

linphone-desktop has the following line:

./CMakeLists.txt:  include("${EP_bctoolbox_CONFIG_DIR}/BcToolboxConfig.cmake")

... and that line is not going to work as-is.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-03-25 22:29 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-25 18:34 Linphone Raghav Gururajan
2020-03-25 22:04 ` Linphone Ricardo Wurmus
2020-03-28  0:55   ` Linphone Maxim Cournoyer
2020-03-28  1:42   ` Linphone Raghav Gururajan
2020-03-28 22:42   ` Linphone Raghav Gururajan
2020-03-29  6:44     ` Linphone Ricardo Wurmus
2020-03-29  6:54     ` Linphone Raghav Gururajan
2020-03-30  1:29     ` Linphone Raghav Gururajan
2020-03-31 15:18     ` Linphone Raghav Gururajan
2020-04-02 16:44     ` Linphone Raghav Gururajan
2020-04-02 20:57     ` Linphone Raghav Gururajan
2020-04-02 23:33     ` Linphone Raghav Gururajan
2020-04-03 23:51     ` Linphone Raghav Gururajan
2020-03-25 22:29 ` Danny Milosavljevic [this message]
2020-03-25 22:42   ` Linphone Danny Milosavljevic
2020-03-25 22:48   ` Linphone Danny Milosavljevic
2020-03-26 12:47   ` Linphone Raghav Gururajan
2020-03-26 14:17     ` Linphone Danny Milosavljevic
2020-03-26 14:24     ` Linphone Raghav Gururajan
2020-03-26 17:53     ` Linphone Raghav Gururajan
2020-03-26 19:24       ` Linphone Danny Milosavljevic
2020-03-26 19:28       ` Linphone Raghav Gururajan
2020-03-26 21:53       ` Linphone Raghav Gururajan
2020-03-25 22:43 ` Linphone Danny Milosavljevic
2020-03-26 12:27 ` Linphone Raghav Gururajan
2020-03-26 13:30   ` Linphone Ricardo Wurmus
2020-03-26 13:35   ` Linphone Raghav Gururajan
2020-03-26 12:40 ` Linphone Raghav Gururajan

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200325232950.59dd1b1e@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=raghavgururajan@disroot.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).