On Mon, Sep 15, 2014 at 4:35 PM, Faré <fah...@gmail.com> wrote: > On Fri, Sep 12, 2014 at 11:30 AM, Faré <fah...@gmail.com> wrote: >> On Fri, Sep 12, 2014 at 10:03 AM, Camm Maguire <c...@maguirefamily.org> >> wrote: >>> Greetings, and thanks for your patience! I have not forgotten about >>> you! >>> > >> I had defpackage woes before on GCL, and that looks like a regression, >> although I haven't recorded which combination of GCL and ASDF worked >> before — or whether indeed it was plainly loading asdf.o. >> > It looks like the issue has to do with the compilation settings. > > When I compile ASDF with the default compilation settings, the > define-package setup fails. But somehow, when the test suite compiles > it, it works (!), yet when I modify the install-asdf.lisp script to do > what looks like the same thing that script-support.lisp does, it still > doesn't work(!). I'm somewhat baffled, and will have to try again when > I have more time. > I can't figure it out. How in GCL do I introspect the system to determine all the variables that matter during compilation, including the optimize settings?
Actually, it looks like it works when compiling with plain compile-file before having loaded asdf, but fails when using compile-file* after having loaded asdf. I suspect that the key element is "after having loaded asdf", at which point the package exists during compilation, and somehow gcl may be failing to record some instructions pertaining to creating the packages. —♯ƒ • François-René ÐVB Rideau •Reflection&Cybernethics• http://fare.tunes.org When you are young you are afraid people will steal your ideas; when you are old you are afraid they won't. — David D. Friedman _______________________________________________ Gcl-devel mailing list Gcl-devel@gnu.org https://lists.gnu.org/mailman/listinfo/gcl-devel
