From: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
To: Quiliro Ordonez Baca <quiliro@riseup.net>
Cc: help-guix@gnu.org
Subject: Re: path error
Date: Tue, 27 Feb 2018 00:05:03 +0100 [thread overview]
Message-ID: <20180227000503.192f7560@alma-ubu> (raw)
In-Reply-To: <877eqza2xl.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1696 bytes --]
Hi Quiliro,
On Mon, 26 Feb 2018 15:52:54 -0500
Quiliro Ordonez Baca <quiliro@riseup.net> wrote:
> I have downloaded OpenKinect. (Disclosure: I have not checked wether
> it is has non-libre software yet.) I typed:
I haven't checked either. I just saw the keyword "firmwire", which
smells like binaries.
>
> git clone https://github.com/OpenKinect/libfreenect
> cd libfreenect
> mkdir build
> cd build
> cmake -L ..
>
> But I get an error on executing that command. Here is the output:
>
> quiliro@portkomputilo ~/libfreenect/build$ cmake -L ..
[...]
> gcc: error trying to exec 'as': execvp: No existe el fichero o el
> directorio
[...]
> Please suggest possible solution. Thank you very much. :-)
There are problems with dependencies. I also found out it is not easy to
directly set up the environment for gcc or even worse cmake.
I would suggest to directly start writing a package definition (weather
or not it is free), like described here:
https://www.gnu.org/software/guix/manual/guix.html#Building-from-Git
In your case you need the cmake-build-system. Look through the source
code und gnu/packages/*.scm for examples.
When you then execute
./pre-inst-env guix build libfreenect
Guix will correctly prepare the cmake-environment for you.
Probably it will hit errors because you missed arguments or
dependencies, but at least the basic dependencies will be available.
Furthermore, you can keep the build directory under failure ("-K"):
./pre-inst-env guix build -K libfreenect
Then you can examine the build directory under /tmp/guix-build-... for
cmake log/error files.
Hope this helps,
Björn
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2018-02-26 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 20:52 path error Quiliro Ordonez Baca
2018-02-26 20:58 ` Andreas Enge
2018-02-26 21:30 ` Quiliro Ordonez Baca
2018-02-26 21:53 ` Quiliro Ordonez Baca
2018-02-26 22:42 ` 3D scanning Quiliro Ordonez Baca
2018-02-26 23:05 ` Björn Höfling [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
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=20180227000503.192f7560@alma-ubu \
--to=bjoern.hoefling@bjoernhoefling.de \
--cc=help-guix@gnu.org \
--cc=quiliro@riseup.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).