<aterius>
Are you still using a LIBRARY_PATH wrapper?
<aterius>
You don't need to do that anymore for native compilation
<ldlework>
aterius: I am using latest commit on emacs overlay and just installing emacsGCC
<ldlework>
aterius: what do you mean?
<aterius>
Oh for awhile for native compilation we had to use a library_path wrapper, but (I think it was antifuchs?) changed it to inject the libraries directly with libgccjit see here: https://github.com/NixOS/nixpkgs/pull/94637/files
<aterius>
(it affected the build process for everything
<aterius>
but that library_path reference stuck out to me
<ldlework>
aterius: so i updated the overlay to the latest github commit, and rebuilt, do i need to do anything else?
<ldlework>
there do seem to be some LIBRARY_PATH mentions in the emacs stacktraces
<aterius>
What nixpkgs checkout are you using?
<aterius>
The overlay uses a lot of the nixpkgs infra
<ldlework>
I am using a channel, and I forgot how to check what commit it is on
selfsymmetric-mu has quit [Ping timeout: 246 seconds]
selfsymmetric-mu has joined #nixos-emacs
srk has joined #nixos-emacs
maddo has joined #nixos-emacs
<maddo>
hello, I've been having problems with emacsGcc, basically it fails to compile on my machine (overlay via home-manager), I'm using a few epkgs, can that be related?
<selfsymmetric-mu>
maddo: I'm not sure in your case, but I know that twice emacsGcc failed to build on my machine. I just fell back to emacsUnstable for a few days and then switched back.
<maddo>
will try, btw is there a way to use telega? TDlib is outdated on 20.09, added the unstable channel and tried using unstable.td to install but it still seems to be the old version
<selfsymmetric-mu>
maddo: I think I may have made a ticket for that, actually...
<selfsymmetric-mu>
Change unstable-2020-10-25 to unstable-2021-01-12, and rev to the latest tdlib revision hash. Then the sha should fail and tell you the correct one. Copy-paste that in and it should be done.
<selfsymmetric-mu>
But yeah…I might if it keeps updating like this then it's not exactly sustainable, right?
<maddo>
master is at 1.7.0, telega's author told that future telega versions will b backported to work on 1.7.0 till new tagged version is out on github
<selfsymmetric-mu>
Ohhhhhhhh
<selfsymmetric-mu>
Okay that's great to hear!
<maddo>
added the channel, used unstable.tdlib in envirorment packages in configuration.nix and I still seem to have the old version
<selfsymmetric-mu>
In the time it took me to fix it I decided to stay with Signal, but it's so nice to know that it will be more of an option in the future.
<maddo>
I want to use signal as well but guess what, nobody in my circle uses it
<maddo>
I either need a better circle or I should just not care ;;
<selfsymmetric-mu>
You might try recommending it to people. You could be surprised.
<selfsymmetric-mu>
I mean I didn't think I had any kind of sway there, but my texts now are 96% Signal.
<selfsymmetric-mu>
I gently badgered people to move our group chats over, and here we are.
<maddo>
brb gonna try
maddo has quit [Remote host closed the connection]
rajivr has quit [Quit: Connection closed for inactivity]
cfinch has quit [Read error: Connection reset by peer]