IRC channel logs


back to list of logs

<easbarbosa>hey, ive run into this error w/ environment: cannot open shared object file
<easbarbosa>how to install it? thx
***Kimapr8 is now known as Kimapr
<easbarbosa>cool gcc-toolchain :)
<the_tubular>Is anyone able to help with a guix install acting weird ?
<the_tubular>I'm having trouble booting with UEFI and also with hardware compability
<MysteriousSilver>hi #guix! i tried create a derivation for a package. Running guix build <package> gives `jack: unbound variable`, but i've already loaded the audio module
<MysteriousSilver>Any idea why this happens?
<ecbrown>MysteriousSilver: i don't know the exact term but i think you need to return a "thunk"
<ecbrown>or, define a package and use GUIX_EXTRA_PACKAGES
<MysteriousSilver>'s that?
<ecbrown>one sec
<ecbrown>it's like, you return (my-package)
<ecbrown>at the last line
<ecbrown>but there's another way to do it so that you just build a module and put it in a special directory
<ecbrown>sorry, that's GUIX_PACKAGE_PATH
<MysteriousSilver>no, i am specifying a dependency 'jack' for my package and building that returns `jack: unbound variable`
<ecbrown>oic, sorry, i though you were packaging jack lol
<ecbrown>i dont see jack defined
<ecbrown>i see jack-1 and jack-2
<ecbrown>i also see a jack-select, not sure whether this makes a 'jack'
<ecbrown>well there it is, sorry i just grepped the source, must have a different name than the definition
<MysteriousSilver>so, `guix edit jack` gives jack-1
<ecbrown>what if you call jack-2?
*MysteriousSilver shrugs
<cossidini>what's the difference bewtween --system and --target when using guix build?
<sneek>Welcome back cossidini, you have 1 message!
<sneek>cossidini, efraim says: you need to only have one instance of guix-daemon running at a time. run guix-daemon-work at work and guix-daemon otherwise, but only one at a time.
<vagrantc>cossidini: one cross-compiles and one compiles "natively" (possibly using qemu-user emulation)
<vagrantc>i forget which is which
<cossidini>i see. i dont have that much experience with either. im trying to build guix for arm board but kbd fails to build
<apteryx>am I the only one for whom bash completion sometimes stutters and goes seeking the disc for a long time? especially on file names
<apteryx>(long time being a few second at most)
<vagrantc>apteryx: definitely happens in some cases...
<apteryx>I think it may have to do with checking entries in /gnu/store. For example I was doing something like: tar xf /gnu/store/wy67wq015gj89n1572mj7wjk946fjas7-guile-tarball-pack.tar ~/proj/[TAB] and it paused
<apteryx>if I do 'ls ~/proj/[TAB]' it's quick
<apteryx>so based on the 1st arg which is in the store, perhaps it searches more entry there... doesn't make sense, but that seems to be happening
<apteryx>--with-patch is fun
<bagsbagsbagsderi>guix pull: error: Git error: error inflating zlib stream
<bagsbagsbagsderi>hi I got that error when trying to run `sudo -i guix pull`
<bagsbagsbagsderi>any ideas regarding what might be wrong?
<apteryx>is it reproducible?
<bagsbagsbagsderi>i'm retrying the command now
<bagsbagsbagsderi>yup same error when I run it again
<tissevert>hello guix !
<maddo>hello, I wanted to report that plantUML on guix is using a broken graphviz version according to the faqs. Versions 2.39 to 2.42 (which guix is using) have unexpected behaviour
<maddo> details here. 2.38 and 2.44 do not seem affected (and there is a new plantuml version out too)
<leoprikler>since graphviz is a core package, this won't get "fixed" anytime soon, but would grafting work here?
<leoprikler>also try to check which graphviz package is used in core-updates
<sgibb>Hello, I try to use `guix pack --format=squashfs` to generate a singularity container. For an HPC I need to use slurm commands (`sbatch`, `sinfo`) from within the container. If I use the host slurm commands I got the error `No such file or directory`(e.g. `SINGULARITY_BIND="/usr" singularity run <container> -c '/usr/bin/sinfo'`) but according to `ls` and `cat` the file is there and accessable. Can anybody point me into
<sgibb>the right direction?
<sgibb>(BTW: putting `slurm` into the container results in the error: `slurm_load_partitions: Zero Bytes were transmitted or received`)
<MysteriousSilver>hello, trying to write a package derivation, the configuration fails with 'Could not resolve host:'
<MysteriousSilver>any idea why?
<bricewge>MysteriousSilver: What does "host" return?
<bricewge> Can you share the whole error and/or your package definition?
***xgqtd is now known as xgqt
<MysteriousSilver>bricewge: my package uses the cmake build system, which installs an dependency itself
<MysteriousSilver>here's the error message:
<bricewge>Oh that's the build code (cmake and co) trying to access remote ressource
<bricewge>There is no network access in the build environment
<bricewge>You need to disable the access to the remote resource and provide it through guix
<MysteriousSilver>there's no such package in the guix.git repository
<MysteriousSilver>so i'd have to define one myself?
<bricewge>Hum, that's 4chan's Audacity, did you tried inheriting from our current Audacity?
<bricewge>If it did not changed too much since the fork it should be straightforward
<MysteriousSilver>i think the current audacity uses conan
<MysteriousSilver>which has several absent dependancies in guix
<pazho>Hi, could anyone here correct a small error in the documentation (not worth a bug report): /doc/guix.texi line 9196 should not have '-symlink' at the end.
<bricewge>« Conan, the C/C++ Package Manager » oh, a new one
<bricewge>MysteriousSilver: Since conan is a package manager, you should try to do without it when building your package and give it its dependies from guix.
<bricewge>wxwidgets (from your error) is already packaged in guix if you need audacity's fork change the source to be Audacity's
<MysteriousSilver>i'll try that
<Radvendii>Hey all, I'm a long-time Nix user just starting to dip a toe into Guix.
<MysteriousSilver>Hello Radvendii! o/
<Radvendii>I've run into a few issues that boil down to "there's this thing I'm used to doing X way in Nix, how do I do that in Guix? Is that even the right way to go about it in Guix?" I haven't been able to find a general guide for migrating Nix -> Guix online. Does anyone know of one that I've missed?
<Radvendii>Hi MysteriousSilver! :)
<Radvendii>The most recent example is: with Nix, there's a common pattern of having a `default.nix` file at the root of a project, which packages that project. It then pulls in the current directory as the source with `src = ./.`. With Guix, I only see tutorials for packaging preexisting projects and pulling them in using a URL. Is having the package
<Radvendii>definition bundled with the project just not done? If so, how do I use the current directory as source? I tried `(url "file://.")` and variations thereof in the `(source (origin ...))` field
<tissevert>hi Radvendii !
<tissevert>I've had exactly the same issues when I came to Guix (although I had hardly touched nix beforehand, but that default.nix pattern was handy and had sticked to me)
<tissevert>I'm not sure whether it's the right thing to do, but these days I tend to have a single file for all my custom / local / still dirty don't touch packages
<tissevert>that I let guix know of with the GUIX_PACKAGE_PATH variable (I've seen also the -L option of many guix commands do achieve the same thing)
<tissevert>in those packages, (uri …) takes simply the file without any scheme
<tissevert>like this: (uri "/home/tissevert/Software/somePackage")
<efraim>you don't need 'file:///' as a prefix?
<tissevert>and I fill the hash with 0s like this (sha256 (base32 "000000…0"))
<tissevert>efraim: should I ? this has always worked without (I was precisely using it when I noticed Radvendii's messages, I'm drafting a grammar for a particular kind of text in haskell)
<tissevert>hey ! it works with it ! : ) cool
<tissevert>I had never tried
<Radvendii>It seems to only take absolute path though? (no relative)
<Radvendii>Is that right?
<tissevert>yes, that I can confirm
<tissevert>I had tried with relative path from my home
<tissevert>with including ~
<tissevert>and even ~tissevert
<tissevert>but nothing was working, which is why I included /home/tissevert in my example above
<tissevert>maybe something else would work (relative from the .scm file itself ?) or other formats have been supported since ? but this only I know
<Radvendii>okay, thanks. So I guess it's not really possible to include the package with the project
<apteryx>don't we have a place that says our packaging policy must abide to the GNU FSDG in the manual?
<tissevert>Radvendii: what do you mean ? having a standalone .scm file in the repos directly ?
<Radvendii>Yeah, exactly. Like the way people use `default.nix` (or now increasingly `flake.nix`)
<tissevert>hmmmm well I think it'd still be possible, maybe just not the more convenient
<Radvendii>apteryx: how does that impact the conversation? I'm not super familiar with FSDG, but I just looked it up and it seems like it would still be compliant
<tissevert>there are ways to source a particular file
<tissevert>it just did seem not that easy to poor noob me
<Radvendii>tissevert: but it would have to be relative to the current directory / .scm file, since you don't know where it's going to be installed on the user's machine
<Radvendii>yeah, that's fair. I also couldn't figure it out. Okay, I just have to change the way I'm thinking about packaging for Guix I guess
<tissevert>in particular, I remember something about not being the same option for guix install / guix environment or guix build or something
<southerntofu>Radvendii: hello! i'm not sure it's a good approach because i'm pretty new to guix myself, but i've done it like that for a rust app:
<southerntofu>guix.scm is the equivalent of your default.nix, i linked in that PR a talk that explains it if you're interested :)
<southerntofu>(source (local-file %source-dir ..........
<tissevert>ahh I remember now: it was the need to «return» the package as a final «instruction» in the file that made me uneasy
<tissevert>thanks for your example southerntofu !!
<Radvendii>Ah hah! Thank you so much southerntofu that's exactly what I was looking for. I'll also watch the talk you link, since it seems relevant
<southerntofu>yea also i haven't found how to make it so you can install the package and/or make a one-off dev environment (using a manifest) from the same file, which would be practical
<southerntofu>but then again it's my first ever guix package so don't take me for example :P :P
<tissevert>which is why I use a «package» defined outside in central file
<tissevert>it lets me enter environments where I can see the package I'm developing and play with any change I've just made
<southerntofu>do you have an example tissevert ? i'm not sure i understand :)
<tissevert>…no because it's still very dirty and I haven't put anything online but it's basically the same format as your example minus the final «aparte» statement
<tissevert>I'll upload some on a paste bin
<tissevert>I've just wrapped up something for the zettelkasten I use this morning
<tissevert>but haven't published the «package» yet
<southerntofu>soooo each package declares its own variables for package declaration and manifest, but without returning them, and then you have a "central" file that imports those package files to expose them?
<tissevert>hmmm I haven't thought of making imports
<tissevert>no, all the declarations are in the central file
<tissevert>(although in my sample I've removed the only other one I have for now)
<tissevert>so, lot of redundant imports because not everything is used here
<tissevert>also, I haven't even filled the description : (
<tissevert>sorry for the messy example
<southerntofu>so then how do you make an environment from that?
<southerntofu>(also pastebin has nasty privacy policy, don't hesitate to use another paste server, or even a null pointer upload service)
<tissevert>that file is placed in ~/GUIX/gnu/packages/parade.scm
<tissevert>I set GUIX_PACKAGE_PATH=/home/tissevert/GUIX
<tissevert>(in my bash profile)
<southerntofu>for example curl -F'file=@path/to/file'
<southerntofu>ah ok so it's like a local guix distro :P
<tissevert>thank you so much for this alternative ! I'm always looking for a better alternative
<southerntofu>0x0 runs nullpointer software which can easily be selfhosted! :)
<tissevert>(yeah, I know pastebin is problematic, but anytime I need to upload something I fail to find any other solution that doesn't require an account)
<tissevert>hmmm I should make a 0x0 instance… ok, on the TODO ; ) thanks again
<tissevert>and so well yeah like you say it's like a local distro
<Radvendii>Oh that's good to know about. I've been using
<tissevert>I can safely forget it's not in the official repos
<Radvendii>but self-hosting is a much better solution
<tissevert>I can guix search it, guix build it, guix environment and so on
<tissevert>without even having to care about the file
<southerntofu>note that apparently blocks uploads from tor (at least from my exit node) but other instances work fine
<southerntofu>here's the script i use for upload:
<southerntofu>so i do [-t] FILE
<tissevert>I don't target files, I target a «proper» (huhummm yeah well let's not be to strict about it for now but I mean at least formally it's a proper) package
<southerntofu>yes i can see that tissevert, but so can it be used on top of the existing guix setup? GUIX_PACKAGE_PATH won't prevent reading "real" guix packages? or you have those as well in your ~/GUIX/ ?
<tissevert>no, no of course, it adds but doesn't replace
<tissevert>I can still see any official package, I don't have to disable that all the time
<tissevert>which is why it's convenient enough for me, and though I'm sure a cleaner setup must exist, I haven't spent anytime looking for it lately
<southerntofu>well i'm interested in this guix.scm pattern personally :)
<tissevert>(plus, the last thing I did with nix before coming to guix was publish a «repos» of my package, which already had that central structure, so I intend to do just the same with guix and that seems just fine to me)
<southerntofu>i like it that you can git clone a project, and suddenly you have all you need to build a one-off environment from there
<tissevert>yeah, I must say it was one of the only things I liked in nix and I miss it
<southerntofu> <-- maybe you'll enjoy this talk then
<tissevert>thanks for the link !
<tissevert>I'll watch it during my next break : )
<Radvendii>Hah, tissevert this might be off-topic for this channel, but I'm curious what you didn't like about Nix
<southerntofu>Radvendii: personal opinion here as someone who has used guix and nix but neither extensively: nix has two different naming schemes for packages and that is highly confusing, also when used on foreign distros GUI doesn't work (need to wrap with nixGL).. also i'm not a fan of nix as a programming language but that's less of a reason. the two first reasons mentioned is why i can't recommend nix to less
<southerntofu>technical friends
<Radvendii>ah, yeah, i've never really used it outside of NixOS, so I can't speak to that one. What's the two different naming schemes?
<southerntofu>but i do wish guix was more strongly-typed and had proper error messages :-/
<southerntofu>for example nixpkgs.firefox vs nixos.firefox
<Radvendii>oh, i wouldn't envy Nix's error messages XD
<southerntofu>the packages aren't named the same depending on where from you use nix.. that's really stupid but i know for sure it's a good enough reason i can't put nix in the hands of non-developers who won't RTFM :P
<Radvendii>oh yeah, I don't really understand what's going on with `nixpkgs.` and `nixos.`. I just put all the packages in my `configuration.nix` (or home-manager now, actually)
<southerntofu>Radvendii: oh nix errors aren't much better, but for example with guix i was having wrong import module statements and suddenly my build was outputing NOTHING and failing silently... as someone who is used to rust programming language with the most helpful error messages i've ever meant, that was a frustrating experience ;)
<Radvendii>Oof. I think I got that at some point too. Yeah, I would love to see Nix/Guix get some helpful error messages
<Radvendii>Half the time the error message doesn't even reference the file you edited
<Radvendii>anywhere in the call stack
<southerntofu>yes... that's the problem with dynamic typing where everything overrides everything until the runtime doesn't know who produced what result :P
<Radvendii>mm yeah
<Radvendii>I'm wondering if nickel will do a better job with this
<Radvendii>it's got much stronger typing
<Radvendii>Oh wait, you mentioned graphics. Maybe you know how to get this working. I tried using `("opengl" ,mesa)` in the inputs like I saw in some packages, but pkg-config can't find it.
<Radvendii>I tried with `("libglvnd" ,libglvnd)`, and that compiled, but everything shows up black
<tissevert>Radvendii: do my direct messages answer your question a bit ?
<Radvendii>Oh, I didn't see that. Will look now
<tissevert>well I hope it worked
<tissevert>I didn't want to talk about things not related to Guix on this chan
<roptat>hi guix!
<tissevert>hey roptat !
<roptat>how are you?
<Radvendii>@roptat o/
<tissevert>good ! thanks, I haven't been much around lately and I have litterally over 1000 unread email on my guix-patch box ^^' but it's good to be around a bit
<tissevert>how about you ?
<roptat>doing well :)
<roptat>I try to keep my inbox clean, which means I sometimes miss messages ^^'
<roptat>haven't been as active as I wanted to lately, but I'm trying to keep up with ocaml and java patches at least
<tissevert>that's funny because the next two packages I'm gonna need are one in ocaml and one in java : )
<roptat>then I'll probably review your patches :)
<tissevert>ohhh no it's really nothing like that, I'm far from even having an ugly draft locally, so it'll be quite some time before I submit patches for review, if I ever manage to do so
<roptat>oh, then good luck with these packages :)
<tissevert>it's «open source», but each time I try to take a glimpse I forget where it is and can browse for hours to no avail, because all that's easily accessibly from their front page is a link to download it for ubuntu
<tissevert>(«see ? of course it's a free software, we packaged it for Linux !»…)
<roptat>which software is it?
<tissevert>hmmmm can I DM you ? ^^
<dstolfa>hmm... has anyone noticed that guix system runs about 3 times as hot on some laptops than other distros do?
<dstolfa>does anyone know how to fix it?
<dstolfa>i just installed fedora just to test it on my laptop, and it went from 70-80c down to 40
<dstolfa>and this is when not under load
<dstolfa>under load it approaches 100c on guix for some reason
<dstolfa>i assume this is because something is running at full power when it really shouldn't be, and this was with tlp and thermald enabled
<tissevert>dstolfa: haven't observed that no, does it do the same with trisquel ?
<dstolfa>tissevert: it doesn't, it's only guix system that behaves weirdly
<dstolfa>this is a dell precision 5550
<dstolfa>i'm really confused as to what's causing it
<tissevert>: / I have no idea
<roptat>never noticed that either
<dstolfa>i assume it's an issue with only certain laptops, or maybe it was something related to my configuration, i really don't know
<dstolfa>roptat: do you run tlp/thermald on your laptop?
<dstolfa>my configuration was pretty straightforward except for tlp/thermald being enabled
<roptat>if it's not part of the default services, then no
<roptat>maybe my laptop is really good at dissipating heat
<dstolfa>heh, maybe, this is one of those "thin" laptops that is terrible at it, but it just doesn't heat up nearly as much on fedora
<dstolfa>i really don't know what causes the issues
<dstolfa>just to rule out guix's version of gnome... roptat, do you use gnome? :)
<roptat>ah, no
<roptat>I even kill gdm as soon as I log in
<roptat>maybe it's not needed anymore, but it used to have a memory leak
<dstolfa>hmm, i wonder if it's caused by guix's gnome verison. it wouldn't be the first time that gnome was heating up my laptop to insane amounts due to some bugs
<dstolfa>i'll need to troubleshoot this at some point when i have time
<Radvendii>Have you tried disabling tlp/thermald? Maybe there's some edge case where they're actually *causing* problems
<dstolfa>Radvendii: i have, but it didn't improve much :/
<Radvendii>Ah, well it was worth a shot
<podiki[m]>hi guixers
<podiki[m]>is there anything in the manual on copyright conventions for patches? is it customary to add/update on any file touched by a patch?
<podiki[m]>(patch submission I mean, not a patch in a build phase)
<dstolfa>podiki[m]: i don't think it really matters all that much, i usually do it if i remember, but i often don't :D
<dstolfa>guix is licensed under GPLv3+ and it's copyright by a lot of people, so it's safe to say that the license won't be changing
<dstolfa>if you want to add your copyright, do it, but i wouldn't worry about it too much if you forget
<apteryx>podiki[m]: practices follows basic copyright "rules"; for example adding or changing fewer than 10 lines of code is not copyrightable.
<apteryx>removed lines are also note copyrightable ;-)
<jackhill>I don't think copyright (at least where I live in the USA) is so cut and try, that we can have a number of line cutoff, but certainly non-creative changes (type fix, hash update) aren't copyrightable, but I am not a lawyer and this isn't legal advice
<danrobi70>Hello. I've asked in #emacs and in #exwm and nothing I've worked. Im running exwm and binding other-window to new keybind doesnt work in a buffer with external apps. Like firefox, mpv etc. It does work when its a buffer with emacs stuff in it. If I bind for example "C-x w" that works with every buffers. But if I bind "<s-right>" it doesnt works with the buffers with external apps in it. Why is that?
<bricewge>podiki: Yes, you should put your copyright (even of it doesn't apply on your juridiction) on each file where you do non trivial modifications
<bricewge>s/even of/even if/
<danrobi70>well, "<s-right>" does work with every buffers without the (exwm-enable) in my emacs init file.
<brettgilio>We should add stumpwm to the installer
<karthik[m]>i am trying to remove guix package manager from debian host. the `/gnu` dir is not getting deleted even with sudo. any help please
<MichaelRaskin>Is it mounted?
<podiki[m]>probably need to stop the `guix-daemon.service`
<podiki[m]>Brett Gilio: yes, more stump!
<drakonis>ah nice, 5.13 is in
<dstolfa>lfam: hey. do you have an idea of why guix system on my laptop would be running twice as hot as fedora/trisquel do?
<lfam>What do you mean dstolfa?
<dstolfa>well, my idle temperature on the laptop with guix system is 70-80c (under load goes up to 100 and i have to kill things), whereas fedora is on 40c idle and under load it's on 60-70 at most
<dstolfa>tlp/thermald made no difference
<dstolfa>cpu frequencies, at least according to cpupower are being adjusted accordingly, but it's still running crazy hot
<lfam>Does it seem to idle at the same rate? Like, is the system load the same at "idle"?
<dstolfa>yeah, it's approximately the same
<drakonis>check if there's any boot flag magic going on here
<lfam>Could be
<lfam>Also could be the linux-libre kernel disabling something useful for your hardware
<drakonis>i've inspected the kernel settings and it has thermal throttling
<drakonis>yes it has some things disabled
<drakonis>multiple thermal settings
<lfam>I would try using the Fedora kernel
<dstolfa>yeah, i'll give that a shot when i get the chance to mess with it. i don't think it's linux-libre itself as trisquel was fine
<dstolfa>it must be some option that my laptop is unhappy with (precision 5550)
<lfam>Maybe our kernel is configured incorrectly
<dstolfa>well, my desktop system is having normal temperatures, but my laptop is just burning up for some reason
<drakonis>acpi woes?
<lfam>I would suggest comparing Guix System to Trisquel. Fedora is wayyy more sophisticated and it will be hard to narrow down the differences
<dstolfa>sounds reasonable, i'll give that a shot when i get the time to do it. ENOTIME at the moment, but at least i'm getting to test guix on fedora in the meantime on my laptop :P
<dstolfa>(it works well, but SELinux is a problem initially)
<t0nt0n>Hi, I'm on guix system and git submodule fails with '/home/ton/.guix-profile/libexec/git-core/git-sh-setup: line 46: /home/ton/.guix-profile/libexec/git-core:/home/ton/.guix-profile/libexec/git-core/git-sh-i18n: No such file or directory' Anyone know how to get git submodule working?
<maximed>t0nt0n: Curiously, .guix-profile/libexec/git-core/git-sh-i18n exists on my system
<lfam>t0nt0n: If you just installed Git, you might need to re-login. For example, `bash --login`
<maximed>t0nt0n: What's $GIT_EXEC_PATH?
<maximed>I wonder if it contains a :. I.e., $GIT_EXEC_PATH consists of two directories
<maximed>if so, maybe "git-sh-setup" doesn't support multiple-directory $GIT_EXEC_PATH
<t0nt0n>ah, could be, the file exists here as well. I'll check the path and login
<t0nt0n>hmm, so $GIT_EXEC_PATH contained the same path twice, I reset it to just one and then it works\
<t0nt0n>thanks. Not sure how this happened, yet works now
<lfam>These variables are set at login time so, in general, you need to login after installing the package
<lfam>Or, start a login shell
<maximed>I wonder how that happened, as GIT_EXEC_PATH has separator #f (see "guix edit git")
<lfam>It's weird
<t0nt0n>Right. :) A project I'm trying to build says it needs OpenGL::GLX I thought they were in mesa or mesa-headers, but it seems like it's not. Anyone know where opengl glx is??
<lfam>Maybe mesa-utils
<t0nt0n>ah, could be, will try :)
<t0nt0n>nope, hmm.
<podiki[m]>Last I see on matrix too. It got out of sync in the past too
<brettgilio>Can confirm
<brettgilio>What is the fix?
<roptat>the source seems to be mesa, maybe we don't build it?
<roptat>I see in debian for instance
<hawthorn>hi, hoping someone can help me as i'm not the best with scheme. i'm trying to append an option to the config file guix generates for the bluetooth service. i'd rather not just feed it a local file that has the right options, but have them contained in config.scm somehow. obviously i'm having a little trouble. here are the relevant parts of my config.scm:
<hawthorn>as it is, guix is complaining about a field specifier, but i thought the desktop service module contains bluetooth-service-type, so i'm not quite sure what's going on: /etc/config.scm:44:1: error: (modify-services %desktop-services (bluetooth-service-type config => (bluetooth-configuration (inherit config) (string-append "MultiProfile = multiple\n" config)))): invalid field specifier
<maximed>sneek: later tell t0nt0n: OpenGL::GLX doesn't like C code. What language is this? Maybe C++ or Perl? Maybe you need to use some language-specific bindings
<tophullyte>is there a command or a file where I can look at currently available services? I'm wanting to enable pipewire in my system
<maximed>tophullyte: "sudo herd status"
<maximed>and "guix system search ..." & reading the manual to find new things
<tophullyte>oki, thank you
<podiki[m]>libglvnd will have libGLX (not sure if that will be the one you want exactly)
<podiki[m]>and maybe for the mesa version need to build with libglvnd (ongoing discussion on that btw)
<apteryx>podiki[m]: do you know which commits implemented libglvnd in Nix
<apteryx>or rather, integrated
<apteryx>this one looks interesting:
<podiki[m]>apteryx: sorry, I don't. Perhaps check the IRC logs if someone mentioned it before?
<podiki[m]>there's also nixgl, for how they worked on gl on foreign distro:
<apteryx>this looks useful too:, especially the line with the comment "# FHS paths are added so that non-NixOS applications can find vendor files."
<apteryx>so that libglvnd would be able to find and use the system on foreign distributions
<podiki[m]>doing some git blame, libglvnd was added back here maybe? (but not sure how they used it exactly)
<podiki[m]>apteryx: right, need to use host system on foreign distro
<podiki[m]>i know irfus has played around more with libglvnd. there's discussion on the mesa patch, though I advocated for doing that in a separate patch series (some packages need modfications to find libGL when it comes from libglvnd)
<podiki[m]>building mesa with libglvnd and getting descendents to build I think is not bad, but I'm still not sure if more is needed so that libglvnd does what you want (sending at runtime to vendor libgl)