Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#231 CLISP 2.33.2 fails to build on OSF/1 5.1

build problems
closed-works-for-me
Bruno Haible
clisp (525)
5
2004-10-11
2004-10-07
Nathan Froyd
No

I downloaded the CLISP 2.33.2 release from ftp.gnu.org and
attempted to build it with:

./configure --build dec-cc

on OSF1 V5.1 (a.k.a. Tru64). I am using the system C compiler,
cc, version 6.4-008. gcc is not available on this particular system.
The build fails when attempting to link lisp.run:

cc -O -DUNICODE -DDYNAMIC_FFI -DNO_GETTEXT -DNO_SIGSEGV
-I. spvw.o spvwtabf.o spvwtabs.o spvwtabo.o eval.o control.o
encoding.o pathname.o stream.o socket.o io.o array.o hashtabl.o
list.o package.o record.o sequence.o charstrg.o debug.o error.o
misc.o time.o predtype.o symbol.o lisparit.o i18n.o foreign.o
unixaux.o modules.o libcharset.o libavcall.o libcallback.a -ltermcap
-liconv -o lisp.run
ld:
Unresolved:
update
make: *** [lisp.run] Error 1

Checking the .o files with nm reveals that spvw.o is the object file
which contains the unresolved `update' function

Discussion

  • Sam Steingold
    Sam Steingold
    2004-10-10

    • assigned_to: sds --> haible
     
  • Sam Steingold
    Sam Steingold
    2004-10-10

    Logged In: YES
    user_id=5735

    update() is a macro, not a function in spvw.d
    if it does not defined, there is something deeply wrong.
    could you please try to figure out why it is not defined?

     
  • Bruno Haible
    Bruno Haible
    2004-10-11

    Logged In: YES
    user_id=5923

    On a machine with a slightly newer compiler ("cc -V" prints
    Compaq C V6.4-009 on Compaq Tru64 UNIX V5.1A (Rev. 1885)
    Compiler Driver V6.4-008 (sys) cc Driver
    ) there is no problem: lisp.run is linked without problems by the
    command
    cc -O -O -DUNICODE -DDYNAMIC_FFI -DNO_GETTEXT
    -DNO_SIGSEGV -I. spvw.o spvwtabf.o spvwtabs.o
    spvwtabo.o eval.o control.o encoding.o pathname.o stream.o
    socket.o io.o array.o hashtabl.o list.o package.o record.o
    sequence.o charstrg.o debug.o error.o misc.o time.o
    predtype.o symbol.o lisparit.o i18n.o foreign.o unixaux.o
    modules.o libcharset.a libavcall.a libcallback.a -ltermcap -liconv
    -o lisp.run

    So it looks like a preprocessor bug to me that should be fixed if
    you upgrade your C compiler.

    Or install a recent GCC.

     
  • Bruno Haible
    Bruno Haible
    2004-10-11

    • status: open --> closed-works-for-me