bug#57116: cling: missing some system header files
On 03-09-2022 11:43, zimoun wrote: Hi, On Sat, 03 Sep 2022 at 00:25, Maxim Cournoyer wrote: Should we close it as 'notabug', or persist with the attempt to wrap the cling binary with the include paths required to ease its setup? From my understanding about what cling is, we have a similar issue with some others packages. Bigloo does not work out of the box [1]: --8<---cut here---start->8--- $ guix shell -C bigloo libunistring gcc-toolchain libgc pcre \ -- bigloo /tmp/myfile.scm --8<---cut here---end--->8--- Idem for ghc (Haskell) which requires gcc-toolchain. And I proposed [2] to have -toolchain for a ready-to-use X compiling toolsuite where could be cling, ghc, bigloo, etc. For instance, Debian has haskell-platform which includes all a regular user needs for a regular Haskell development setup. And we already provide gcc-toolchain or clang-toolchain, or even gfortan-toolcahin, gdc-toolchain, piet-toolchain, etc. Therefore, we could also have the package cling-toolchain propagating all the required packages that we currently have to manually specify i.e. gcc-toolchain. WDYT? 1: https://yhetil.org/guix/878rp3bs1a@gmail.com 2: https://yhetil.org/guix/caj3okz0i0djqmzgj9wwzdc2tkc8wetzxqw46kh+vq9zkbgb...@mail.gmail.com I do not see any problems with a X-toolchain (with X=cling,ghc,bigloo, ...) and they appear to be convenient. I'd say, go for it. Greetings, Maxime. OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
bug#57559: guix pull fails on http status code 503
On 03-09-2022 13:21, André A. Gomes wrote: Hi Guix, --8<---cut here---start->8--- $ guix pull Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'... guix pull: error: Git error: unexpected http status code: 503 --8<---cut here---end--->8--- It seems reasonable that if a certain channel isn't available, it should be possible to ignore it and proceed. Thanks. More concretely: * if all channels are available --> ok, keep status quo * if no channels are available --> error, keep status quo * if some but not all channels are available, and there is at least one updated channel --> log the missing channels, and update the channels that _are_ available (but don't 'ignore' the missing channels by removing them!). * if some but not all channels are available, and none of the available channels were updated --> bail out, no progress was made and this might be due to lack of connectivity instead of lack of updates. ? Technically, your message can be interpreted as: if I only have a single channel, the Guix channel, and it isn't available, it should be possible to ignore it and proceed. (Proceed with what? It's the only channel, what is there to proceed with.) To actually implement this, we need to be precise. Greetings, Maxime OpenPGP_0x49E3EE22191725EE.asc Description: OpenPGP public key OpenPGP_signature Description: OpenPGP digital signature
bug#57559: guix pull fails on http status code 503
Hi Guix, --8<---cut here---start->8--- $ guix pull Updating channel 'nonguix' from Git repository at 'https://gitlab.com/nonguix/nonguix'... guix pull: error: Git error: unexpected http status code: 503 --8<---cut here---end--->8--- It seems reasonable that if a certain channel isn't available, it should be possible to ignore it and proceed. Thanks. -- André A. Gomes "You cannot even find the ruins..."
bug#57116: cling: missing some system header files
Hi, On Sat, 03 Sep 2022 at 00:25, Maxim Cournoyer wrote: > Should we close it as 'notabug', or persist with the attempt to wrap the > cling binary with the include paths required to ease its setup? >From my understanding about what cling is, we have a similar issue with some others packages. Bigloo does not work out of the box [1]: --8<---cut here---start->8--- $ guix shell -C bigloo libunistring gcc-toolchain libgc pcre \ -- bigloo /tmp/myfile.scm --8<---cut here---end--->8--- Idem for ghc (Haskell) which requires gcc-toolchain. And I proposed [2] to have -toolchain for a ready-to-use X compiling toolsuite where could be cling, ghc, bigloo, etc. For instance, Debian has haskell-platform which includes all a regular user needs for a regular Haskell development setup. And we already provide gcc-toolchain or clang-toolchain, or even gfortan-toolcahin, gdc-toolchain, piet-toolchain, etc. Therefore, we could also have the package cling-toolchain propagating all the required packages that we currently have to manually specify i.e. gcc-toolchain. WDYT? 1: https://yhetil.org/guix/878rp3bs1a@gmail.com 2: https://yhetil.org/guix/caj3okz0i0djqmzgj9wwzdc2tkc8wetzxqw46kh+vq9zkbgb...@mail.gmail.com Cheers, simon
