all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "(" <paren@disroot.org>
To: "Kyle Andrews" <kyle@posteo.net>,
	"Simon Tournier" <zimon.toutoune@gmail.com>
Cc: "help-guix" <help-guix@gnu.org>
Subject: Re: How to copy a file to the package /bin folder using the r-build-system?
Date: Sun, 09 Apr 2023 10:36:50 +0100	[thread overview]
Message-ID: <CRS4GW442096.1W3MVPJHGD6NC@guix-framework> (raw)
In-Reply-To: <87sfd9wv7o.fsf@posteo.net>

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

Heya,

On Sun Apr 9, 2023 at 4:15 AM BST, Kyle Andrews wrote:
> >             (lambda _
> >               (mkdir (string-append #$output "/bin"))
> >               (copy-file "inst/bin/r"
> >                          (string-append #$output "/bin/r")))
>
> This perfect makes sense now and is much more concise.

Actually, you can even do:

```
(lambda _
  (install-file "inst/bin/r"
                (string-append #$output "/bin")))
```

> ```
> $ guix build -L dev r-littler
> ...
> ld: cannot find -lz
> collect2: error: ld returned 1 exit status
> ...
> ```
>
> I know I have seen that error before, but I thought it was fixed by importing compression, prefixing (guix licenses) to prevent a namespace collision, and including zlib in the package inputs.

I think (!) you also need to import (gnu packages pkg-config) and add
PKG-CONFIG to NATIVE-INPUTS.

    -- (

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2023-04-09  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-31 23:21 How to copy a file to the package /bin folder using the r-build-system? Kyle Andrews
2023-04-07 16:07 ` Simon Tournier
2023-04-09  3:15   ` Kyle Andrews
2023-04-09  9:36     ` ( [this message]
2023-04-09 12:54       ` Kyle Andrews

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=CRS4GW442096.1W3MVPJHGD6NC@guix-framework \
    --to=paren@disroot.org \
    --cc=help-guix@gnu.org \
    --cc=kyle@posteo.net \
    --cc=zimon.toutoune@gmail.com \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.