From: Kei Kebreau <kei@openmailbox.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add fpc. (version 2)
Date: Mon, 20 Mar 2017 18:54:27 -0400 [thread overview]
Message-ID: <87tw6n4l0c.fsf@openmailbox.org> (raw)
In-Reply-To: <87mvcfg1nv.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 20 Mar 2017 20:59:16 +0100")
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
Ricardo Wurmus <rekado@elephly.net> writes:
> Danny Milosavljevic <dannym@scratchpost.org> writes:
>
>> Hi,
>>
>>>+ (copy-file (assoc-ref inputs "fpc-binary")
>>>+ "fpc-bin.tar")
>>>+ (zero? (system* "tar" "xvf" "fpc-bin.tar")))))
>>
>> Why the copy-file and then untar ? Can't it be untarred immediately from where it is? If it is useful, maybe add a comment about the reason.
>>
>> Also, it might be easier to have a fpc-bootstrap package with the
>> bootstrap binaries that installs the binaries required to build fpc
>> normally and to make a fpc package depend on fpc-bootstrap as
>> native-inputs. What do you think? I myself don't have a strong
>> preference about it - but some other packages do it that way.
>
> It’s not so nice to depend on a binary bootstrap. Can this be avoided?
> I tried packaging a version of the GNU Pascal compiler, which is
> unmaintained, in an effort to bootstrap a version of FPC from source.
>
> Have you attempted this?
>
Though I would prefer a source bootstrap, I haven't attempted this. I
anticipate that it would be no small feat getting the GNU Pascal
compiler to work. Were you using a recent version of GCC to try to
bootstrap FPC?
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-03-20 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 22:44 [PATCH] gnu: Add fpc Kei Kebreau
2017-01-27 4:01 ` [PATCH] gnu: Add fpc. (version 2) Kei Kebreau
2017-01-27 4:52 ` Kei Kebreau
2017-01-27 6:00 ` Kei Kebreau
2017-03-12 12:47 ` Danny Milosavljevic
2017-03-13 21:22 ` Kei Kebreau
2017-03-14 21:45 ` Danny Milosavljevic
2017-03-20 15:02 ` Kei Kebreau
2017-03-20 19:59 ` Ricardo Wurmus
2017-03-20 22:54 ` Kei Kebreau [this message]
2017-06-05 13:20 ` Danny Milosavljevic
2017-06-05 13:33 ` Marius Bakke
2017-06-05 13:42 ` Marius Bakke
2017-06-09 1:30 ` Kei Kebreau
2017-06-05 19:55 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tw6n4l0c.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.