From: Nicolas Graves via Guix-patches via <guix-patches@gnu.org>
To: 57954@debbugs.gnu.org
Subject: [bug#57954] Some details about why and see if there is no other solution.
Date: Tue, 20 Sep 2022 14:58:52 +0200 [thread overview]
Message-ID: <87wn9ykxrn.fsf@ngraves.fr> (raw)
In-Reply-To: <20220920124010.21646-1-ngraves@ngraves.fr>
I am trying to get a vosk package to work for guix.
The build process is a bit tricky with replaced dependencies etc.
The team from vosk uses a version where they replace fortran by having
both openblas and clapack in libraries (which is incompatible in the
base kaldi configuration, so they have their own fork).
I don't know why exactly the library should be called from another
place, but when compiling kaldi with clapack, I get the following
message (and siblings):
ld: /gnu/store/yvc2w9mg554y6i4frvahjhacj0np9c7s-clapack-3.2.1/lib/liblapack.a(ssptrf.c.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC
I actually does work when recompiling with this flag, but I've also read
that it might make the package a bit slower.
In case it might help to answer, here's where I am for this package,
although not done yet (I still do have to untangle some ffi segmentation
fault issue) :
https://git.sr.ht/~ngraves/dotfiles/tree/main/item/packages/vosk.scm
What is the best option / course of action ?
--
Best regards,
Nicolas Graves
next prev parent reply other threads:[~2022-09-20 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 12:40 [bug#57954] [PATCH] gnu: clapack: Use position-independent code for use as a library Nicolas Graves via Guix-patches via
2022-09-20 12:58 ` Nicolas Graves via Guix-patches via [this message]
2022-09-22 15:48 ` [bug#57954] Some details about why and see if there is no other solution Maxime Devos
2022-09-24 8:37 ` Nicolas Graves via Guix-patches via
2022-09-24 9:46 ` Maxime Devos
2022-09-28 12:19 ` bug#57954: " Nicolas Graves via Guix-patches via
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=87wn9ykxrn.fsf@ngraves.fr \
--to=guix-patches@gnu.org \
--cc=57954@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/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).