From: Adonay Felipe Nogueira <adfeno@hyperbola.info>
To: guix-devel@gnu.org
Subject: Re: LanguageKit (targets llvm)
Date: Sat, 13 Jan 2018 13:09:32 -0200 [thread overview]
Message-ID: <877esl7q37.fsf@hyperbola.info> (raw)
In-Reply-To: <CAJ98PDzpRCOLansHdLdfm79iMM0-6mF94gDqegTCEYcgt24Dhg@mail.gmail.com> (catonano@gmail.com's message of "Sat, 13 Jan 2018 15:47:21 +0100")
For those just getting the discussion, I have here a stripped log from
from #guix IRC channel at chat.freenode.net:
--8<---------------cut here---------------start------------->8---
2018-01-13T11:31:33-0200 <catonano> the Languagekit project targets llvm. Is
it good for Guix ? And how does that relate to the GNU project ?
http://etoileos.com/etoile/features/languagekit/
[...]
2018-01-13T11:38:19-0200 <wigust> correctly: This is bad for user's freedom
for sure (non-copyleft thing), but we have in Guix packages with those
licenses.
[...]
2018-01-13T11:45:55-0200 <adfeno> catonano wigust: Agree, LLVM is one of the
worst indeed.
2018-01-13T11:46:44-0200 <adfeno> The question is: what should we do? (a)
Provide recipes to build with GCC; (b) Use LLVM.
2018-01-13T11:47:35-0200 <adfeno> I vote for (a), but it would be somehow more
work in the begining. After the recipes are ready, however, we will have the
option to send them upstream. This is an option of course, not a requirement.
2018-01-13T11:48:54-0200 <adfeno> ... but I wish that LanguageKit would soon
figure out the right reasons for using GCC build recipes/instructions
instead.
2018-01-13T11:49:08-0200 <adfeno> ... before something worse happens.
2018-01-13T11:49:50-0200 <catonano> adfeno: something worse ?
[...]
2018-01-13T12:02:05-0200 <adfeno> catonano wigust: Re: LangugageKit and GCC
vs. LLVM: Something worse in terms of "software freedom not being available
for the end-user".
2018-01-13T12:02:23-0200 <adfeno> .... aaand I can't type today... ;)
2018-01-13T12:02:41-0200 <wigust> catonano: See about llvm from RMS
https://gcc.gnu.org/ml/gcc/2014-01/msg00247.html
[...]
2018-01-13T12:05:47-0200 <adfeno> catonano wigust: I may not be an experienced
programmer, but I can already see an issue here if LanguageKit and other
projects keep up with this madness to support LLVM.
[...]
2018-01-13T12:07:33-0200 <catonano> adfeno: we should probably move this
discussion on the mailing list. I'd love having a deeper discussion about
this
[...]
2018-01-13T12:09:58-0200 <catonano> wigust: Stallman's assessment settles the
point of the relationship between the GNU project and LanguageKit
2018-01-13T12:10:43-0200 <catonano> it´s a pity because otherwise GNUStep is
an interesting project
2018-01-13T12:10:45-0200 <adfeno> catonano wigust: Agreed to move to mailing
list. ;)
2018-01-13T12:10:50-0200 <catonano> ok
2018-01-13T12:11:00-0200 <adfeno> ... who will do the move?
2018-01-13T12:11:10-0200 <catonano> adfeno: I will ;-)
2018-01-13T12:11:23-0200 <adfeno> Oh OK thanks catonano ;)
[...]
2018-01-13T12:49:46-0200 <catonano> adfeno: I wrote on the dev ml
[...]
2018-01-13T12:56:24-0200 <adfeno> catonano: OK ;)
2018-01-13T12:56:31-0200 <adfeno> Thanks! :D
--8<---------------cut here---------------end--------------->8---
2018-01-13T15:47:21+0100 Catonano wrote:
> This project
>
> http://etoileos.com/etoile/features/languagekit/
>
> targets llvm
>
> As far as I understand it doesn't target llvm too. It targets llvm _only_
>
> If I understand correctly, it aims to make dinamic languages wrap the GNUStep
> kernel
>
> Sort of like Guile does
>
> I know what Stallmand wrote about llvm
>
> But what does this mean for Guix ?
>
> Is LanguageKit acceptable in Guix ?
>
> Is it worth to ask the Etoile devs about this choice of theirs ?
> Could it be that they can help in making LanguageKit work with the GCC ?
>
> Thanks
--
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
(apenas sem DRM), PNG, TXT, WEBM.
next prev parent reply other threads:[~2018-01-13 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-13 14:47 LanguageKit (targets llvm) Catonano
2018-01-13 15:09 ` Adonay Felipe Nogueira [this message]
2018-01-13 16:29 ` Leo Famulari
2018-01-13 20:56 ` Catonano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877esl7q37.fsf@hyperbola.info \
--to=adfeno@hyperbola.info \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).