unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Emmanuel Medernach <emmanuel.medernach@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Help on writing package definitions
Date: Thu, 23 Apr 2020 12:00:11 +0200	[thread overview]
Message-ID: <CAJ3okZ2syxYG6OLgZDURPh60Jy0Uw8NVUMM8=DrykM45Ai+5vg@mail.gmail.com> (raw)
In-Reply-To: <CAC_pKx_L0H_ZLex8d1kM0qEsPrtomvKSTijp6bqGhpDSknGV7g@mail.gmail.com>

Dear,


On Thu, 23 Apr 2020 at 10:29, Emmanuel Medernach
<emmanuel.medernach@gmail.com> wrote:

> - Why not export the license record type from license.scm ? Some project
> has its own license and I cannot create it.

You mean the project's license is not part of this list [1], right?

[1] https://www.gnu.org/licenses/license-list.html


Otherwise, I do not have the answer for your question. :-)


> - I have errors when I try to build with guix that I don't have when I
> build manually. I have a package (asiofi) which depends on another one
> (libfabric) but the build does not find it. Here is my current file
> attached and the command I use:
>
> # guix build -K --load-path=/home/emederna/src/packages -e '(@ (CBM)
> asiofi)'

Does the '#' at the beginning mean that your are running as root?

Well, I find easier 1/ to log in as 'emederna' user and 2/ to run

  guix build -L ~/src/packages asiofi


> CMake Error at test/CMakeLists.txt:9 (add_executable):
>   Target "afi_msg_bw" links to target "OFI::libfabric" but the target was
> not
>   found.  Perhaps a find_package() call is missing for an IMPORTED target,
> or
>   an ALIAS target is missing?

From my understanding, there are 3 "issues":

 a) instead of create a full new package for libfabric, you could
update the Guix one or use 'inherit', e.g., (not tested)

(define-public my-libfabric
  (inherit libfabric
     (version "X.Y")
     (source blablabla)))

 b) missing '#t' to the phase 'add-before'

 c) missing the package 'pkg-config', i.e.,
       #:use-module  (gnu packages pkg-config)
and
    ("pkgconfig" ,pkg-config)
in the list of inputs.


Now, it seems compiling on my machine. :-)


Hope that helps.
simon

  reply	other threads:[~2020-04-23 10:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23  6:32 Help on writing package definitions Emmanuel Medernach
2020-04-23 10:00 ` zimoun [this message]
2020-04-23 12:21   ` Emmanuel Medernach
2020-04-23 14:17     ` zimoun
2020-04-23 16:44 ` Leo Famulari
2020-04-23 17:11   ` zimoun
  -- strict thread matches above, loose matches on Subject: below --
2020-04-23  9:41 Vincent Legoll
2020-04-23 12:09 ` Emmanuel Medernach
2020-04-23 12:17   ` Vincent Legoll

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='CAJ3okZ2syxYG6OLgZDURPh60Jy0Uw8NVUMM8=DrykM45Ai+5vg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=emmanuel.medernach@gmail.com \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).