Re: Got my name in the list

Vladimir Tzankov <[email protected]>
Newsgroups gmane.lisp.clisp.devel
Message-ID <CAHWYE6JROh_m00pU5a9x6-2CP8w_wcZ1eP+JqhfXY94RyxjGgQ@mail.gmail.com>
Compo, Don,

'hg pull' and check that MT build is good now - tested on osx and
linux-amd64. No need for --enable-portability. There was a problem with
initialization of special variables bindings.

I'm experiencing check-tests failures on socket tests both on single and
multithread builds. Will investigate further.

--
 vlad



On Fri, May 19, 2017 at 8:58 AM, Don Cohen <don-sourceforge-x2012@isis.
cs3-inc.com> wrote:

> Compro Prasad writes:
>
>  > MT builds successful only with --enable-portability but running
>  > clisp binary segfaults.
>
> More detail would help.
> This is how my transcript ends:
>
>   gcc -m64 -g -O2 -W -Wswitch -Wcomment -Wpointer-arith -Wreturn-type
> -Wmissing-declarations -Wimplicit -Wno-sign-compare -Wno-format-nonliteral
> -Wno-shift-negative-value -fwrapv -pthread -fno-strict-aliasing -ggdb -O0
> -DDEBUG_OS_ERROR -DDEBUG_SPVW -DDEBUG_BYTECODE -DSAFETY=3 -DENABLE_UNICODE
> -DMULTITHREAD -DPOSIX_THREADS -DNO_TERMCAP_NCURSES -DDYNAMIC_FFI
> -DDYNAMIC_MODULES  -Wl,--export-dynamic spvw.o spvwtabf.o spvwtabs.o
> spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o
> funarg.o array.o hashtabl.o list.o package.o record.o weak.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 zthread.o built.o modules.o libgnu.a  -ldl
> /usr/local/lib/libavcall.a /usr/local/lib/libcallback.a
> /usr/local/lib64/libsigsegv.a -lc  -o lisp.run
>   ./lisp.run -B . -N locale -E UTF-8 -Emisc 1:1 -Epathname 1:1 -norc -m
> 2MW -lp ../src/ -x '(and (load "../src/init.lisp") (sys::%saveinitmem)
> (ext::exit)) (ext::exit t)'
>   Makefile:1423: recipe for target 'interpreted.mem' failed
>   make: *** [interpreted.mem] Segmentation fault (core dumped)
>
> Is that what happens to you?
>
>  > > As I've posted recently, this fails for many of the memory models,
> inc.
>  > > whichever is the default on my current system (linux).
>  > > I suggest starting with Makefile.devel (is that part of the hg
> source?),
>
> Do you have Makefile.devel ?
>
>  > > finding the line that says
>  > >  # Options to pass to configure
>  > > and changing the next line to
>  > >  MULTIBUILD_OPTIONS =  --with-threads=POSIX_THREADS
>  > > storing the result as Makefile.develMT
>  > > then
>  > >  make -f Makefile.develMT -k multibuild-porting64-gcc
>  > > in order to at least find SOME way to build MT.
>
> In other words, I hope this is going to show you what other config
> options you can use to get an mt image to work.
>
>

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
clisp-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/clisp-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.