Re: [Chicken-users] (no subject)
Yes - but i should also mention this is on a brand new machine too so they were not stale builds. Anyway, no luck. On Sep 15, 2007, at 9:19 PM, Zbigniew wrote: Did you try rebuilding any of the eggs? On 9/15/07, Todd Ingalls <[EMAIL PROTECTED]> wrote: i built snapshot chicken-2.708 on intel mac, and now every egg i try to use results in a segmentation fault ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] (no subject)
Did you try rebuilding any of the eggs? On 9/15/07, Todd Ingalls <[EMAIL PROTECTED]> wrote: > i built snapshot chicken-2.708 on intel mac, and now every egg i try > to use results in a segmentation fault ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
[Chicken-users] (no subject)
i built snapshot chicken-2.708 on intel mac, and now every egg i try to use results in a segmentation fault (use easyffi) ; loading /usr/local/lib/chicken/1/easyffi.so ... Segmentation fault ;1> (use loop) ; loading /usr/local/lib/chicken/1/loop.scm ... ; loading library srfi-1 ... ; loading /usr/local/lib/chicken/1/loop-support.so ... Segmentation fault i would be glad to provide additional info - anything that would be helpful? ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
Re: [Chicken-users] chicken-setup on Windows
> > I found a problem with the latest SVN check out of Chicken. chicken-setup > could download and compile extensions all right, but failed when copying > them because the paths passed to the copy command contained both forward- > and back-slashes. I've attached a patch that will, under Windows only, quote > any paths with forward slashes in them, which fixes the problem. I tested it > under Linux also (Ubuntu 7.04), and it still worked fine there. Thanks, Eric. The patch is applied. > > Another option would be to change the appropriate make files to insert the > correct path separator for each OS. I played with doing that for a while, > but the combination of passing the paths in on the command line, running > them through make, and writing them to the C header file seemed error prone > and brittle. Yes, it wouldn't really enhance the readability of the makefiles. > > I wasn't entirely sure where to send this, since it's more of a bug fix than > a bug report. If I need to post this to Trac, just let me know. This is fine. > > Thanks for a great product. I really appreciate all the work that's gone > into it. You're welcome. Thanks for using it! cheers, felix ___ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
