From: Mehmet Tekman <mtekman89@gmail.com>
To: Mathieu Othacehe <othacehe@gnu.org>
Cc: 67405-done@debbugs.gnu.org
Subject: [bug#67405] [PATCH] Update fftw3
Date: Sun, 26 Nov 2023 20:59:12 +0100 [thread overview]
Message-ID: <CAHHeYzLh5Mg0pAs-vf-MQRpwbz-UqJi6PVtetU1yuEXfp1ez_w@mail.gmail.com> (raw)
In-Reply-To: <87msv0pr5y.fsf@gnu.org>
Hello Mathieu,
I was wondering if you could advise me best on how to handle
this related patch (fftw-cmake):
https://patches.guix-patches.cbaines.net/project/guix-patches/patch/87o7fmu8or.fsf@gmail.com/
It's a direct clone of fftw, but built with cmake-build instead of gnu-build.
The reason is that the gnu-build doesn't generate the required *.cmake
files required in a dependent package (krita):
https://patches.guix-patches.cbaines.net/project/guix-patches/patch/87il5uu5tt.fsf@gmail.com/
The cmake-build provides all the required *.cmake files for the library, but has
none of the CPU-optimisations in the gnu-build.
Do you know how I can proceed with this? Is it bad etiquette to have a package
that is a direct source clone of another, only built differently?
Best,
Mehmet
prev parent reply other threads:[~2023-11-26 20:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 15:59 [bug#67405] [PATCH] Update fftw3 Mehmet Tekman
2023-11-26 13:42 ` bug#67405: " Mathieu Othacehe
2023-11-26 19:59 ` Mehmet Tekman [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHHeYzLh5Mg0pAs-vf-MQRpwbz-UqJi6PVtetU1yuEXfp1ez_w@mail.gmail.com \
--to=mtekman89@gmail.com \
--cc=67405-done@debbugs.gnu.org \
--cc=othacehe@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.
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.