From: Roman Scherer <roman@burningswell.com>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 60039-done@debbugs.gnu.org
Subject: [bug#60039] Update GDAL and NetCDF and include lz4 and openjpeg support
Date: Fri, 23 Dec 2022 12:13:33 +0100 [thread overview]
Message-ID: <CAEc_D29E1zzSv50WZVc9Kn3thF9uAfv2AoZZngb+UYMuX=85Og@mail.gmail.com> (raw)
In-Reply-To: <87wn6iv0hk.fsf@kitej>
[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]
Thank you!
On Fri, Dec 23, 2022, 12:11 Guillaume Le Vaillant <glv@posteo.net> wrote:
> Roman Scherer <roman.scherer@burningswell.com> skribis:
>
> > Hi Guillaume,
> >
> > sorry about that. Here is another patch. The failed dependencies you
> > mentioned are working now. Another reason why netcdf-parallel-openmpi
> > failed was that I changed the build system previously to cmake. I went
> > back to use the original gnu build system. I changed it to cmake
> > initially because I saw that in Arch Linux's PKGBUILD and I remember
> > having had some problems initially. I guess it was related to the tests
> > I now patched.
> >
> > While at the topic. Do we prefer any build system over the other in
> > general in Guix, like cmake vs gnu. Does one have more features than the
> > other (I heard something about cross compilation)?
>
> Usually the best build system is the one that upstream developers use.
> If several equivalent build systems can be used, it depends what works
> best or what is easier in Guix...
>
>
> > And another question. How did you find the failing dependencies in the
> > first place? Did you build all the dependencies of the netcdf packages
> > with --sources=all?
>
> You can find the dependents of a package with:
>
> --8<---------------cut here---------------start------------->8---
> ./pre-inst-env guix refresh -l <package-name>
> --8<---------------cut here---------------end--------------->8---
>
> So you can rebuild all the dependents of a package with something like:
>
> --8<---------------cut here---------------start------------->8---
> ./pre-inst-env guix build $(./pre-inst-env guix refresh -l <package-name>
> | cut -d ':' -f 2)
> --8<---------------cut here---------------end--------------->8---
>
>
> Patch pushed as 66188398c446bdf9ce044fa539536e9b54c28c60 with a complete
> commit message.
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 2427 bytes --]
prev parent reply other threads:[~2022-12-23 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 18:00 [bug#60039] Update GDAL and NetCDF and include lz4 and openjpeg support Roman Scherer
2022-12-20 17:07 ` Guillaume Le Vaillant
2022-12-20 19:10 ` Roman Scherer
2022-12-22 10:41 ` Guillaume Le Vaillant
2022-12-22 19:07 ` Roman Scherer
2022-12-23 10:58 ` bug#60039: " Guillaume Le Vaillant
2022-12-23 11:13 ` Roman Scherer [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
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='CAEc_D29E1zzSv50WZVc9Kn3thF9uAfv2AoZZngb+UYMuX=85Og@mail.gmail.com' \
--to=roman@burningswell.com \
--cc=60039-done@debbugs.gnu.org \
--cc=glv@posteo.net \
/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).