out of date portable aserve?

My first day experimenting with QuickLisp on Allegro and LispWorks (PC
and Mac) I ran into WITHOUT-PREEMPTION compilation failures with
portableaserve.

These went away when I replaced the files QL downloaded
(portableaserve-20101006-cvs) with the tarball retrieved by
http://portableaserve.cvs.sourceforge.net/viewvc/portableaserve/portableaserve/?view=tar

Re: out of date portable aserve?

Chris <chris.riesbeck@...> writes:

> My first day experimenting with QuickLisp on Allegro and LispWorks (PC
> and Mac) I ran into WITHOUT-PREEMPTION compilation failures with
> portableaserve.
>
> These went away when I replaced the files QL downloaded
> (portableaserve-20101006-cvs) with the tarball retrieved by
> http://portableaserve.cvs.sourceforge.net/viewvc/portableaserve/portableaserve/?view=tar

Quicklisp updates happen about once per month, and there have been
portableaserve changes since the last update. The next Quicklisp update,
which will happen in a week or two, will incorporate the changes.

Zach

problem with f2cl?

Hello!

When loading f2cl alone, everything works well:

CL-USER> (ql:quickload :f2cl)
To load "f2cl":
  Load 1 ASDF system:
    f2cl
; Loading "f2cl"
[package f2cl-lib]................................
[package fortran-to-lisp].........................
..................................................
.....................
(:F2CL)
CL-USER> (ql-dist:ensure-installed (ql-dist:find-system "f2cl"))
#<SYSTEM f2cl / f2cl-20110619-hg / quicklisp 2011-06-19>
CL-USER> (ql-dist:find-release "f2cl")
#<RELEASE f2cl-20110619-hg / quicklisp 2011-06-19>

However, when installing everything, it fails, seemingly on f2cl:

CL-USER> (quick-install-all)
> Debug: FIND-SYSTEM-IN-DIST returned NIL but I expected one of (#<SYSTEM toms717-tests /
#1=f2cl-20110619-hg / quicklisp 2011-06-19> #<SYSTEM toms717 / #1# / quicklisp 2011-06-19> #<SYSTEM
toms419-test / #1# / quicklisp 2011-06-19> #<SYSTEM toms419 / #1# / quicklisp 2011-06-19> #<SYSTEM
quadpack-tests / #1# / quicklisp 2011-06-19> #<SYSTEM quadpack / #1# / quicklisp 2011-06-19> #<SYSTEM
minpack-tests-lmdif / #1# / quicklisp 2011-06-19> #<SYSTEM minpack-tests-hybrd / #1# / quicklisp
2011-06-19> #<SYSTEM minpack / #1# / quicklisp 2011-06-19> #<SYSTEM machar / #1# / quicklisp
2011-06-19> #<SYSTEM mach-par / #1# / quicklisp 2011-06-19> #<SYSTEM mach-par / #1# / quicklisp
2011-06-19> #<SYSTEM hompack-test-mains / #1# / quicklisp 2011-06-19> #<SYSTEM hompack-test-mainp /

quick-install-all

I forgot to give the definition of quick-install-all in my "problem
with f2cl?" message:

(defun quick-update ()
  (ql:update-client)
  (ql:update-all-dists)) 

(defun quick-clean ()
  (map nil 'ql-dist:clean (ql-dist:enabled-dists)))

(defun quick-install-all ()
  (map nil 'ql-dist:ensure-installed (ql-dist:provided-systems t)))

(defun quick-uninstall (&rest systems)
  (map 'list (lambda (system) (ql-dist:uninstall (ql-dist:release system)))
       systems))

--

-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
A bad day in () is better than a good day in {}.

Re: problem with f2cl?

pjb@... (Pascal J. Bourguignon) writes:

> Hello!
>
> When loading f2cl alone, everything works well:
[snip]
> However, when installing everything, it fails, seemingly on f2cl:

Yes, there is a known problem with f2cl's metadata in systems.txt and
releases.txt. I hope to fix it within a week or so for a new dist
update.

GBBopen also has an issue I hope to fix at the same time.

Zach

re: Error while trying to install lispbuilder-sdl

Was there ever a resolution to this? I make'd cocoahelper but still
get the same error. In LW 6 Pro:

1 > (probe-file (asdf:system-relative-pathname 'lispbuilder-sdl
"cocoahelper/cocoahelper.dylib"))
; Loading text file ~/lisp/quicklisp/dists/quicklisp/software/
lispbuilder-20110619-svn/lispbuilder-sdl/lispbuilder-sdl.asd
#P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
lispbuilder-sdl/cocoahelper/cocoahelper.dylib"

2 > (asdf:system-source-directory 'lispbuilder-sdl)
#P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
lispbuilder-sdl/"

I was able to get cocoahelper running by downloading it in framework
form but the examples were unresponsive, so I'd like to do it via the
generated dylib instead.

Thank you

On Jan 14, 11:22 am, Zach Beane <x...@...> wrote:
> Andrea <andrea.sto...@...> writes:
> > Guys,
>
> > I have tried to install lispbuilder-sdlseveral times from quicklisp,
> > and I always run into a similar error:
>
> > * (ql:quickload "lispbuilder-sdl")
> > To load "lispbuilder-sdl":
> >   Load 1 ASDF system:

Re: re: Error while trying to install lispbuilder-sdl

Re: Error while trying to install lispbuilder-sdl

I wanted to verify that the unresponsiveness problem wasn't related to
the potentially out of date framework I was using. Either way, I
haven't been able to actually get it running through quicklisp.

Thanks

On Jul 17, 2:47 pm, Elliott Slaughter <elliottslaugh...@...>
wrote:
> On Sun, Jul 17, 2011 at 11:27 AM, Kordova <kord...@...> wrote:
> > Was there ever a resolution to this? I make'd cocoahelper but still
> > get the same error. In LW 6 Pro:
>
> > 1 > (probe-file (asdf:system-relative-pathname 'lispbuilder-sdl
> > "cocoahelper/cocoahelper.dylib"))
> > ; Loading text file ~/lisp/quicklisp/dists/quicklisp/software/
> > lispbuilder-20110619-svn/lispbuilder-sdl/lispbuilder-sdl.asd
> > #P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
> > lispbuilder-sdl/cocoahelper/cocoahelper.dylib"
>
> > 2 > (asdf:system-source-directory 'lispbuilder-sdl)
> > #P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
> > lispbuilder-sdl/"
>
> > I was able to get cocoahelper running by downloading it in framework
> > form but the examples were unresponsive, so I'd like to do it via the
> > generated dylib instead.
>
> That doesn't sound like the same error to me; assuming that "unresponsive"
> means "the example started but mouse/keyboard input didn't work", as opposed
> to "the example threw an exception". If so, there are larger issues going on
> here, and I suggest taking them to the Lispbuilder mailing list (see below).
> Alternatively, try SBCL and see if you get the same error. (There are some
> known implementation-specific issues in cocoahelper.)
>
> http://groups.google.com/group/lispbuilder
>
> Thank you
>
>
>
>
>
>
>
>
>
>
>
> > On Jan 14, 11:22 am, Zach Beane <x...@...> wrote:
> > > Andrea <andrea.sto...@...> writes:
> > > > Guys,
>
> > > > I have tried to install lispbuilder-sdlseveral times from quicklisp,
> > > > and I always run into a similar error:
>
> > > > * (ql:quickload "lispbuilder-sdl")
> > > > To load "lispbuilder-sdl":
> > > >   Load 1 ASDF system:
> > > >     lispbuilder-sdl
> > > > ; Loading "lispbuilder-sdl"
>
> > > > debugger invoked on a LOAD-FOREIGN-LIBRARY-ERROR:
> > > >   Unable to load any of the alternatives:
> > > >    ((:FRAMEWORK "cocoahelper") (:DEFAULT "cocoahelper"))
>
> > > > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>
> > > > restarts (invokable by number or by possibly-abbreviated name):
> > > >   0: [RETRY          ] Try loading the foreign library again.
> > > >   1: [USE-VALUE      ] Use another library instead.
> > > >   2: [TRY-RECOMPILING] Recompile cocoahelper and try loading it again
> > > >   3: [RETRY          ] Retry
> > > >                        loading component ("cocoahelper" "cocoahelper"
> > > > "cocoahelper").
> > > >   4: [ACCEPT         ] Continue, treating
> > > >                        loading component ("cocoahelper" "cocoahelper"
> > > > "cocoahelper")
> > > >                        as having been successful.
> > > >   5: [ABORT          ] Give up on "lispbuilder-sdl"
> > > >   6:                   Exit debugger, returning to top level.
>
> > > > (CFFI::FL-ERROR "Unable to load any of the alternatives:~%   ~S")
> > > > [:EXTERNAL]
> > > > 0]
>
> > > > I did try Zach's suggestion (cd in ~/quicklisp/.../cocoahelper, then
> > > > make) but it did not change a single thing.  Does any of you have any
> > > > idea what could be the cause?
>
> > > Hmm, that is weird. I would expect the "make" bit to succeed. What do
> > > you get back from this?
>
> > >   (probe-file (asdf:system-relative-pathname 'lispbuilder-sdl
>
> >  "cocoahelper/cocoahelper.dylib"))
>
> > > Or this:
>
> > >   (asdf:system-source-directory 'lispbuilder-sdl)
>
> > > Zach
>
> --
> Elliott Slaughter
>
> "Don't worry about what anybody else is going to do. The best way to predict
> the future is to invent it." - Alan Kay

Re: Re: Error while trying to install lispbuilder-sdl

Re: Error while trying to install lispbuilder-sdl

Yes, that's fair. I'd still like to know why the lib isn't loaded
correctly from quicklisp, but I'll direct my other issue to the
lispbuilder mailing list.

Thank you.

On Jul 18, 12:39 am, Elliott Slaughter <elliottslaugh...@...>
wrote:
> On Sun, Jul 17, 2011 at 1:43 PM, Kordova <kord...@...> wrote:
> > I wanted to verify that the unresponsiveness problem wasn't related to
> > the potentially out of date framework I was using.
>
> I am not aware of any version incompatibility issues (other than obvious
> things like 32-bit vs 64-bit architectures).
>
> Again, I'm not sure what "unresponsiveness" means. If you are getting a
> crash identical to the one in the original quoted message, than that
> probably means either:
>
> 1. Lisp can't find the dylib/framework.
> 2. Lisp is 32-bit while the dylib/framework is 64-bit (or vice versa).
> 3. A library which cocoahelper depends on (i.e. SDL) either can't be found
> or is built for an incompatible architecture.
>
> If you are not seeing a crash, but instead see the window freeze up, or
> something else, then I'll need to know what that is before I can help.
>
> Either way, I
>
> > haven't been able to actually get it running through quicklisp.
>
> I think Quicklisp is probably not the problem. (I have used Quicklisp with
> the Lispbuilder-provided binaries for some time without trouble.)
>
> If you continue to have trouble with this, I recommend taking it to the
> Lispbuilder list, and maybe report back here when you find the solution.
>
> It would also be helpful to know the OS version, C compiler version, Lisp
> version and architecture, dylib/framework and architecture, where you got
> SDL from, and where you've put all the files on your system.
>
> Thanks
>
>
>
>
>
>
>
> > On Jul 17, 2:47 pm, Elliott Slaughter <elliottslaugh...@...>
> > wrote:
> > > On Sun, Jul 17, 2011 at 11:27 AM, Kordova <kord...@...> wrote:
> > > > Was there ever a resolution to this? I make'd cocoahelper but still
> > > > get the same error. In LW 6 Pro:
>
> > > > 1 > (probe-file (asdf:system-relative-pathname 'lispbuilder-sdl
> > > > "cocoahelper/cocoahelper.dylib"))
> > > > ; Loading text file ~/lisp/quicklisp/dists/quicklisp/software/
> > > > lispbuilder-20110619-svn/lispbuilder-sdl/lispbuilder-sdl.asd
> > > > #P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
> > > > lispbuilder-sdl/cocoahelper/cocoahelper.dylib"
>
> > > > 2 > (asdf:system-source-directory 'lispbuilder-sdl)
> > > > #P"~/lisp/quicklisp/dists/quicklisp/software/lispbuilder-20110619-svn/
> > > > lispbuilder-sdl/"
>
> > > > I was able to get cocoahelper running by downloading it in framework
> > > > form but the examples were unresponsive, so I'd like to do it via the
> > > > generated dylib instead.
>
> > > That doesn't sound like the same error to me; assuming that
> > "unresponsive"
> > > means "the example started but mouse/keyboard input didn't work", as
> > opposed
> > > to "the example threw an exception". If so, there are larger issues going
> > on
> > > here, and I suggest taking them to the Lispbuilder mailing list (see
> > below).
> > > Alternatively, try SBCL and see if you get the same error. (There are
> > some
> > > known implementation-specific issues in cocoahelper.)
>
> > >http://groups.google.com/group/lispbuilder
>
> > > Thank you
>
> > > > On Jan 14, 11:22 am, Zach Beane <x...@...> wrote:
> > > > > Andrea <andrea.sto...@...> writes:
> > > > > > Guys,
>
> > > > > > I have tried to install lispbuilder-sdlseveral times from
> > quicklisp,
> > > > > > and I always run into a similar error:
>
> > > > > > * (ql:quickload "lispbuilder-sdl")
> > > > > > To load "lispbuilder-sdl":
> > > > > >   Load 1 ASDF system:
> > > > > >     lispbuilder-sdl
> > > > > > ; Loading "lispbuilder-sdl"
>
> > > > > > debugger invoked on a LOAD-FOREIGN-LIBRARY-ERROR:
> > > > > >   Unable to load any of the alternatives:
> > > > > >    ((:FRAMEWORK "cocoahelper") (:DEFAULT "cocoahelper"))
>
> > > > > > Type HELP for debugger help, or (SB-EXT:QUIT) to exit from SBCL.
>
> > > > > > restarts (invokable by number or by possibly-abbreviated name):
> > > > > >   0: [RETRY          ] Try loading the foreign library again.
> > > > > >   1: [USE-VALUE      ] Use another library instead.
> > > > > >   2: [TRY-RECOMPILING] Recompile cocoahelper and try loading it
> > again
> > > > > >   3: [RETRY          ] Retry
> > > > > >                        loading component ("cocoahelper"
> > "cocoahelper"
> > > > > > "cocoahelper").
> > > > > >   4: [ACCEPT         ] Continue, treating
> > > > > >                        loading component ("cocoahelper"
> > "cocoahelper"
> > > > > > "cocoahelper")
> > > > > >                        as having been successful.
> > > > > >   5: [ABORT          ] Give up on "lispbuilder-sdl"
> > > > > >   6:                   Exit debugger, returning to top level.
>
> > > > > > (CFFI::FL-ERROR "Unable to load any of the alternatives:~%   ~S")
> > > > > > [:EXTERNAL]
> > > > > > 0]
>
> > > > > > I did try Zach's suggestion (cd in ~/quicklisp/.../cocoahelper,
> > then
> > > > > > make) but it did not change a single thing.  Does any of you have
> > any
> > > > > > idea what could be the cause?
>
> > > > > Hmm, that is weird. I would expect the "make" bit to succeed. What do
> > > > > you get back from this?
>
> > > > >   (probe-file (asdf:system-relative-pathname 'lispbuilder-sdl
>
> > > >  "cocoahelper/cocoahelper.dylib"))
>
> > > > > Or this:
>
> > > > >   (asdf:system-source-directory 'lispbuilder-sdl)
>
> > > > > Zach
>
> > > --
> > > Elliott Slaughter
>
> > > "Don't worry about what anybody else is going to do. The best way to
> > predict
> > > the future is to invent it." - Alan Kay
>
> --
> Elliott Slaughter
>
> "Don't worry about what anybody else is going to do. The best way to predict
> the future is to invent it." - Alan Kay