From: Milind Kamble <milind.b.kamble@gmail.com>
To: phodina <phodina@protonmail.com>
Cc: help-guix@gnu.org
Subject: Re: Seeking help to create link to libstdc++.so in /lib64
Date: Wed, 2 Nov 2022 06:59:35 -0500 [thread overview]
Message-ID: <CAJpe+Q+sQcXXKr=b4ZposMz7dhTkpw_xEPmGPmwr2pe04nNVAQ@mail.gmail.com> (raw)
In-Reply-To: <LI3L_oglNCEPYFUb0G2-B7tvd6Wcd5SXtRMbobkwGgEpHNZGZjkK7zozNNN7ThMNjzWMQQN12Srll2McKRRoADn6_dsKx0_hdB-r9PKiTIc=@protonmail.com>
Thanks for responding Petr. Could you elaborate how to compose it with
the outer function?
I tried this
(operating-system ;; other stuff snipped out
(services
(list
(extra-special-file "/lib64/libstdc++.so.6"
(file-append `(,gcc "lib") "/lib/libstdc++.so.6"))
))))
It gives me this error:
In procedure struct-vtable: Wrong type argument in position 1
(expecting struct): (#<package gcc@10.3.0 gnu/packages/gcc.scm:659
7fb670d7d0b0> "lib")
So file-append does not like/expect a list. It expects a package
object for first argument
-Milind
On Tue, Nov 1, 2022 at 4:54 AM phodina <phodina@protonmail.com> wrote:
>
> Hi Milind,
>
>
>
> > If instead of file-append, I use string-append like this:
> > #~(string-append $#gcc:lib "/lib/libstdc++.so.6")
> > it works to the extent that gcc:lib is expanded correctly, but then
> > activate-service.scm script contains
> > (activate-special-files (quote (("/lib64/libstdc++.so.6"
> > (string-append "/gnu/store/6d0pl5khj08j3c2619jnypc8bznspgx8-gcc-10.3.0-lib"
> > "/lib/libstdc++.so.6")))))
> >
> > and which results in an error:
> > wrong type (expecting string): (string-append
> > "/gnu/store//gnu/store/6d0pl5khj08j3c2619jnypc8bznspgx8-gcc-10.3.0.lib"
> > "/lib/libstdc++.so.6")
> >
>
> IMHO you can try the following code instead of the Gexp:
> `(,gcc "lib")
>
> Hope it helps!
>
> ----
> Petr
next prev parent reply other threads:[~2022-11-02 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 3:38 Seeking help to create link to libstdc++.so in /lib64 Milind Kamble
2022-11-01 9:53 ` phodina
2022-11-02 11:59 ` Milind Kamble [this message]
2022-11-10 15:42 ` (
2022-11-10 16:29 ` phodina
2022-11-10 16:37 ` (
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='CAJpe+Q+sQcXXKr=b4ZposMz7dhTkpw_xEPmGPmwr2pe04nNVAQ@mail.gmail.com' \
--to=milind.b.kamble@gmail.com \
--cc=help-guix@gnu.org \
--cc=phodina@protonmail.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.
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).