Marius Bakke writes:
> Marius Bakke writes:
>
>> Just to piggy-back on this discussion, I'm attempting to package
>> "Hedgewars" and needed this patch to get fpc working properly:
>
> Oops, found one more patch in that old branch. @Kei, feel free to squash
> this into the original patch:
Patch
Danny Milosavljevic writes:
> ... but it turns out that gpc patches gcc parts - and the most recent
> patch is for gcc 4.0.3 - which we don't carry.
Actually, the most recent patch is for 4.3, which is why I’ve packaged gcc-4.3:
--8<---cut here---start->8---
Marius Bakke writes:
> Just to piggy-back on this discussion, I'm attempting to package
> "Hedgewars" and needed this patch to get fpc working properly:
Oops, found one more patch in that old branch. @Kei, feel free to squash
this into the original patch:
From cb94a2c4c697541183cb912039399df54e
Just to piggy-back on this discussion, I'm attempting to package
"Hedgewars" and needed this patch to get fpc working properly:
From 4f76fb12f031652e11063c0fb37949229caa45cc Mon Sep 17 00:00:00 2001
From: Marius Bakke
Date: Tue, 25 Apr 2017 15:39:30 +0200
Subject: [PATCH] gnu: fpc: Make sure it f
Hi,
to experiment, I tried this:
(define-module (wip pascal)
#:use-module ((guix licenses) #:prefix license:)
#:use-module (guix packages)
#:use-module (guix download)
#:use-module (guix git-download)
#:use-module (guix hg-download)
#:use-module (guix utils)
#:use-module (guix build
Ricardo Wurmus writes:
> Danny Milosavljevic 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
Danny Milosavljevic 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
Danny Milosavljevic 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
>
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
Danny Milosavljevic writes:
> Hi Kei,
>
> is anything holding this up?
>
> I've tested it and can confirm it works fine.
Not that I can remember. I believe it was just waiting for review. If
this counts as a positive review I can see about tidying it up if
necessary and pushing it to master.
s
Hi Kei,
is anything holding this up?
I've tested it and can confirm it works fine.
Kei Kebreau writes:
> Kei Kebreau writes:
>
>> Kei Kebreau writes:
>>
>>> This is a patch that adds a package for the Free Pascal Compiler.
>>> Can someone verify that this builds reproducibly on an i386 machine?
>>
>> This update allows the compiler to find its configuration file.
>
> My apolo
Kei Kebreau writes:
> Kei Kebreau writes:
>
>> This is a patch that adds a package for the Free Pascal Compiler.
>> Can someone verify that this builds reproducibly on an i386 machine?
>
> This update allows the compiler to find its configuration file.
My apologies, the former upload was missin
Kei Kebreau writes:
> This is a patch that adds a package for the Free Pascal Compiler.
> Can someone verify that this builds reproducibly on an i386 machine?
This update allows the compiler to find its configuration file.
From 10b52891b6fd522231081e5735ce5287060dff21 Mon Sep 17 00:00:00 2001
Fr
14 matches
Mail list logo
