Hi!
Attached is a patch that seems to work for me. I don't think #!eof
should be handled specially, as it is a distinct object.
felixFrom 834a8d231d5bcdfc9bc517e8902ceee3c18d98e8 Mon Sep 17 00:00:00 2001
From: felix
Date: Sun, 23 Dec 2018 20:44:51 +0100
Subject: [PATCH] preserve read/write
>
> Here's a version with more extensive test suite. Tested to work with
> master.
>
I'm probably missing context here, but what is the use case of
this form?
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
> On 2018-12-10 13:39, felix.winkelm...@bevuta.com wrote:
> > Evan, the patches don't apply cleanly. Can you rebase them to the
> > current master?
>
> Sure, here's a set that can be applied in order.
>
> megane has asked that the third one be left out until we have a look at
> the other
Evan, the patches don't apply cleanly. Can you rebase them to the
current master?
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
The attached patch adds the "c-objects" component type to the .egg
format to allow integrating compiled C/C++ objects to be linked into
eggs without resortring to the hassle of using custom-build. For
static objects that are combined with c-objects, the static linking
mechanism has been extended
Two patches that drop obsolete debugging functionality.
felix
From 244190d134da89a5f86fc77a07cb897eb1abb612 Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 6 Dec 2018 16:05:46 +0100
Subject: [PATCH 1/2] Drop ancient "stress test" feature.
This was once used to force minor GCs randomly.
---
Pushed, thanks.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Hi!
Indeed, all you say is right. It needed a full recompile with the HEAD
to trigger this error by generating a use of the unboxed fXX accessors
in the SRFI-4 runtime system.
See attached patch, the reason is quite clear: the unboxed accessors
assumed unboxed fixnum index arguments.
felix
Sorry, I sent an empty mail. I'm trying to reproduce this.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
> Hi Felix,
>
> On Sat, 01 Dec 2018 08:42:40 +0100 felix.winkelm...@bevuta.com wrote:
>
> >> No problem. Unfortunately, now "make check" breaks:
> >>
> >> Error: assertion failed: (eqv? (f32vector-ref old 6) (f32vector-ref new 0))
> >
> > Ouch. I'm running make check with something based on
>
> No problem. Unfortunately, now "make check" breaks:
>
> Error: assertion failed: (eqv? (f32vector-ref old 6) (f32vector-ref new 0))
>
Ouch. I'm running make check with something based on the current
HEAD all the time, on what platform is this? Is the error consistently
appearing? If you
> On Wed, Nov 28, 2018 at 07:25:33PM +0100, Mario Domenech Goulart wrote:
> > It looks like this patch (79cf7427, master) has broken "make
> > bootstrap". Log attached (using CHICKEN 5.0.0 as CHICKEN).
>
> Right you are. The reason is that lfa2 is trying to unbox the arguments
> to
Thanks, your suggestions seem to be correct, I applied the patch and removed
the last call to sub-boxed!. I also added a (very simple) test.
> - Finally: there are still quite some remnants of the old boxing/unboxing
>code around to mark variables as 'boxed, and there's still ##core#box
>
> >
> > There is a protocol_version test in feathers.tcl ... Is this what you mean?
>
> Ah, I suppose so. I couldn't find it so quickly; where is it in the C code?
C_DEBUG_PROTOCOL_VERSION
> What happens when the version is different?
feathers aborts.
felix
>
> One thing though; I think we need to add some sort of versioning support
> to the debugger protocol so when you run feathers to talk to a program
> compiled with a different version of CHICKEN, this is going to fail.
>
> I think this is a situation we ought to at least detect and warn or
This patch adds an additional optimization pass to the "lfa2"
compiler stage, which attempts to remove unnecessary
boxing and unboxing of floating point numbers. Specifically,
calls to floating point inline operations that have a variant that
accepts unboxed arguments are replaced with a faster
>
> Here's the patchset without the first commit.
>
Thanks, much appreciated. Now we just have to find someone who understands
the scrutinizer and can review these patches... :-)
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
> > I'm vehemently against patches that merely change whitespace or
> > layout (patch 1/9) and make it impossible to track changes properly.
>
> You can give the -w switch to git blame to see through whitespace
> changes. Or (setq vc-git-annotate-switches '("-w")) in emacs if you're
> using
>
> Hi,
>
> Here's a reworked patch set. It's not exactly small, but I tried to make
> it pretty easy to follow. Except maybe for the last patch, which
> digs for some extra info from the nodes.
>
> There's small bit of back-and-forth in the patches:
> - errors? is taken out of let and put
> felix.winkelm...@bevuta.com wrote:
> > 2 patches: first one fixes the problem that program components
> > are not considered when resolving component dependencies,
>
> Pushed, thanks :)
>
>
> > second adds "cond-expand" + "error" forms to the egg specification
> > format and resurrects
2 patches: first one fixes the problem that program components
are not considered when resolving component dependencies,
second adds "cond-expand" + "error" forms to the egg specification
format and resurrects "chicken-install"s "-feature" option.
felix
From
> Hi all,
>
> I noticed that /egg/foo still redirects to eggref/4/foo. Should we
> change this to redirect to eggref/5/foo now that 5.0.0 is officially
> the current release?
Yes, C5 should be the one official version, I think.
felix
___
Hi!
Here is an updated patch that adds the import libraries of a compiled module
(.scm variant) and the link files of static extensions to the target list
for chicken-do(1) invocations.
felix
From ffb8bd6e317de199d5c2482f68d90d554a00eb3c Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 20 Oct
> On 2018-10-24 9:31, felix.winkelm...@bevuta.com wrote:
> > > The patch looks OK to me. Just one question, having more to do with the
> > > feature it adds than the patch itself: now that chicken-do supports
> > > multiple targets, should the import libraries for modules be added as
> > >
> Hi Felix,
>
> The patch looks OK to me. Just one question, having more to do with the
> feature it adds than the patch itself: now that chicken-do supports
> multiple targets, should the import libraries for modules be added as
> targets in addition to the types and inline files?
Do you mean
> On Sun, Oct 21, 2018 at 12:39:07PM +0200, felix.winkelm...@bevuta.com wrote:
> > No, you're quite right, but since there is not much variance (with regard
> > to tools) there, I considered it unnecessary. But we can do it your way,
> > if you prefer.
>
> I think it's a bit simpler/less
> This looks alright, but I still have a question: why not use the install
> command on Windows too? That should allow us to get rid of the platform
> case and simplify install-executable-command and install-file-command so
> it doesn't even need to accept the platform.
>
>[...]
>
> Maybe I'm
As described in the commit message, fixes #1550 (hopefully).
felix
From dfa410001df6224a53eeacd40cfe226600c009e0 Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 20 Oct 2018 13:54:03 +0200
Subject: [PATCH] allow multiple targets in "chicken-do" invocations
To handle selective deletion of files
A trivial change.
felix
From 3f4eabcd8984016b6256b148dc97bf38833ff67a Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 20 Oct 2018 13:52:27 +0200
Subject: [PATCH] drop last debris of chicken-bug program removal
---
Makefile.cross-linux-mingw | 4 ++--
defaults.make | 3 ---
2
This patch reuses parameters for default.make for the name of the
installation program to be used for egg installation, including options.
felix
From e7b25a1fff103cc876f8abf36e2d8064012d9e9a Mon Sep 17 00:00:00 2001
From: felix
Date: Tue, 16 Oct 2018 13:34:42 +0200
Subject: [PATCH] Use
> Hi all,
>
> I found out about this issue yesterday while porting sql-de-lite:
> https://bugs.call-cc.org/ticket/1550
>
> I noticed that the egg compilation code specifically drops the
> options -emit-types-file and -emit-inline-file for performance
> reasons. It doesn't look like that has
A trivial change, as reported by Vasilij.
felix
From 58c9ef16179d1d73aca363e84f702fda731eee35 Mon Sep 17 00:00:00 2001
From: felix
Date: Fri, 12 Oct 2018 11:23:48 +0200
Subject: [PATCH] remove redundant definitions from chicken-config.h
(as reported by wasamasa)
---
Makefile.android | 1 -
> On Tue, Sep 18, 2018 at 01:01:55PM +0300, megane wrote:
> > Hi,
> >
> > Here's a patch for #1533. The fix itself is pretty simple.
> >
> > The first patch makes scrutinizer tests give more info when a test
> > fails, which makes it faster to figure out these refinement issues.
>
> Looks good
> The problem with old versions of chicken-install would be they don't
> understand those new forms. But for those I guess you'd just pin
> the version of the egg to an older one.
With cond-expand in egg files, you can always do a
(cond-expand (chicken-5.x ...) (else ...))
felix
Hi!
A trivial change, fixing an unnecessary test reported by the
scrutinizer during build.
felix
From 57171d0d9dfe8dafcd52a84954081e367319fa2b Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 27 Sep 2018 22:07:22 +0200
Subject: [PATCH] drop unnecessary test
---
lolevel.scm | 2 +-
1 file
Hi!
I wonder: there is no way to conditionally set options, configure egg building,
etc. I think it would be handy to have a "cond-expand" form that can be used
inside
..egg files customize the egg build/installation depending on platform.
This would also bring back the "-feature" option for
> Hi folks,
>
> I think the extension list in setup.defaults is out of date -- it still
> refers to units and includes some that don't exist anymore.
>
> Here's a patch that switches it to just "srfi-4", which is of course
> still around. I'm not totally sure this is right; we could conceivably
Attached the fix for #1534 in C4, somehow I didn't see that this one was
broken, too...
felix
From f9c28c08c5f381040fb6ebfbcae05d18b841c057 Mon Sep 17 00:00:00 2001
From: Felix Winkelmann
Date: Mon, 17 Sep 2018 10:01:53 +0200
Subject: [PATCH] =?UTF-8?q?Fix=20broken=20string-ci<=3D=3F/string
This patch fixes the problem reported by Sven Hartrumpf (originally
by Nils Holm) with the aforementioned primitives.
Note that this bug already seems to be fixed in C4, as far as I can
tell.
felix
From 5b29d4a1fa3df935c5e68bb2913b7d831ef77932 Mon Sep 17 00:00:00 2001
From: felix
Date: Sat,
> By relocation I mean when a program is deployed into a package
> repository or otherwise distributed to users. At that point, the paths
> are no longer helpful since those directories won't exist. The full
> paths also leak information about the build environment, which is part
> of the issue
> On 2018-09-09 9:28, felix.winkelm...@bevuta.com wrote:
> > I don't think this is a good idea or even worthwhile. I strongly object.
>
> Do you mind if I ask why?
No.
>
> If it's that you would prefer the build tools to use absolute pathnames
> in all cases, then I'm happy to find another
>
> The other two fix some bugs where strings are being double-quoted for
> shell with the `qs*' procedure, causing build failures in one case and
> incorrect directory paths to be created in the other.
These don't seem to apply.
felix
___
> Hello,
>
> Here are a few patches that I think should be included in the next RC.
>
> The first fixes #1505 by simply using relative pathnames for all source
> files in generated build scripts. All other file paths (e.g. target
> pathnames, source paths in install scripts, etc.) remain
> * felix.winkelm...@bevuta.com [180906 12:27]:
> > Should be self-explaining...
>
> I would delay this patch. I did look up FreeBSD's code base and it
> seems that they have importet OpenBSD's version 18 days ago, according
> to
> On Thu, Sep 06, 2018 at 04:52:29PM +0200, Peter Bex wrote:
> > Ah of course. Thanks for reporting!
> >
> > It seems that this is caused by the fix for #1515, and apparently on Mac OS
> > we were relying on the bogus behaviour that strings were just spliced into
> > the arguments list. Could
Should be self-explaining...
felix
From 2269c7c18dbe905fa0c21d7c72b4d63299391e3f Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 6 Sep 2018 12:25:20 +0200
Subject: [PATCH] Use arc4random_buf(3) on FreeBSD + DragonFly
---
runtime.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
> OK, attached is a new patch that keeps slashification where it was
> already present (except for shell variables; those don't have to be
> quoted or slashified). I decided to move the slashification into "qs*"
> so that it's easier to add or remove slashification on any given call.
>
> From a
> Here's another attempt. Attached are two patches:
>
> * 0001-chicken-install-accept-distribution-files-egg-proper.patch
> That's for chicken-core. It reverts the change to `files' (i.e., the
> previous patch to revert the change that broke things does NOT need to
> be applied) and adds
> On Sun, 02 Sep 2018 13:34:27 +0200 felix.winkelm...@bevuta.com wrote:
>
> >> Hi,
> >>
> >> Attached is a small patch to address http://bugs.call-cc.org/ticket/1511
> >>
> >> If it looks good, I propose the documentation that you can see in the
> >> second patch (files-doc.diff).
> >>
> >
> >
> Hi,
>
> Attached is a small patch to address http://bugs.call-cc.org/ticket/1511
>
> If it looks good, I propose the documentation that you can see in the
> second patch (files-doc.diff).
>
OK, I applied these patches. The second gave some trouble so I had to
apply it by hand and add a few
> How should we go about this topic?
>
> The easiest approach would be using `files' in the egg description file.
> It should not require any modifications to henrietta-cache. As far as I
> can see, only flipping `f' in chicken-install.scm should do the trick.
> Felix mentions `files' in the
> I thought it wasn't necessary anymore, but on second thought that might
> have been a mistake: qs doesn't convert to slashes. Having said that,
> it looks like slashify was used just as inconsistently as quotearg.
>
> If you follow the instructions in the README, you need to install with
> a
> Here's a patch for #1515. It turns out to be quite invasive because the
> quotation stuff was completely messed up. Even on *nix, chicken-install
> didn't work when CHICKEN was installed to a PREFIX path with spaces in it!
>
I maybe missing something, but why is "slashify" not used anymore?
> After fixing all the quoting issues, I finally ran into this weirdness
> when running the tests:
> https://stackoverflow.com/questions/9964865/c-system-not-working-when-there-are-spaces-in-two-different-parameters#9965141
>
> Note that this only holds for system(), it does not seem to be
> Hi,
>
> Attached is a small patch to address http://bugs.call-cc.org/ticket/1511
>
> If it looks good, I propose the documentation that you can see in the
> second patch (files-doc.diff).
>
I suggest we use a different name to avoid confusion, say,
"distribution-files".
felix
> There is some canonicalisation that happens to module names in other
> places (e.g. converting (srfi 1) -> srfi-1), so I think this needs to
> use the existing routine for that. How about the attached patch?
Much better. Pushed.
felix
___
This patch addresses the requests from Thomas and Ivan to support
directories transparently in include and data components for eggs.
"install-data" and "install-c-include" have been factored and
create parent directories as needed.
felix
From 2723d084ecd541a42143ee829bea262ed99cde3f Mon Sep 17
> Additionally I propose that the (destination ...) form should be made
> relative to the default target directory and create all specified
> subdirectories as necessary, then I could just add a
>
> (destination "../extend/protobuf")
>
> to the c-include form above and be happy.
I don't see
This patch addresses a platform incompatibility in runtests.sh.
felixFrom db873d6dab3b00f985c0547b27c676501f151179 Mon Sep 17 00:00:00 2001
From: felix
Date: Wed, 29 Aug 2018 14:54:30 +0200
Subject: [PATCH] For unsetting CHICKEN_REPOSITORY_PATH use "env -u" only when
MSYSTEM is set
---
Hi!
As in the subject, noted by Thomas Chust.
felix
From 0615f14c352ee1603c84782314b8c787e97379a1 Mon Sep 17 00:00:00 2001
From: felix
Date: Wed, 29 Aug 2018 14:34:35 +0200
Subject: [PATCH] Allow list-notation for modules property in egg files
---
egg-compile.scm | 7 ++-
1 file changed,
>
> I can't say that I like this design decision, but I guess I'll have to
> live with it. If this is unsupported, it also feels strange that
> the .egg format allows specification of multiple import libraries per
> extension at all – the provider side of the picture, when you write a
> library
> Hello,
>
> multiple sets of files may already be possible with multiple component forms
> in the .egg, but installation into any nested subdirectories relative to the
> CHICKEN installation prefix is currently not possible.
>
> For example, some include files provided with the protocol
> On Wed, Aug 29, 2018 at 10:57:54AM +0200, felix.winkelm...@bevuta.com wrote:
> > The foreign-declare case is simple and straightforward and should
> > be used, if possible, but we need a fallback solution and this case
> > of a separate .c file is common enough to be addressed.
>
> For 5.0?
>
> I have a couple of eggs that generate and compile code similar to the
> way chicken-crunch works. These eggs would install header or source
> files that are required for the compilation process. Some of these
> source files belong to distinct functional modules that are organized
> in
Hi, Thomas!
I'll try to address some of your questions.
> - Some eggs install one extension library containing several modules. The new
> CHICKEN module system always tries to load a library named the same as the
> module upon import. Is it no longer possible to separate library loading and
>
This problem was mentioned chicken-users: a custom build script
for an extension was invoked for the the code module and the import
library, but it doesn't make sense for the latter. With this patch the
import library will be built by csc, regarding of the custom build
script.
felix
From
> Hi all,
>
> apparently chicken-install lost the -D switch.
>
> To put it mildly: This worries me a lot.
>
There is no bad intent behind this - during the rewrite simply a few options
were dropped, since they didn't look crucial. If you want it back, no problem.
felix
> Applied, with a little tweak.
>
I don't understand this tweak. Why applying ->string twice?
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
This patch addresses the issue reported by Joerg: all arguments to
subprograms are converted to strings now, so strings, numbers and
symbols are accepted.
felix
From 97d8934c482b3fe87cecad3be5ff7d1e5fb2f730 Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 18 Aug 2018 10:45:57 +0200
Subject:
> Hey Jörg
>
> > Any reasons this is not a good idea (TM).
>
> The string syntax allows things such as easily specifying several
> libraries to link. Compare ("-L" "-lfoo -lbar") with (-L -lfoo -lbar).
> The latter is an error as it's interpreted as three separate arguments
> and the -l
> Hi all,
>
> As I was trying to install spiffy on Haiku, I noticed that the
> posix-groups egg (a dependency) refused to install because haiku
> is not unix, and posix-groups.egg has a (platform unix) clause.
>
> So I changed it to (platform (or unix haiku)) and it still failed.
> If I swapped
> Hi all,
>
> I was testing rc1 on Haiku and noticed that the file-access-test fails.
> It turns out that stat() on Haiku will return 0 when the path contains
> a trailing slash, even if it's a file (POSIX says it should return -1
> and set errno to ENOTDIR).
>
> Attached is a patch that copies
> As discussed on IRC, it doesn’t make much sense to have
> (repository-path) return a string now that it’s a search path and thus
> is not guaranteed to be a valid directory name any longer.
>
> I tried to keep the scope of this patch as minimal as possible, it’s not
> very clean but it seems to
> Speaks for itself.
>
>
Pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
Pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
> When reviewing the last chicken-status patches from evhan, I found two
> little problems:
>
> chicken-install doesn’t cleanup its temporary files in every cases and
>
> chicken-status doesn’t find the version of eggs in the cache when
> using the `-cached` option
>
Pushed.
felix
This patch adds a "component-options" egg specification item to specify global
csc- or link-options for all components. These options are combined with
component-specific options.
This fixes #1484.
felixFrom 8b490adeeb9b5e98d0ceccc40757d7992af6384e Mon Sep 17 00:00:00 2001
From: felix
Date:
> Hi all,
>
> As far as I can tell, there's only one minor ticket left: #1484.
> This should be relatively easy to implement.
I can take a look at that.
>
> Given that many of the essential eggs have been ported, we should
> try to make a release soon. Different people have wishlists about
>
> Hi,
>
> please just answer "yes, that's normal" or "don't believe" (or "changed
> with chicken 5) - if you don't believe I will make further tests before
> wasting your time.
Drop the "export" from your "define-interface" forms
felix
___
> Here's a fix for something I noticed while testing Felix's patch.
> Without it, we can chicken-install directories correctly but not
> chicken-uninstall them.
>
Pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
> Thanks, applied.
>
> I made a small change, to prepend the source dir *before* checking for
> directories rather than after. Otherwise it would only work when
> installing from within the source directory.
>
Ugh... thanks!
felix
___
While porting manual-labor, I noticed that a data component that wants to
copy a directory did not work. Now the install script distinguishes
directories and tries to use the correct shell operation.
felixFrom 9fabde9d10b3cb6ddf5e01d504e5f4fc445748ab Mon Sep 17 00:00:00 2001
From: felix
Date:
This was reported by Peter: egg build scripts on Windows did not abort on
error, as the exitlevel of each command has to be checked explicitly.
felix
From 29b7d964852c9701d559b351080874dfdd397f2d Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 30 Jun 2018 11:53:11 +0200
Subject: [PATCH] Check
Sorry, that last patch was broken. Attached a better one.
felixFrom f948339ce8ef8fa437b1966866615270bef3379c Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 28 Jun 2018 09:00:23 +0200
Subject: [PATCH] chicken-install: use explicit ".bat" extension for custom
scripts on Windows
This also
See commit message.
felixFrom 1157bf50aa9a27774d129766ecc54dcc3ec0323c Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 28 Jun 2018 08:46:23 +0200
Subject: [PATCH] chicken-install: use explicit ".bat" extension for custom
scripts on Windows
THis also converts the names in chicken-do dependency
The attached patch fixes a problem found by Kooda: Henrietta transmits the
egg version during download and this is correctly stored in the VERSION
file in the egg cache, but was not propagated to the installed .egg-info
file, so chicken-status was unable to obtaint the installed egg versions.
Now
Pushed.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-hackers
> Hello,
>
> Here's a fix for an issue Kristian discovered at the last meetup. It's
> related to our switch to a more strict treatment of definitions occuring
> outside the top level. Basically, definitions in an included file should
> be allowed (but currently aren't) if the include occurs
> Sorry, that patch was incomplete -- it needed to include one additional
> hunk that makes chicken actually use the setup-mode logic in the
> previous patch. The rest of the fix for #1468 is attached.
>
Excellent. Works. Pushed.
felix
___
> Hello,
>
> Here's the fix for #1468 in a patch that will apply to master. The
> commit message has details.
Pushed. I ran make check, installed awful from scratch and build a
static awful-server. I did not make any further tests, so I leave closing
the ticket to someone else.
felix
>
> And indeed, the chicken-5-eggs repo does not contain a bind/gen-lexer
> script.
Oh, fuck. I could swear that bind did work for C5 once, but apparently it never
did.
felix
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
> On 2018-06-09 16:40, felix.winkelm...@bevuta.com wrote:
> > I tried to make patch #1 work (excluding the first hunk) but somehow
> > static extensions don't seem to be found (I tried to build a static
> > awful-server, it could not find awful..o even though it is installed.
> >
> > I strongly
> On Sat, Jun 09, 2018 at 10:18:01AM +0200, felix.winkelm...@bevuta.com wrote:
> > See commit message.
>
> Thanks, I've pushed this. Now the C5 bind egg doesn't give an obscure
> message from map not accepting #f as an argument, but you get a clear
> message that gen-lexer doesn't exist.
Does
Hi!
I tried to make patch #1 work (excluding the first hunk) but somehow static
extensions
don't seem to be found (I tried to build a static awful-server, it could not
find awful..o even though
it is installed.
I strongly recommend to let all the cleanups, cosmetics and cascaded,
staggered,
> Hi all, here are a few more patches, small ones this time. The first is
> a fix for #1468, and the others clean up a handful of things I noticed
> in csc.scm, batch-driver.scm, and eval.scm while working on it.
Regarding patch #1: the first hunk seems to already applied in my repo.
Do you have
See commit message.
felixFrom e0027e126737a79d0ccc9b0b7001a0d1752981b1 Mon Sep 17 00:00:00 2001
From: felix
Date: Sat, 9 Jun 2018 10:14:22 +0200
Subject: [PATCH] Pass the source-file-dependencies to the component p-list
for generated source files
Without this the source-dependencies list in
> Hello again,
>
> Here's a small patch that adds a "best effort" attempt to do the right
> thing regarding #1469 in chicken-install. We should still consider using
> relative pathnames unsupported, but at least with this change any files
> that are built successfully will end up installed to the
This patch adds variables for csc / csi to egg build scripts and "export"
is used to make them available in custom build scripts.
felix
From eeb27bce4c0b6e1c69cb86ee48e49bfbb5389fa2 Mon Sep 17 00:00:00 2001
From: felix
Date: Wed, 30 May 2018 17:21:49 +0200
Subject: [PATCH] chicken-install:
The attached patch just aborts with a proper error message instead
of failing inside string->list.
felix
From eabf188d000d5cdb8139f7a5332b8d7faa432ab1 Mon Sep 17 00:00:00 2001
From: felix
Date: Wed, 30 May 2018 10:55:50 +0200
Subject: [PATCH] chicken-uninstall: show helpful msg when asking for
301 - 400 of 826 matches
Mail list logo
