Re: [Telegram-Desktop]: Help with packaging

Hello Guix! While building 'tdesktop', I get this error: https://paste.debian.net/1180280/ Any ideas? Regards, RG.

Re: Staging branch [i686]

mesa has failed to build for i686-linux on the staging branch, but there is no build log for this failure: -- builder for `/gnu/store/isx9ra95v8gw3fqgrvz62cwrlzl5s5y7-mesa-20.2.4' failed previously (cached) build of /gnu/store/26f51p9y1glpal0ik84qsyy5z7nqhc6w-mesa-20.2.4.drv failed Could not

Re: [Telegram-Desktop]: Help with packaging

Hi Mark and Ricardo! It's more appropriate to use 'for-each' here. 'map' collects all of the results into a list and returns that list, which is not needed here, and is slightly less readable. Also, the second argument to 'find-files' is optional; omitting it does what's needed more efficientl

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Danny Milosavljevic writes: Hi Danny, > On Fri, 8 Jan 2021 19:56:19 +0100 > Danny Milosavljevic wrote: > >> The CI on nanana is currently building and running the tests. >> >> I'm curious what it will say. > > Tests succeeded. > > Pushed to mes on savannah as commit 10c38e112f177bc0b01ecf107fff

Re: [Telegram-Desktop]: Help with packaging

Hi Mark, > It's more appropriate to use 'for-each' here. 'map' collects all of the > results into a list and returns that list, which is not needed here, and > is slightly less readable. Also, the second argument to 'find-files' is > optional; omitting it does what's needed more efficiently.

Re: [Telegram-Desktop]: Help with packaging

Hi, Ricardo Wurmus writes: > Because you are fetching from git and the git checkout is not writable > You need a build phase like this: > > --8<---cut here---start->8--- > (add-after 'unpack 'make-writable >(lambda _ > (map ma

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi Janneke, On Fri, 8 Jan 2021 19:56:19 +0100 Danny Milosavljevic wrote: > The CI on nanana is currently building and running the tests. > > I'm curious what it will say. Tests succeeded. Pushed to mes on savannah as commit 10c38e112f177bc0b01ecf107d193e4c6b13 ("wip" branch). pgpVlyVc2X

Re: Cuirass logo - artwork.

Hey :) ‐‐‐ Original Message ‐‐‐ On Friday, January 8, 2021 9:31 AM, Mathieu Othacehe wrote: [...] > I think it would be nice to give the project a nice logo that could be > displayed on the web interface, and maybe on an hypothetical project > page. I'll give it a try. I'll let you kn

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi Janneke, On Fri, 08 Jan 2021 17:15:24 +0100 Jan Nieuwenhuizen wrote: > > +/* TODO: On armhf gcc, max_align_t is 16 Byte big instead. Use that? */ > > + > > +typedef double max_align_t; > > + > > #endif // ! SYSTEM_LIBC > > Is this something you can get more info on, or do we just try it

Re: Snapper DBus woes

Can you share with us the full error messages you got? And a more full description of what you tried? On Thu, Jan 7, 2021, at 20:16, raingloom wrote: > Hiya folks. > > I'm trying to finish up that Snapper package that Pierre Neidhardt > abandoned and am also running into DBus issues. > Could som

Re: Cuirass logo - artwork.

On 08.01.21 10:31, Mathieu Othacehe wrote:> I think it would be nice to give the project a nice logo that could be displayed on the web interface, and maybe on an hypothetical project page. It would be, so we can have a favicon :) And I can find my cuirass server better in the forest of browser

Re: Cuirass logo - artwork.

Hello Pierre, > - Why is it called "Cuirass"? :p No idea, you would have to ask Mathieu Lirzin about it! > - Why the move to PostgreSQL? At first I thought that all the performance issues we had were caused by unoptimized SQL queries. Turns out it was only half of the problem. As we have mul

Re: Guile 2.0 in make-bootstrap.scm

Hi all, Jan Nieuwenhuizen writes: >> What’s surprising is that >> does use >> 2.2. > > Oh, that's weird. Well, we used gule-2.2 until almost the very last > moment, I remember. I am cc'ing Timothy, as he helped make the > guile-2.0 b

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Danny Milosavljevic writes: Hi Danny, > I propose to, instead, change mes libc to align stuff malloc returns like > this: > > That should fix it. That's great; I'd like to go test this. Would you like to push to "wip" when you're ready? > diff --git a/include/stddef.h b/include/stddef.h > ind

Re: [Tinycc-devel] [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Danny Milosavljevic writes: Hi Danny, Grishka! > On Fri, 08 Jan 2021 08:16:29 +0100 > grischka wrote: > >> But no such thing happens in this case. The 'ptr' in init_putv() >> comes from >> >> ptr = sec->data + c; >> >> and it seems that if tcc is doing the right thing then 'c' cannot

Re: [Tinycc-devel] [bootstrappable] Re: Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

On 2021-01-08 13:36:26 +, Orians, Jeremiah (DTMB) wrote: > > If so, is libc malloc supposed to ensure alignment of allocated memory? > > According to https://man7.org/linux/man-pages/man3/malloc.3.html yes. > > @Janneke: So our mes libc malloc should be aligning the stuff--but it's not > > doi

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi Janneke, I propose to, instead, change mes libc to align stuff malloc returns like this: That should fix it. diff --git a/include/stddef.h b/include/stddef.h index a597c9bb..a682d726 100644 --- a/include/stddef.h +++ b/include/stddef.h @@ -37,6 +37,10 @@ #endif // !__MESC__ #endif // offset

Snapper DBus woes

Hiya folks. I'm trying to finish up that Snapper package that Pierre Neidhardt abandoned and am also running into DBus issues. Could someone who knows DBus look into it? I really think we should get this package working on Guix sooner rather than later, because right now there is no way to protect

Re: [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi Janneke, On Fri, 08 Jan 2021 07:25:52 +0100 Jan Nieuwenhuizen wrote: > > Alignment could be disabled on the CPU > > > > > > https://developer.arm.com/documentation/ddi0464/f/system-control/register-descriptions/system-control-register > > > > but I don't think EABI wants that. > > Hmm,

Wikidata, Guix and the Free Software DIrectory [was: Re: [ELPA] New package: repology.el]

On 1/7/21 2:49 PM, Richard Stallman wrote: > I see two ways we could possibly manage to use repology.org in the > Free World. > > * Find a way to distinguish free from nonfree packages. I see two > ideas One is to snarf the lists of free packages from Debian and > Parabola. Another is to see if

RE: [bootstrappable] Re: [Tinycc-devel] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

> If so, is libc malloc supposed to ensure alignment of allocated memory? > According to https://man7.org/linux/man-pages/man3/malloc.3.html yes. > @Janneke: So our mes libc malloc should be aligning the stuff--but it's not > doing it. So it's a bug in our libc. Looks like you'll have to waste 3

Re: [Tinycc-devel] [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Hi grischka, Hi Janneke, On Fri, 08 Jan 2021 08:16:29 +0100 grischka wrote: > But no such thing happens in this case. The 'ptr' in init_putv() > comes from > > ptr = sec->data + c; > > and it seems that if tcc is doing the right thing then 'c' cannot > be misaligned, and if malloc/re

Re: [Tinycc-devel] [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

> Jan Nieuwenhuizen wrote: Hello Arnold! >> to the gawk-mesbot0 recipe also fixes "inc.awk". The pre >> increment/decrement code looks like this: >> >> --8<---cut here---start->8--- >> *lhs = make_number(lval + >> (tre

Re: [Tinycc-devel] [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Jan Nieuwenhuizen wrote: > to the gawk-mesbot0 recipe also fixes "inc.awk". The pre > increment/decrement code looks like this: > > --8<---cut here---start->8--- > *lhs = make_number(lval + > (tree->type == Node_prein

Re: [Tinycc-devel] [bootstrappable] Re: wip-full-source-bootstrap: from a 357-byte `hex0' to 'hello'

Danny Milosavljevic wrote: int main() { double f = 1.0; return 0; } ... I get a bus error here: │ 0x24698 vstr d0, [r0] │ ... And indeed, (0x24b01e % 8) == 6, not 0.

Re: [Telegram-Desktop]: Help with packaging

Le 8 janvier 2021 07:11:38 GMT-05:00, Ekaitz Zarraga a écrit : >Hi, > >I'm not sure about what I'm going to say so take it with care: > >About the permission error I think the build directories are write >protected by default it Guix, please someone correct me if I'm wrong. >I'd say you can ch

Re: [Telegram-Desktop]: Help with packaging

Raghav Gururajan writes: > Hello Guix! > >> With this email, I have attached the complete diff, which is to be >> applied on top of master. > > I have attached wrong file before. Here is the correct one attached. The error you posted is this: --8<---cut here---start--

Re: [Telegram-Desktop]: Help with packaging

Hi, I'm not sure about what I'm going to say so take it with care: About the permission error I think the build directories are write protected by default it Guix, please someone correct me if I'm wrong. I'd say you can change the permissions of the folder with the chmod util, you can see many

Re: Cuirass logo - artwork.

Hi! Thanks again for all the efforts you are putting into Cuirass! Since we are on the topic, I have 2 questions: - Why is it called "Cuirass"? :p - Why the move to PostgreSQL? Cheers! -- Pierre Neidhardt https://ambrevar.xyz/ signature.asc Description: PGP signature

Cuirass logo - artwork.

Hello, I have started some heavy background work on Cuirass including its port to PostgreSQL and a new remote building mechanism. I think it would be nice to give the project a nice logo that could be displayed on the web interface, and maybe on an hypothetical project page. A 'Cuirass' is a p