emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#60039: closed (Update GDAL and NetCDF and include lz4 and openjpeg s


From: GNU bug Tracking System
Subject: bug#60039: closed (Update GDAL and NetCDF and include lz4 and openjpeg support)
Date: Fri, 23 Dec 2022 11:12:01 +0000

Your message dated Fri, 23 Dec 2022 10:58:44 +0000
with message-id <87wn6iv0hk.fsf@kitej>
and subject line Re: [bug#60039] Update GDAL and NetCDF and include lz4 and 
openjpeg support
has caused the debbugs.gnu.org bug report #60039,
regarding Update GDAL and NetCDF and include lz4 and openjpeg support
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
60039: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60039
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: Update GDAL and NetCDF and include lz4 and openjpeg support Date: Tue, 13 Dec 2022 19:00:32 +0100 User-agent: mu4e 1.8.11; emacs 29.0.50
Hello Guix,

this patch series updates the GDAL, Netcdf and libtiff packages. It also
adds support for lz4 and openjpeg to GDAL.

Could you please review it?

Thanks, Roman.

Attachment: 0001-gnu-gdal-Update-to-3.6.0.patch
Description: Text Data

Attachment: 0002-gnu-gdal-Add-support-for-lz4-and-openjpeg.patch
Description: Text Data

Attachment: 0003-gnu-libtiff-Update-to-4.4.0.patch
Description: Text Data

Attachment: 0004-gnu-netcdf-Update-to-4.9.0.patch
Description: Text Data

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message --- Subject: Re: [bug#60039] Update GDAL and NetCDF and include lz4 and openjpeg support Date: Fri, 23 Dec 2022 10:58:44 +0000
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: signature.asc
Description: PGP signature


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]