From attila.lendvai at gmail.com Wed Nov 5 12:19:49 2008 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Wed, 5 Nov 2008 13:19:49 +0100 Subject: [closer-devel] loading closer-mop without fasls on sbcl. WAS: [asdf-devel] Eliminating the ACCEPT restart Message-ID: instead of cross-posting i forward this to closer-devel. ---------- Forwarded message ---------- From: Attila Lendvai Date: Wed, Nov 5, 2008 at 1:18 PM Subject: Re: [asdf-devel] Eliminating the ACCEPT restart To: leslie.polzer at gmx.net Cc: asdf-devel at common-lisp.net > The ACCEPT restart of ASDF is terribly confusing to > newbies. It's very tempting to just hit it and go on. > > How about removing it? Are there really situations > in which one can set the creation of a vital object > file aside? try loading closer-mop from fresh sources on sbcl, so that it also compiles before loading. the asdf:load-op will stop with some warnings about already exported symbols (probably due to redefining a package). without the accept restart, i'd have to C-c and start over building my image. -- attila ps: this should be fixed in closer-mop, but still... From pc at p-cos.net Wed Nov 5 19:58:44 2008 From: pc at p-cos.net (Pascal Costanza) Date: Wed, 5 Nov 2008 20:58:44 +0100 Subject: [closer-devel] loading closer-mop without fasls on sbcl. WAS: [asdf-devel] Eliminating the ACCEPT restart In-Reply-To: References: Message-ID: <5C69D4A7-1A1C-4F0A-AE9D-DD16892C1E07@p-cos.net> Hi Attila, Thanks a lot for reporting problems with Closer to MOP. However, I cannot reproduce this. If I delete all the fasls from Closer to MOP, I don't get any errors on asdf:load-op, they will just get compiled and loaded without any further interruptions. Can you post the error messages, so I have a better idea about the details? Pascal On 5 Nov 2008, at 13:19, Attila Lendvai wrote: > instead of cross-posting i forward this to closer-devel. > > > ---------- Forwarded message ---------- > From: Attila Lendvai > Date: Wed, Nov 5, 2008 at 1:18 PM > Subject: Re: [asdf-devel] Eliminating the ACCEPT restart > To: leslie.polzer at gmx.net > Cc: asdf-devel at common-lisp.net > > >> The ACCEPT restart of ASDF is terribly confusing to >> newbies. It's very tempting to just hit it and go on. >> >> How about removing it? Are there really situations >> in which one can set the creation of a vital object >> file aside? > > try loading closer-mop from fresh sources on sbcl, so that it also > compiles before loading. > > the asdf:load-op will stop with some warnings about already exported > symbols (probably due to redefining a package). without the accept > restart, i'd have to C-c and start over building my image. > > -- > attila > > ps: this should be fixed in closer-mop, but still... > > _______________________________________________ > closer-devel mailing list > closer-devel at common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/closer-devel -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium From attila.lendvai at gmail.com Thu Nov 6 01:03:28 2008 From: attila.lendvai at gmail.com (Attila Lendvai) Date: Thu, 6 Nov 2008 02:03:28 +0100 Subject: [closer-devel] loading closer-mop without fasls on sbcl. WAS: [asdf-devel] Eliminating the ACCEPT restart In-Reply-To: <5C69D4A7-1A1C-4F0A-AE9D-DD16892C1E07@p-cos.net> References: <5C69D4A7-1A1C-4F0A-AE9D-DD16892C1E07@p-cos.net> Message-ID: > reproduce this. If I delete all the fasls from Closer to MOP, I don't get > any errors on asdf:load-op, they will just get compiled and loaded without > any further interruptions. > > Can you post the error messages, so I have a better idea about the details? hm, i felt i should double check this before sending... i can't reproduce it either when simply load-op'ing closer-mop, or through contextl as a dependency. it only comes up in our image building code, and that can also be fixed by explicitly load-op'ing closer-mop before it's loaded as a dependency. i think this is just an unwelcome sideeffect of asdf-system-connections, and i've found a way to sidestep my problem... so, sorry for the noise! -- attila From pc at p-cos.net Thu Nov 6 11:52:14 2008 From: pc at p-cos.net (Pascal Costanza) Date: Thu, 6 Nov 2008 12:52:14 +0100 Subject: [closer-devel] loading closer-mop without fasls on sbcl. WAS: [asdf-devel] Eliminating the ACCEPT restart In-Reply-To: References: <5C69D4A7-1A1C-4F0A-AE9D-DD16892C1E07@p-cos.net> Message-ID: <68F79E08-BE1D-40EE-9495-FDF74BB90601@p-cos.net> On 6 Nov 2008, at 02:03, Attila Lendvai wrote: >> reproduce this. If I delete all the fasls from Closer to MOP, I >> don't get >> any errors on asdf:load-op, they will just get compiled and loaded >> without >> any further interruptions. >> >> Can you post the error messages, so I have a better idea about the >> details? > > hm, i felt i should double check this before sending... > > i can't reproduce it either when simply load-op'ing closer-mop, or > through contextl as a dependency. it only comes up in our image > building code, and that can also be fixed by explicitly load-op'ing > closer-mop before it's loaded as a dependency. > > i think this is just an unwelcome sideeffect of > asdf-system-connections, and i've found a way to sidestep my > problem... so, sorry for the noise! Don't worry. It's better you send a bug report that turns out to be none than the other way around. (Yeah, this sentence doesn't make any sense, but you get the idea... ;) Pascal -- Pascal Costanza, mailto:pc at p-cos.net, http://p-cos.net Vrije Universiteit Brussel, Programming Technology Lab Pleinlaan 2, B-1050 Brussel, Belgium