[EMAIL PROTECTED] writes:

> This does appear to be the Debian package sources, in which case you are
> attempting to build a Debian package.  The proper way to do that would
> be "dpkg-buildpackage -b -uc -rfakeroot", though
> "fakeroot debian/rules binary" will do fine too.  Make sure you've
> gotten all the Build-Depends from the debian/control file and
> the necessary development packages (dpkg-dev, devscripts, fakeroot).
> 
> I'm not exactly too sure what you managed to accomplish already.  However,
> you might want to consider installing like a normal Debian user would:
> apt-get install cmucl cmucl-normal cmucl-source.  If you really want
> to recompile the whole deal, then 'apt-get source cmucl' and see my
> instructions above.  You will, of course, need CMUCL to build it.
> 
> The point of the cmucl-source package is to contain CLX, gray-streams,
> and other things, as well as the source for debugging purposes.
> (or so I remember pvaneynde saying).

Thank you and everyone else who responded.  Indeed, when I used
"dpkg-buildpackage" compilation and installation worked fine.  I was
somewhat misleaded by the file cmucl-3.0.9/debian/README.debian where
it is said that "make" alone would be sufficient.  Maybe Peter could
add some more words how to install sources correctly with
dpkg-buildpackage (even if it was my error not knowing it:-)

The reason I recompiled CMUCL is that I have problems installing
matlisp (see http://sourceforge.net) which I suspect to arise from the
new CMUCL version (or bad installation of it on my machine).  When I
try to compile matlisp the compiling of the Fortran files works fine,
but linking with Lisp yields an error:

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
/usr/bin/lisp -noinit -eval '(progn (load "start.lisp"))'
; Loading #p"/usr/local/src/matlisp/start.lisp".
Converted SETLOGICALROOT.
Converted GETLOGICALROOT.
Converted DEFLOGICALPATH.
;; Loading #p"/usr/local/src/matlisp/system.dcl".
;; Loading #p"/usr/local/src/matlisp/config.lisp".


Error in function SYSTEM::LOAD-OBJECT-FILE:
   Can't open object "/tmp/29938AG0": "/usr/local/src/matlisp/lib/libmatlisp.so: 
undefined symbol: fstat"

Restarts:
  0: [CONTINUE] Return NIL from load of "start.lisp".
  1: [ABORT   ] Skip remaining initializations.

Debug  (type H for help)

(SYSTEM::LOAD-OBJECT-FILE "/tmp/29938AG0")
Source: Error finding source: 
Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:  Source file no longer exists:
  target:code/foreign.lisp.
0] 
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I asked on the matlisp list, and Raymond Toy replied:

> I'm also surprised that fstat is used by anything in matlisp.  I'm
> pretty sure none of LAPACK and friends knows or cares about files.
> It must be coming from either the lisp binary itself or -lg2c.
> Adding -lc should have fixed that.

> Maybe the lisp binary needs to be compiled with the export-dynamic
> (?)  switch.  I vaguely recall some discussion about this.

Does anyone on this list know what could be the problem?

Thank you very much.

Nicolas.

Reply via email to