On Sun, Dec 12, 2010 at 9:40 PM, Matthew Mondor wrote:
> I could indeed see the ECL_BASE_STRING_P() check in enter_directory()
> but had no idea how come that case wasn't problematic before or with
> other software.
>
Maybe there was some normalization phase in older versions of ECL (somewhere
co
On Sun, 12 Dec 2010 20:09:13 +0100
Juan Jose Garcia-Ripoll wrote:
> I identified the problem and fixed it. Slime is building pathnames with
> components of type (array character (*)) while the operating system (or at
> least the ECL routines) only accept (array base-char (*)). I have added a
> fi
On Sun, Dec 12, 2010 at 5:23 AM, Matthew Mondor wrote:
> On Sat, 11 Dec 2010 14:55:21 -0500
> Matthew Mondor wrote:
>
> > I'll also try with an up to date slime when I have more time, but I
> > wanted to post this in case the origin of the problem seems obvious to
> > others.
>
> It also happens
On Sat, 11 Dec 2010 14:55:21 -0500
Matthew Mondor wrote:
> I'll also try with an up to date slime when I have more time, but I
> wanted to post this in case the origin of the problem seems obvious to
> others.
It also happens with today's SLIME CVS HEAD and an empty ~/.eclrc
--
Matt
--
I didn't take time to try with a more recent version of slime yet,
although I've used that tree for a while successfully with various
previous ECL builds. This is using today's ECL CVS HEAD.
What I get is the following:
[...]
;;; Note:
;;; Invoking external command:
;;; gcc -I. "-I/usr/local
