Status of clisp on Solaris/Sparc

View: New views
2 Messages — Rating Filter:   Alert me  

Status of clisp on Solaris/Sparc

by Christian Walther-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I'm currently trying to build Clisp 2.48 on Solaris 10/Sparc.
The result after several days of testing is that I'm unable to build
in every configuration I could think of. Before I dive into the
details I would like to ask if there are known issues with Solaris
10/Sparc?

My build environment is based on the OpenCSW packages to a large
degree. All dependencies (ffcall, sigsegv, etc...) are satisfied from
the repository.
The compilers I tried where the gcc supplied by the system
/usr/sfw/bin/gcc, and both /opt/csw/gcc3 and /opt/csw/gcc4. To
complete the collection I tried compiling Clisp 2.48 with SunStudio
12.1. The tools required for building (gmake, etc...) come from
/opt/csw/bin, too.

In all cases I used
export CPPFLAGS="-I/opt/csw/include -I/usr/include"
export LDFLAGS="-L/opt/csw/lib -L/lib -L/usr/lib"

With the Sunstudio compiler I used:
export CC="/opt/sunstudio12.1/bin/cc -m32"

Basically, when using the Sunstudio compiler it appears that there is
no valid selection of #defines, so that the build process fails
eventually.
This happens first in lispbibl.d, where alloca is declared through
gllib/alloca.h, but the next #ifdef is true, too, and declares it
directly as "extern void* alloca (int size);". The same happens in
clisp.h, too.
But there seems to be a bigger issue, because the build fails during
the link of spvw.o, where gc_sweep1_sstring_target is an undefined
symbol. Looking at the output I see the following warnings a bit
earlier:
"spvw_garcol.d", line 1166: warning: implicit function declaration:
gc_sweep1_sstring_forward
"spvw_garcol.d", line 1173: warning: implicit function declaration:
gc_sweep1_sstring_target

And indeed, looking at the code I see that both functions are only
used in case where HAS_SMALL_SSTRING is defined. And because I'm on
SPARC, this isn't the case. So the bottomline is that both functions
aren't defined, but still called later on. So IMO there is either
something wrong with HAS_SMALL_SSTRING or the cases in which it is
defined, or there is an #ifdef missing for every call to these
functions.

I'd really love to see Clisp running in my environment, because I'm
planning to use stumpwm while learning clisp. I ordered my copy of the
PCL book recently and I'm quite astonished by the language, its
features and beauty.

Regards
Christian Walther

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
clisp-list mailing list
clisp-list@...
https://lists.sourceforge.net/lists/listinfo/clisp-list

Re: Status of clisp on Solaris/Sparc

by Sam Steingold :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Christian Walther wrote:
> "spvw_garcol.d", line 1166: warning: implicit function declaration:
> gc_sweep1_sstring_forward
> "spvw_garcol.d", line 1173: warning: implicit function declaration:
> gc_sweep1_sstring_target

Vladimir has just fixed this in the CVS.
could you please try the cvs head?
thanks!

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
clisp-list mailing list
clisp-list@...
https://lists.sourceforge.net/lists/listinfo/clisp-list