On 2015-08-07 18:30, Alexej Magura wrote:
> Fixed the problem; rolled out v4.1.0 of the Readline egg.
Works here with Readline library version 6.3.
Evan
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/c
Fixed the problem; rolled out v4.1.0 of the Readline egg.
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Would libreadline versions factor into this?
On the machine where I am experiencing this error, I am using GNU
libreadline7 ver 6.3.8-1 from Cygwin. Further, I'm using libncurses 4.9.
Let me know if any more information is necessary.
Regards,
- --
I'm getting a different error than your's, Erik, I get:
#;1> acsi: symbol lookup error: /usr/lib/chicken/7/apropos.so:
undefined symbol: C_mutate
instead of
#;1> acsi: symbol lookup error: /usr/lib/chicken/7/readline.so: undefined
symbol: C_enumerate_symbols
__
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Thank you! This does solve my problem for the time being.
Cheers,
- --
Jeremy Steward
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iQIcBAEBCAAGBQJVxOyZAAoJEHVwwAZUeZnZBdIP/iCLbztdsjVlswVHJ67oCWjo
IOoDD4P2CUuDBUy1hjk/xFE+EUqUscY9HRD4sy5KHha313to
Hello Jeremy,
Jeremy Steward writes:
> Unfortunately the main benefit of readline currently is that it
> supports history (linenoise does not, at least when I last checked).
>
> It's not the worst break in the world, as I can always use the SLIME
> egg, but that does not preserve history across s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>Would it be possible to replace readline with linenoise in your
>workflow?
Unfortunately the main benefit of readline currently is that it supports
history (linenoise does not, at least when I last checked).
It's not the worst break in the world,
Would it be possible to replace readline with linenoise in your
workflow?
http://wiki.call-cc.org/eggref/4/linenoise
— Stephen
On Fri, Aug 7, 2015, at 09:07 AM, Jeremy Steward wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> As of today I installed CHICKEN 4.10, and have encoun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As of today I installed CHICKEN 4.10, and have encountered this problem as
well. However, unlike Erik Fair, I have not even been able to install the egg
with chicken-install.
Is there a workaround in the meantime to get this working, such as rever
Jeremy Steward writes:
> Moreover, while I have not tested CHICKEN 4.10 yet, I compiled CHICKEN
> 4.9.1 myself on cygwin64 with no error,so it's unlikely any changes
> need to be made on that front.
Note that cygwin comes with a current CHICKEN package :)
--
May you be peaceful, may you live in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'll just chime in here on the side, but I believe I made an edit to the wiki
quite some time ago about switching to mingw-64, since at the time I had some
issues using the bind egg.
Moreover, while I have not tested CHICKEN 4.10 yet, I compiled C
On Fri, Aug 07, 2015 at 04:08:49PM +0200, Christian Kellermann wrote:
> Claude Marinier writes:
> > Is it useful to dig deeper into the problem with the old MinGW or should
> > I just drop it?
>
> If you aren't sure about the configuration you experienced the error in
> I think it's better not to
Claude Marinier writes:
> Building on rc4 on the same PC with mingw-w64 works without error (also
> without MSYS). Check works as expected as does numbers egg installation.
>
> I have had problems with MinGW and re-installed a couple of times. I am
> growing less confident in these installations.
On Fri, Aug 7, 2015 at 04:53, Peter Bex wrote:
> On Fri, Aug 07, 2015 at 09:54:22AM +0200, Christian Kellermann wrote:
> > * Claude Marinier [150806 20:15]:
> > > Note that I did not have this problem with the release candidates.
> >
> > Could you try with them again and tell me exactly which one w
Peter Bex scripsit:
> One problem with MINGW is that it's badly maintained (unless I'm
> mistaken, the most recent binary release is from 2013). Mingw-w64
> is better maintained, and despite the name it also works on 32 bit
> systems. I think it does support getc_unlocked. You can find it
> her
On Fri, Aug 07, 2015 at 09:54:22AM +0200, Christian Kellermann wrote:
> * Claude Marinier [150806 20:15]:
> >
> > Note that I did not have this problem with the release candidates.
>
> Could you try with them again and tell me exactly which one worked?
> Because there are no differences that touc
* Claude Marinier [150806 20:15]:
>
> Note that I did not have this problem with the release candidates.
Could you try with them again and tell me exactly which one worked?
Because there are no differences that touch code between the rc4 and
the 4.10.0 version in git. If there are differences in
17 matches
Mail list logo
