>> * image-op and program-op couldn't have been fully portable without
>> bundle-operations, and wouldn't have been attempted.
>
> I use program-op on a regular basis and it has replaced a very complex
> scripting machinery which I gladly got rid of.
+1
it eliminated an entire project for us (hu.
Hi,
On 2015-09-16 20:06 CEST, Faré wrote:
> On Wed, Sep 16, 2015 at 11:46 AM, Robert Goldman wrote:
>> [...]
>> I regret the inclusion of the bundle operations [...]
> You're underestimating what the bundle operations brought to ASDF 3,
> even on "non-C-hosted" implementations. They do work an
On Wed, Sep 16, 2015 at 11:46 AM, Robert Goldman wrote:
> On 9/15/15 Sep 15 -4:31 PM, Faré wrote:
>>> However, whereas using LISP=ccl as the driver correctly invokes buildi.exe,
>>> using LISP=allegro as the driver leads to alisp.exe being called,
>>> which is not what I wanted.
>>> I haven't inve
Robert Goldman wrote:
>> On 9/14/15 Sep 14 -5:36 PM, Kevin Layer wrote:
>> > Faré wrote:
>> >
>> >> @thor[git:master]$ ALLEGRO=/c/acl100/alisp make l=allegro test-lisp
>> >>> ALLEGRO=/c/acl100/alisp
>> >> I believe this should be ALLEGRO=c:\acl100\alisp ? (with proper shell
>> >>
On 9/15/15 Sep 15 -4:31 PM, Faré wrote:
>> However, whereas using LISP=ccl as the driver correctly invokes buildi.exe,
>> using LISP=allegro as the driver leads to alisp.exe being called,
>> which is not what I wanted.
>> I haven't investigated why.
>>
> That was because defining LISP=allegro resul
On 9/14/15 Sep 14 -5:36 PM, Kevin Layer wrote:
> Faré wrote:
>
>> @thor[git:master]$ ALLEGRO=/c/acl100/alisp make l=allegro test-lisp
>>> ALLEGRO=/c/acl100/alisp
>> I believe this should be ALLEGRO=c:\acl100\alisp ? (with proper shell
>> escaping).
>> If using cygwin, $(cygpat
> However, whereas using LISP=ccl as the driver correctly invokes buildi.exe,
> using LISP=allegro as the driver leads to alisp.exe being called,
> which is not what I wanted.
> I haven't investigated why.
>
That was because defining LISP=allegro resulted in exporting ALLEGRO=
which wasn't defined
> u
> #
> asdf="asdf-${os}/";
>
Sorry, that 'u' was a typo inserted at the last second before sending...
I think Faré's windows-env.sh supersedes and is a superset of this, but for
what it's worth here is what I have in my toplevel "run" script for asdf
testing (I've attached the whole script for reference - note that it
handles Mac, Windows, and Linux, and makes a separate copy of the asdf/
directory
On Mon, Sep 14, 2015 at 6:36 PM, Kevin Layer wrote:
> Perhaps you can give me the exact command you used. I couldn't find
> something that worked.
>
Attached are the relevant parts of an environment file that I sourced
into my cygwin bash shell with
. windows-env.sh
I tested it to work with both
I have a lot to catch up on this conversation: I was out all day today
because of the holiday.
I'll catch up with the list tomorrow or Wednesday. Sorry about the delay.
Faré wrote:
>> >> > @thor[git:master]$ ALLEGRO=/c/acl100/alisp make l=allegro test-lisp
>> >>> > ALLEGRO=/c/acl100/alisp
>> >>> I believe this should be ALLEGRO=c:\acl100\alisp ? (with proper shell
>> >>> escaping).
>> >>> If using cygwin, $(cygpath ...) can help.
>> >
>> > The test scripts are w
>> > @thor[git:master]$ ALLEGRO=/c/acl100/alisp make l=allegro test-lisp
>>> > ALLEGRO=/c/acl100/alisp
>>> I believe this should be ALLEGRO=c:\acl100\alisp ? (with proper shell
>>> escaping).
>>> If using cygwin, $(cygpath ...) can help.
>
> The test scripts are written in BASH, so that would not
Faré wrote:
>> On Mon, Sep 14, 2015 at 4:44 PM, Kevin Layer wrote:
>> > Faré wrote:
>> >
>> >>> On Mon, Sep 14, 2015 at 3:38 PM, Kevin Layer wrote:
>> >>> > This whole branch of that conversation was about an error I got while
>> >>> > compiling 3.1.5 asdf.lisp on Windows. I no longer get that
On Mon, Sep 14, 2015 at 4:44 PM, Kevin Layer wrote:
> Faré wrote:
>
>>> On Mon, Sep 14, 2015 at 3:38 PM, Kevin Layer wrote:
>>> > This whole branch of that conversation was about an error I got while
>>> > compiling 3.1.5 asdf.lisp on Windows. I no longer get that error.
>>>
>>> If you don't get
Faré wrote:
>> On Mon, Sep 14, 2015 at 3:38 PM, Kevin Layer wrote:
>> > This whole branch of that conversation was about an error I got while
>> > compiling 3.1.5 asdf.lisp on Windows. I no longer get that error.
>>
>> If you don't get this error — wonderful!
>>
>> Please proceed to the next s
On Mon, Sep 14, 2015 at 3:38 PM, Kevin Layer wrote:
> This whole branch of that conversation was about an error I got while
> compiling 3.1.5 asdf.lisp on Windows. I no longer get that error.
If you don't get this error — wonderful!
Please proceed to the next stage (this assumes the master bran
Faré wrote:
>> >>> On Mon, Sep 14, 2015 at 11:15 AM, Faré wrote:
>> >>> > On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer wrote:
>> >>> I suspect any problem Kevin had were related to Allegro somehow
>> >>> having
>> >>> (user-homedir-pathname) incorrectly returning NIL in their tes
>>> On Mon, Sep 14, 2015 at 11:15 AM, Faré wrote:
>>> > On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer wrote:
>>> I suspect any problem Kevin had were related to Allegro somehow having
>>> (user-homedir-pathname) incorrectly returning NIL in their test
>>> configuration.
>>> >>
>>> >
I'm in favor of 3.1.6 being HEAD on master. That way, I can make
patches for all platforms.
Kevin
Faré wrote:
>> On Mon, Sep 14, 2015 at 11:15 AM, Faré wrote:
>> > On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer wrote:
>> I suspect any problem Kevin had were related to Allegro somehow having
>> (user-homedir-pathname) incorrectly returning NIL in their test
>> configuration.
>> >
I'm able to compile ASDF 3.1.5.11 (what I get from HEAD on master) on
Windows with 10.0 GM.
When I try and run the test suite, I get:
$ export PATH=/c/acl100:$PATH
$ @thor[git:master]$ ALLEGRO=/c/acl100/alisp make t u l=allegro
ALLEGRO=/c/acl100/alisp
CL_SOURCE_REGISTRY=/home/layer/asdf/:/home/la
On Mon, Sep 14, 2015 at 11:15 AM, Faré wrote:
> On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer wrote:
I suspect any problem Kevin had were related to Allegro somehow having
(user-homedir-pathname) incorrectly returning NIL in their test
configuration.
>>
>> It's definitely not that:
On Mon, Sep 14, 2015 at 3:11 AM, Kevin Layer wrote:
>>> I suspect any problem Kevin had were related to Allegro somehow having
>>> (user-homedir-pathname) incorrectly returning NIL in their test
>>> configuration.
>
> It's definitely not that:
>
> ;; Current reader case mode: :case-sensitive-lower
Faré wrote:
>> >> Since there's a cache pathname bug on Windows in 3.1.5, I recommend
>> >> shipping with 3.1.5.7 (or 3.1.6, if we manage to ship faster than you
>> >> do).
>> >
>> > I would be happy to coordinate with you to release a 3.1.6 that is 3.1.5
>> > with fixes for Allegro (and whatever
>> Since there's a cache pathname bug on Windows in 3.1.5, I recommend
>> shipping with 3.1.5.7 (or 3.1.6, if we manage to ship faster than you
>> do).
>
> I would be happy to coordinate with you to release a 3.1.6 that is 3.1.5
> with fixes for Allegro (and whatever other fixes come along for the
On 9/11/15 Sep 11 -8:57 PM, Faré wrote:
[...snip...]
> Since there's a cache pathname bug on Windows in 3.1.5, I recommend
> shipping with 3.1.5.7 (or 3.1.6, if we manage to ship faster than you
> do).
I would be happy to coordinate with you to release a 3.1.6 that is 3.1.5
with fixes for Allegro
Dear Kevin,
On Fri, Sep 11, 2015 at 12:55 PM, Kevin Layer wrote:
> Hi, all. I had an spr with Faré, but I figure it's better to have
> this discussion on asdf-devel.
>
Yes, my apologies for not getting back to you. I had a very busy
couple of weeks at work, and debugging ASDF on Allegro/Windows
Hi, all. I had an spr with Faré, but I figure it's better to have
this discussion on asdf-devel.
First, as Faré pointed out, ACL was releasing non-release versions of
ASDF. I've rectified that, and I will be using the `release' branch
from now on.
Second, I can't build 3.1.5 on Windows. See be
29 matches
Mail list logo
