emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#39372: closed (Chicken Scheme: Update version to 5.1.0 and add gcc-t


From: GNU bug Tracking System
Subject: bug#39372: closed (Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain)
Date: Sun, 09 Feb 2020 20:03:02 +0000

Your message dated Sun, 9 Feb 2020 21:01:47 +0100
with message-id <address@hidden>
and subject line Re: [bug#39372] Chicken Scheme: Update version to 5.1.0 and 
add gcc-toolchain
has caused the debbugs.gnu.org bug report #39372,
regarding Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden.)


-- 
39372: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=39372
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain Date: Fri, 31 Jan 2020 16:22:41 +0000
Hi,

I made a patch for chicken-scheme according to this conversation in the 
help-guix mailing list:

https://lists.gnu.org/archive/html/help-guix/2020-01/msg00230.html

I pushed the version to 5.1.0 and added gcc-toolchain as a propagated-input as 
the conversation suggested. The reason is without the gcc-toolchain csc (the 
chicken compiler) is unable to deal with -lm (math library), which is not 
installed with the current chicken package.

The linked conversation suggests that gcc-toolchain is a fundamental part of 
chicken so it should be a dependency of it.

Sorry if I didn't follow the format, but I was unable to find a good 
contributing guide.

Best,

Ekaitz


Attachment: chicken.diff
Description: Text Data


--- End Message ---
--- Begin Message --- Subject: Re: [bug#39372] Chicken Scheme: Update version to 5.1.0 and add gcc-toolchain Date: Sun, 9 Feb 2020 21:01:47 +0100
Le Sun, 09 Feb 2020 14:11:09 +0000,
Ekaitz Zarraga <address@hidden> a écrit :

> > I suppose this is caused by a module loop or something between (gnu
> > packages scheme) and (gnu packages commencement). Maybe splitting
> > (gnu packages scheme) into two things (maybe a new (gnu packages
> > chicken)) would solve the issue?  
> 
> I think it does. I made a new patch with that but I'm not sure if I
> did everything right:
> 

Pushed as 2846aec2f7d53b9244ad55c1436437843287426a and
7f6cb6bbac181a11859283922037e374a82035db. Thank you!


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]