clisp-devel — closed list for developers and testers

Help regarding solving bug

[Deepak S. <dee...@gm...>]

Hello,

I'm newbie to CLISP. I found bug on savannah regarding CLISP that,
when va_start_struct and va_return* are used in clisp/src/foreign.d,
GCC issues warnings. Here is the link
http://savannah.gnu.org/bugs/?22035.

I need your help regarding solving this bug, how do I get started with it.
Thank you.

-- 
Deepak Kumar Sharma
Blog:
http://deekysharma.wordpress.com

Re: help on building clisp

[Vladimir T. <vtz...@gm...>]

On Wed, Mar 12, 2014 at 11:05 PM, shashank <sha...@gm...> wrote:
> I have a few question to ask:
> 1. How does the program interact with lisp and c while building it?
Can you clarify?

> 2. What is NOT thread-safe in CLisp? vs what is thread-safe in clisp?
> 3. Is there a list of things that is known to be threadsafe ?
As wikipedia states:  A piece of code is thread-safe if it only
manipulates shared data structures in a manner that guarantees safe
execution by multiple threads at the same time.
We may argue what is "safe execution" so let's narrow it to: clisp
does not crash/segfault.
Having this 'definition' I may say that most of the clisp runtime is
thread safe - clisp will not crash but depending on the access
patterns you may not always get what you expect unless synchronisation
primitives are used (mutexes and exemptions).

Hashtables are the only (known to me) standard datatype that causes
segfaults when manipulated from multiple threads.

> 4. The project page says "Finish a multi-threading interface", so what all
> things am I looking into working with?
>     Is it just how clisp is built or is it also related to the internal
> workings of clisp.

Hashtable implementation should not cause segfaults when accesses from
multiple threads. There are two approaches:
A. using sync primitives (SBCL has/had this)
B. using lock free implementation (ClozureCL has implementation).

IMO, both ways require more or less same efforts to be implemented but
the latter is more 'scalable'.

> 5. Should I brush up my lisp? since i guess I will need to work with lisp
> code.
Most of the work should be done in plain old C.

> All in all, can you guys narrow me down as to what I will be working on?
Roughly: lock free hash table that is drop in replacement of current
implementation :).
Note that there are also weak hashtables:
http://clisp.org/impnotes/weak.html#weak-ht

Vlad

Re: help on building clisp

[shashank <sha...@gm...>]

Hi,

Thanks for the info.
As Sam and you both mentioned I am reading the code and documentation in
"hashtable.d" file.

> Hash tables are used in both lisp and c code - to get an impression do
> simple grep for: make-hash-table (and make_hash_table), gethash, etc.
> I would recommend you to get common with clisp internals -
> http://clisp.org/impnotes/internals.html is a good start.

I searched for make-hash-table and gethash and basically *hash* inside the
project folder and I found numerous references to them.
It is scary, I believe this is due to Clos using hash tables internally.
Clisp internals look like a good place to start.

I have a few question to ask:
1. How does the program interact with lisp and c while building it?
2. What is NOT thread-safe in CLisp? vs what is thread-safe in clisp?
3. Is there a list of things that is known to be threadsafe ?
4. The project page<http://www.gnu.org/software/soc-projects/ideas-2014.html>says
"Finish a multi-threading interface", so what all things am I looking
into working with?
    Is it just how clisp is built or is it also related to the internal
workings of clisp.
5. Should I brush up my lisp? since i guess I will need to work with lisp
code.

I think some of my questions will be answered as I get familiar with clisp
internals <http://clisp.org/impnotes/internals.html>.
All in all, can you guys narrow me down as to what I will be working on?
This will help me form a better idea of hashtable and its usage in clisp,
and how a lockfree version will benefit the software.
It is necessary that I understand the concept.

Thanks in advance



On Wed, Mar 12, 2014 at 2:06 AM, Vladimir Tzankov <vtz...@gm...>wrote:

> Hey Shashank,
> Thanks for interest in clisp.
> > $ ./configure --with-threads=POSIX_THREADS
>
> This is the normal way to configure clisp with threads.
>
> > Later, the execution of `make` and `make check` commands also occurs
> > successfully (with huge amount of execution steps being flushed out on
> the
> > terminal).
>
> `make` should build successfully clisp.
> `make check` usually segfaults in multi thread builds (you were lucky)
> mostly due to non thread safe hash tables.
>
> > Can you guide me as to how I shall proceed in this regard. Also, how and
> > where the CLISP hash table implementation is used, which in turn should
> be
> > replaced by a lock-free implementation.
>
> The hash table implementation is located in src/hashtabl.d. Hash
> tables are used in both lisp and c code - to get an impression do
> simple grep for: make-hash-table (and make_hash_table), gethash, etc.
> I would recommend you to get common with clisp internals -
> http://clisp.org/impnotes/internals.html is a good start.
>
> Vlad
>

Re: help on building clisp

[Jerry J. <log...@gm...>]

On Wed, Mar 12, 2014 at 2:17 PM, shashank <sha...@gm...> wrote:

> >>    3.   readline:   no (user requested: default)
> > what is your platform that it lacks readline?
> I run Ubuntu 13.04 on a Intel i5 machine though I don't know why the
> program said that my system lacks readline.
>

You are probably missing the developer files.  Install libreadline-dev, or
libreadline-gplv2-dev if you don't want to mix the GPLv2 clisp with the
GPLv3 libreadline.
-- 
Jerry James
http://www.jamezone.org/

Re: help on building clisp

[shashank <sha...@gm...>]

Hey!

Thanks for the tip.

> What made you think that this command does anything useful?
well I was fumbling around and I thought make files should yield something.
Turns out it does something else but I wanted to know why it running "make
-f Makefile.devel" gave me an error?

> ISTR that you also expressed interest in libffcall - you might want to
> start with building and installing it.
I was thinking of sticking to clisp itself, but I will definitely look into
it. Thanks ;)

>>    3.   readline:   no (user requested: default)
> what is your platform that it lacks readline?
I run Ubuntu 13.04 on a Intel i5 machine though I don't know why the
program said that my system lacks readline.

> "make check" either prints "tests passed" or instructions on where to
> find the failures (see tests/*.erg)

I carefully inspected each step this time while running "make check". And
there was just this one single error
in the "src/tests/backquot.erg" file.  I suspect if it is an error I should
expect.





On Wed, Mar 12, 2014 at 2:01 AM, Sam Steingold <sd...@gn...> wrote:

> Hi,
>
> > * shashank <fun...@tz...> [2014-03-12 01:20:56 +0500]:
> >
> > I am Shashank (a gsoc aspirant) and I have been trying to build clisp
> > however I can't seem to progress.
> > I have cloned the mercuial repository from here -
> > http://sourceforge.net/p/clisp/clisp/ci/default/tree/doc/
> >
> > In an earlier exchange of email, Sam Steingold asked me to:
> >> Clone the clisp mercurial repo and build from it with threads.
> >> Observe the crashes in the tests.
> >> Investigate how you would replace the CLISP hash table implementation
> >> with the lock-free one.
> >
> > However as soon as I do :
> >
> >
> >    1. $ make -f Makefile.devel CFLAGS=MULTITHREAD
> >
> >
> > I get this error :     (The complete stacktrace is
> > here<http://pastebin.com/PpHsT1vU>
> > )
> >
> >
> >    1. find: `@srcdir@\\..\\modules\\': No such file or directory
>
> What made you think that this command does anything useful? :-)
>
> > So I tried build using configure
> >
> >    1. $ ./configure --with-threads=POSIX_THREADS
> >
> > the command runs successfully and in the end, I get the following
> >
> >
> >    1. Configure findings:
> >    2.   FFI:        no (user requested: default)
>
> ISTR that you also expressed interest in libffcall - you might want to
> start with building and installing it.
>
> >    3.   readline:   no (user requested: default)
>
> what is your platform that it lacks readline?
>
> >    4. libsigsegv: yes
> >    5. ./makemake  --with-threads=POSIX_THREADS  > Makefile
> >    6. make: `config.lisp` is up to date.
> >    7.
> >    8. To continue building CLISP, the following commands are recommended
> >    9.   (cf. unix/INSTALL step 4 ff):
> >    10.     cd src
> >    11.     vi config.lisp
> >    12.     make
> >    13.     make check
>
> you could also wrap the whole thing in one command, by passing "--cbc"
> (config/build/check) to configure.
>
> > However, I can't possibly seem to locate errors while building with
> > threads, although I may be wrong in execution or looking at the wrong
>
> "make check" either prints "tests passed" or instructions on where to
> find the failures (see tests/*.erg)
>
> > place.  Can you guide me as to how I shall proceed in this
> > regard. Also, how and where the CLISP hash table implementation is
> > used, which in turn should be replaced by a lock-free implementation.
>
> See clisp/src/hashtbl.d for the hash table implementation.
>
> --
> Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1265
> http://www.childpsy.net/ http://pmw.org.il http://openvotingconsortium.org
> http://jihadwatch.org http://islamexposedonline.com
> Feynman: 'Philosophy of science is as useful to scientists as ornithology
> is to birds'
>

Re: help on building clisp

[Vladimir T. <vtz...@gm...>]

Hey Shashank,
Thanks for interest in clisp.
> $ ./configure --with-threads=POSIX_THREADS

This is the normal way to configure clisp with threads.

> Later, the execution of `make` and `make check` commands also occurs
> successfully (with huge amount of execution steps being flushed out on the
> terminal).

`make` should build successfully clisp.
`make check` usually segfaults in multi thread builds (you were lucky)
mostly due to non thread safe hash tables.

> Can you guide me as to how I shall proceed in this regard. Also, how and
> where the CLISP hash table implementation is used, which in turn should be
> replaced by a lock-free implementation.

The hash table implementation is located in src/hashtabl.d. Hash
tables are used in both lisp and c code - to get an impression do
simple grep for: make-hash-table (and make_hash_table), gethash, etc.
I would recommend you to get common with clisp internals -
http://clisp.org/impnotes/internals.html is a good start.

Vlad

Re: help on building clisp

[Sam S. <sd...@gn...>]

Hi,

> * shashank <fun...@tz...> [2014-03-12 01:20:56 +0500]:
>
> I am Shashank (a gsoc aspirant) and I have been trying to build clisp
> however I can't seem to progress.
> I have cloned the mercuial repository from here -
> http://sourceforge.net/p/clisp/clisp/ci/default/tree/doc/
>
> In an earlier exchange of email, Sam Steingold asked me to:
>> Clone the clisp mercurial repo and build from it with threads.
>> Observe the crashes in the tests.
>> Investigate how you would replace the CLISP hash table implementation
>> with the lock-free one.
>
> However as soon as I do :
>
>
>    1. $ make -f Makefile.devel CFLAGS=MULTITHREAD
>
>
> I get this error :     (The complete stacktrace is
> here<http://pastebin.com/PpHsT1vU>
> )
>
>
>    1. find: `@srcdir@\\..\\modules\\': No such file or directory

What made you think that this command does anything useful? :-)

> So I tried build using configure
>
>    1. $ ./configure --with-threads=POSIX_THREADS
>
> the command runs successfully and in the end, I get the following
>
>
>    1. Configure findings:
>    2.   FFI:        no (user requested: default)

ISTR that you also expressed interest in libffcall - you might want to
start with building and installing it.

>    3.   readline:   no (user requested: default)

what is your platform that it lacks readline?

>    4. libsigsegv: yes
>    5. ./makemake  --with-threads=POSIX_THREADS  > Makefile
>    6. make: `config.lisp` is up to date.
>    7.
>    8. To continue building CLISP, the following commands are recommended
>    9.   (cf. unix/INSTALL step 4 ff):
>    10.     cd src
>    11.     vi config.lisp
>    12.     make
>    13.     make check

you could also wrap the whole thing in one command, by passing "--cbc"
(config/build/check) to configure.

> However, I can't possibly seem to locate errors while building with
> threads, although I may be wrong in execution or looking at the wrong

"make check" either prints "tests passed" or instructions on where to
find the failures (see tests/*.erg)

> place.  Can you guide me as to how I shall proceed in this
> regard. Also, how and where the CLISP hash table implementation is
> used, which in turn should be replaced by a lock-free implementation.

See clisp/src/hashtbl.d for the hash table implementation.

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1265
http://www.childpsy.net/ http://pmw.org.il http://openvotingconsortium.org
http://jihadwatch.org http://islamexposedonline.com
Feynman: 'Philosophy of science is as useful to scientists as ornithology is to birds'

help on building clisp

[shashank <sha...@gm...>]

Hello,

I am Shashank (a gsoc aspirant) and I have been trying to build clisp
however I can't seem to progress.
I have cloned the mercuial repository from here -
http://sourceforge.net/p/clisp/clisp/ci/default/tree/doc/

In an earlier exchange of email, Sam Steingold asked me to:
> Clone the clisp mercurial repo and build from it with threads.
> Observe the crashes in the tests.
> Investigate how you would replace the CLISP hash table implementation
> with the lock-free one.

However as soon as I do :


   1. $ make -f Makefile.devel CFLAGS=MULTITHREAD


I get this error :     (The complete stacktrace is
here<http://pastebin.com/PpHsT1vU>
)


   1. find: `@srcdir@\\..\\modules\\': No such file or directory


So I tried build using configure

   1. $ ./configure --with-threads=POSIX_THREADS

the command runs successfully and in the end, I get the following


   1. Configure findings:
   2.   FFI:        no (user requested: default)
   3.   readline:   no (user requested: default)
   4. libsigsegv: yes
   5. ./makemake  --with-threads=POSIX_THREADS  > Makefile
   6. make: `config.lisp` is up to date.
   7.
   8. To continue building CLISP, the following commands are recommended
   9.   (cf. unix/INSTALL step 4 ff):
   10.     cd src
   11.     vi config.lisp
   12.     make
   13.     make check



Later, the execution of `make` and `make check` commands also occurs
successfully (with huge amount of execution steps being flushed out on the
terminal).

However, I can't possibly seem to locate errors while building with
threads, although I may be wrong in execution or looking at the wrong place.
Can you guide me as to how I shall proceed in this regard. Also, how and
where the CLISP hash table implementation is used, which in turn should be
replaced by a lock-free implementation.

Thanks in advance.

Shashank

Re: ANSI CL support

[Pascal J. B. <pj...@in...>]

Raymond Toy <toy...@gm...> writes:

>>>>>> "Pascal" == Pascal J Bourguignon <pj...@in...> writes:
>
>     Pascal> Raymond Toy <toy...@gm...> writes:
>     >> A friend pointed this out to me:
>     >> 
>     >> (apropos "-ANSI") ->
>     >> *COERCE-FIXNUM-CHAR-ANSI*                  variable
>     >> *FLOATING-POINT-CONTAGION-ANSI*            variable
>     >> *FLOATING-POINT-RATIONAL-CONTAGION-ANSI*    variable
>     >> *LOOP-ANSI*                                variable
>     >> *MERGE-PATHNAMES-ANSI*                     variable
>     >> *PARSE-NAMESTRING-ANSI*                    variable
>     >> *PHASE-ANSI*                               variable
>     >> *PRINT-EMPTY-ARRAYS-ANSI*                  variable
>     >> *PRINT-PATHNAMES-ANSI*                     variable
>     >> *PRINT-SPACE-CHAR-ANSI*                    variable
>     >> *PRINT-UNREADABLE-ANSI*                    variable
>     >> *SEQUENCE-COUNT-ANSI*                      variable
>     >> 
>     >> The ANSI CL spec is now almost 20 years old and hasn't changed since
>     >> then. I didn't check to see what all of variables actually do, but
>     >> isn't it time to make these default to T? Or at least some of them?
>
>     Pascal> Always run clisp with -ansi (for the case you also give -norc),
>     Pascal> and put (setf custom:*ansi* t) in ~/.clisprc.lisp
>
> Yes, my friend mentioned that to me as well. But that doesn't explain
> why this is not the default. Does anyone really want a Common Lisp
> implementation that isn't?

I'd agree, IMO the default should be ANSI, if only for the unsuspecting
newbies and other occasional users.


-- 
__Pascal Bourguignon__
http://www.informatimago.com/

Re: (cos (scale-float 1d0 120)) incorrect

[Sam S. <sd...@gn...>]

Please file a bug report on SF.net.
Thanks.

> * Raymond Toy <gbl...@tz...> [2013-11-19 13:49:56 -0800]:
>
> Clisp 2.49 on a Linux Ubuntu box says:
>
> [1]> (cos (scale-float 1d0 120))
> 1.0d0
>
> The true answer is closer to -0.92.  Cmucl and ccl produce this
> answer.  Maxima says this is the correct answer.
>
> I think the issue is that pi reduction is not done to full precision.
>
> Using long-floats, clisp still produces 1L0, but making
> long-float-digits 128 gives the correct answer.
>
> Note also that (scale-float 1d0 120) can be represented exactly as an
> IEEE754 double precision value, and that IEEE754 doubles are not
> approximations.  They are exact rationals (of a certain form).
>
> Ray
>
>
> ------------------------------------------------------------------------------
> Shape the Mobile Experience: Free Subscription
> Software experts and developers: Be at the forefront of tech innovation.
> Intel(R) Software Adrenaline delivers strategic insight and game-changing 
> conversations that shape the rapidly evolving mobile landscape. Sign up now. 
> http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
> _______________________________________________
> clisp-devel mailing list
> cli...@li...
> https://lists.sourceforge.net/lists/listinfo/clisp-devel
>

-- 
Sam Steingold (http://sds.podval.org/) on darwin Ns 10.3.1265
http://www.childpsy.net/ http://honestreporting.com http://ffii.org
http://www.PetitionOnline.com/tap12009/ http://iris.org.il http://dhimmi.com
nobody's life, liberty or property are safe while the legislature is in session

Re: ANSI CL support

[Raymond T. <toy...@gm...>]

>>>>> "Pascal" == Pascal J Bourguignon <pj...@in...> writes:

    Pascal> Raymond Toy <toy...@gm...> writes:
    >> A friend pointed this out to me:
    >> 
    >> (apropos "-ANSI") ->
    >> *COERCE-FIXNUM-CHAR-ANSI*                  variable
    >> *FLOATING-POINT-CONTAGION-ANSI*            variable
    >> *FLOATING-POINT-RATIONAL-CONTAGION-ANSI*    variable
    >> *LOOP-ANSI*                                variable
    >> *MERGE-PATHNAMES-ANSI*                     variable
    >> *PARSE-NAMESTRING-ANSI*                    variable
    >> *PHASE-ANSI*                               variable
    >> *PRINT-EMPTY-ARRAYS-ANSI*                  variable
    >> *PRINT-PATHNAMES-ANSI*                     variable
    >> *PRINT-SPACE-CHAR-ANSI*                    variable
    >> *PRINT-UNREADABLE-ANSI*                    variable
    >> *SEQUENCE-COUNT-ANSI*                      variable
    >> 
    >> The ANSI CL spec is now almost 20 years old and hasn't changed since
    >> then. I didn't check to see what all of variables actually do, but
    >> isn't it time to make these default to T? Or at least some of them?

    Pascal> Always run clisp with -ansi (for the case you also give -norc),
    Pascal> and put (setf custom:*ansi* t) in ~/.clisprc.lisp

Yes, my friend mentioned that to me as well. But that doesn't explain
why this is not the default. Does anyone really want a Common Lisp
implementation that isn't?

Ray

Re: ANSI CL support

[Pascal J. B. <pj...@in...>]

Raymond Toy <toy...@gm...> writes:

> A friend pointed this out to me:
>
> (apropos "-ANSI") ->
> *COERCE-FIXNUM-CHAR-ANSI*                  variable
> *FLOATING-POINT-CONTAGION-ANSI*            variable
> *FLOATING-POINT-RATIONAL-CONTAGION-ANSI*    variable
> *LOOP-ANSI*                                variable
> *MERGE-PATHNAMES-ANSI*                     variable
> *PARSE-NAMESTRING-ANSI*                    variable
> *PHASE-ANSI*                               variable
> *PRINT-EMPTY-ARRAYS-ANSI*                  variable
> *PRINT-PATHNAMES-ANSI*                     variable
> *PRINT-SPACE-CHAR-ANSI*                    variable
> *PRINT-UNREADABLE-ANSI*                    variable
> *SEQUENCE-COUNT-ANSI*                      variable
>
> The ANSI CL spec is now almost 20 years old and hasn't changed since
> then. I didn't check to see what all of variables actually do, but
> isn't it time to make these default to T? Or at least some of them?

Always run clisp with -ansi (for the case you also give -norc),
and put (setf custom:*ansi* t) in ~/.clisprc.lisp

-- 
__Pascal Bourguignon__
http://www.informatimago.com/

(cos (scale-float 1d0 120)) incorrect

[Raymond T. <toy...@gm...>]

Clisp 2.49 on a Linux Ubuntu box says:

[1]> (cos (scale-float 1d0 120))
1.0d0

The true answer is closer to -0.92.  Cmucl and ccl produce this
answer.  Maxima says this is the correct answer.

I think the issue is that pi reduction is not done to full precision.

Using long-floats, clisp still produces 1L0, but making
long-float-digits 128 gives the correct answer.

Note also that (scale-float 1d0 120) can be represented exactly as an
IEEE754 double precision value, and that IEEE754 doubles are not
approximations.  They are exact rationals (of a certain form).

Ray

ANSI CL support

[Raymond T. <toy...@gm...>]

A friend pointed this out to me:

(apropos "-ANSI") ->
*COERCE-FIXNUM-CHAR-ANSI*                  variable
*FLOATING-POINT-CONTAGION-ANSI*            variable
*FLOATING-POINT-RATIONAL-CONTAGION-ANSI*    variable
*LOOP-ANSI*                                variable
*MERGE-PATHNAMES-ANSI*                     variable
*PARSE-NAMESTRING-ANSI*                    variable
*PHASE-ANSI*                               variable
*PRINT-EMPTY-ARRAYS-ANSI*                  variable
*PRINT-PATHNAMES-ANSI*                     variable
*PRINT-SPACE-CHAR-ANSI*                    variable
*PRINT-UNREADABLE-ANSI*                    variable
*SEQUENCE-COUNT-ANSI*                      variable

The ANSI CL spec is now almost 20 years old and hasn't changed since
then. I didn't check to see what all of variables actually do, but
isn't it time to make these default to T? Or at least some of them?

Ray

[ clisp-Bugs-3610518 ] pari module fails to compile with pari-2.5.x

[SourceForge.net <no...@so...>]

Bugs item #3610518, was opened at 2013-04-10 21:15
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610518&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
>Category: modules
>Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: grozin (grozin)
Assigned to: Nobody/Anonymous (nobody)
Summary: pari module fails to compile with pari-2.5.x

Initial Comment:
The current stable version is pari-2.5.3. Starting from 2.5.0, compilation of pari.c fails:

gcc -I/usr/include/db4.8  -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/gllib -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir -I/usr/include/db4.8 -O2 -march=native -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/linkkit -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/modules/pari  -c pari.c
pari.c: In function ‘get_entry_doc’:
pari.c:7:58: warning: return discards qualifiers from pointer target type
pari.c: In function ‘subres0’:
pari.c:10:1: warning: implicit declaration of function ‘subres’
pari.c:10:30: warning: return makes pointer from integer without a cast
pari.c: In function ‘module__pari__init_function_2’:
pari.c:136:37: error: ‘gpi’ undeclared (first use in this function)
pari.c:136:37: note: each undeclared identifier is reported only once for each function it appears in
pari.c:137:37: error: ‘geuler’ undeclared (first use in this function)
pari.c:142:37: error: ‘gi’ undeclared (first use in this function)
pari.c:146:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:147:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:149:37: error: ‘ordvar’ undeclared (first use in this function)
pari.c:150:37: error: ‘polvar’ undeclared (first use in this function)
pari.c:152:37: error: ‘varentries’ undeclared (first use in this function)
pari.c:160:37: error: ‘allocatemoremem’ undeclared (first use in this function)
pari.c:164:37: error: ‘gscalmat’ undeclared (first use in this function)
pari.c:178:37: error: ‘caradj0’ undeclared (first use in this function)
pari.c:186:37: error: ‘extract’ undeclared (first use in this function)
pari.c:187:37: error: ‘matextract’ undeclared (first use in this function)
pari.c:192:37: error: ‘matrixqz’ undeclared (first use in this function)
pari.c:193:37: error: ‘matrixqz2’ undeclared (first use in this function)
pari.c:194:37: error: ‘matrixqz3’ undeclared (first use in this function)
pari.c:197:37: error: ‘kerint1’ undeclared (first use in this function)
pari.c:204:37: error: ‘racine’ undeclared (first use in this function)
pari.c:218:37: error: ‘phi’ undeclared (first use in this function)
pari.c:219:37: error: ‘smallfact’ undeclared (first use in this function)
pari.c:226:37: error: ‘gener’ undeclared (first use in this function)
pari.c:230:37: error: ‘fundunit’ undeclared (first use in this function)
pari.c:231:37: error: ‘regula’ undeclared (first use in this function)
pari.c:232:37: error: ‘compimag’ undeclared (first use in this function)
pari.c:236:37: error: ‘sqcompreal’ undeclared (first use in this function)
pari.c:237:37: error: ‘sqcompimag’ undeclared (first use in this function)
pari.c:246:37: error: ‘comprealraw’ undeclared (first use in this function)
pari.c:247:37: error: ‘powrealraw’ undeclared (first use in this function)
pari.c:254:37: error: ‘mu’ undeclared (first use in this function)
pari.c:257:37: error: ‘hil’ undeclared (first use in this function)
pari.c:259:37: error: ‘base’ undeclared (first use in this function)
pari.c:260:37: error: ‘smallbase’ undeclared (first use in this function)
pari.c:261:37: error: ‘discf’ undeclared (first use in this function)
pari.c:262:37: error: ‘smalldiscf’ undeclared (first use in this function)
pari.c:267:37: error: ‘factoredbase’ undeclared (first use in this function)
pari.c:268:37: error: ‘factoreddiscf’ undeclared (first use in this function)
pari.c:276:37: error: ‘galoisconj2’ undeclared (first use in this function)
pari.c:277:37: error: ‘galoisconj4’ undeclared (first use in this function)
pari.c:284:37: error: ‘element_mul’ undeclared (first use in this function)
pari.c:285:37: error: ‘element_pow’ undeclared (first use in this function)
pari.c:298:37: error: ‘principalideal’ undeclared (first use in this function)
pari.c:299:37: error: ‘principalidele’ undeclared (first use in this function)
pari.c:308:37: error: ‘nfhermite’ undeclared (first use in this function)
pari.c:309:37: error: ‘nfhermitemod’ undeclared (first use in this function)
pari.c:314:37: error: ‘element_div’ undeclared (first use in this function)
pari.c:316:37: error: ‘element_reduce’ undeclared (first use in this function)
pari.c:319:37: error: ‘element_val’ undeclared (first use in this function)
pari.c:351:37: error: ‘changevar’ undeclared (first use in this function)
pari.c:354:37: error: ‘reorder’ undeclared (first use in this function)
pari.c:387:37: error: ‘buchall’ undeclared (first use in this function)
pari.c:392:37: error: ‘buchfu’ undeclared (first use in this function)
pari.c:415:37: error: ‘torsell’ undeclared (first use in this function)
pari.c:496:37: error: ‘factpol’ undeclared (first use in this function)
pari.c:500:37: error: ‘discsr’ undeclared (first use in this function)
pari.c:552:37: error: ‘polylogd’ undeclared (first use in this function)
pari.c:553:37: error: ‘polylogdold’ undeclared (first use in this function)
pari.c:554:37: error: ‘polylogp’ undeclared (first use in this function)
make[1]: *** [pari.o] Error 1

See https://bugs.gentoo.org/show_bug.cgi?id=376673 for more details. Is there a hope this will be fixed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610518&group_id=1355

[ clisp-Bugs-3610521 ] pari module fails to compile with pari-2.5.x

[SourceForge.net <no...@so...>]

Bugs item #3610521, was opened at 2013-04-10 21:52
Message generated for change (Settings changed) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610521&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Deleted
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: grozin (grozin)
Assigned to: Nobody/Anonymous (nobody)
Summary: pari module fails to compile with pari-2.5.x

Initial Comment:
The current stable version is pari-2.5.3. Starting from 2.5.0, compilation of pari.c fails:

gcc -I/usr/include/db4.8  -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/gllib -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir -I/usr/include/db4.8 -O2 -march=native -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/linkkit -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/modules/pari  -c pari.c
pari.c: In function ‘get_entry_doc’:
pari.c:7:58: warning: return discards qualifiers from pointer target type
pari.c: In function ‘subres0’:
pari.c:10:1: warning: implicit declaration of function ‘subres’
pari.c:10:30: warning: return makes pointer from integer without a cast
pari.c: In function ‘module__pari__init_function_2’:
pari.c:136:37: error: ‘gpi’ undeclared (first use in this function)
pari.c:136:37: note: each undeclared identifier is reported only once for each function it appears in
pari.c:137:37: error: ‘geuler’ undeclared (first use in this function)
pari.c:142:37: error: ‘gi’ undeclared (first use in this function)
pari.c:146:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:147:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:149:37: error: ‘ordvar’ undeclared (first use in this function)
pari.c:150:37: error: ‘polvar’ undeclared (first use in this function)
pari.c:152:37: error: ‘varentries’ undeclared (first use in this function)
pari.c:160:37: error: ‘allocatemoremem’ undeclared (first use in this function)
pari.c:164:37: error: ‘gscalmat’ undeclared (first use in this function)
pari.c:178:37: error: ‘caradj0’ undeclared (first use in this function)
pari.c:186:37: error: ‘extract’ undeclared (first use in this function)
pari.c:187:37: error: ‘matextract’ undeclared (first use in this function)
pari.c:192:37: error: ‘matrixqz’ undeclared (first use in this function)
pari.c:193:37: error: ‘matrixqz2’ undeclared (first use in this function)
pari.c:194:37: error: ‘matrixqz3’ undeclared (first use in this function)
pari.c:197:37: error: ‘kerint1’ undeclared (first use in this function)
pari.c:204:37: error: ‘racine’ undeclared (first use in this function)
pari.c:218:37: error: ‘phi’ undeclared (first use in this function)
pari.c:219:37: error: ‘smallfact’ undeclared (first use in this function)
pari.c:226:37: error: ‘gener’ undeclared (first use in this function)
pari.c:230:37: error: ‘fundunit’ undeclared (first use in this function)
pari.c:231:37: error: ‘regula’ undeclared (first use in this function)
pari.c:232:37: error: ‘compimag’ undeclared (first use in this function)
pari.c:236:37: error: ‘sqcompreal’ undeclared (first use in this function)
pari.c:237:37: error: ‘sqcompimag’ undeclared (first use in this function)
pari.c:246:37: error: ‘comprealraw’ undeclared (first use in this function)
pari.c:247:37: error: ‘powrealraw’ undeclared (first use in this function)
pari.c:254:37: error: ‘mu’ undeclared (first use in this function)
pari.c:257:37: error: ‘hil’ undeclared (first use in this function)
pari.c:259:37: error: ‘base’ undeclared (first use in this function)
pari.c:260:37: error: ‘smallbase’ undeclared (first use in this function)
pari.c:261:37: error: ‘discf’ undeclared (first use in this function)
pari.c:262:37: error: ‘smalldiscf’ undeclared (first use in this function)
pari.c:267:37: error: ‘factoredbase’ undeclared (first use in this function)
pari.c:268:37: error: ‘factoreddiscf’ undeclared (first use in this function)
pari.c:276:37: error: ‘galoisconj2’ undeclared (first use in this function)
pari.c:277:37: error: ‘galoisconj4’ undeclared (first use in this function)
pari.c:284:37: error: ‘element_mul’ undeclared (first use in this function)
pari.c:285:37: error: ‘element_pow’ undeclared (first use in this function)
pari.c:298:37: error: ‘principalideal’ undeclared (first use in this function)
pari.c:299:37: error: ‘principalidele’ undeclared (first use in this function)
pari.c:308:37: error: ‘nfhermite’ undeclared (first use in this function)
pari.c:309:37: error: ‘nfhermitemod’ undeclared (first use in this function)
pari.c:314:37: error: ‘element_div’ undeclared (first use in this function)
pari.c:316:37: error: ‘element_reduce’ undeclared (first use in this function)
pari.c:319:37: error: ‘element_val’ undeclared (first use in this function)
pari.c:351:37: error: ‘changevar’ undeclared (first use in this function)
pari.c:354:37: error: ‘reorder’ undeclared (first use in this function)
pari.c:387:37: error: ‘buchall’ undeclared (first use in this function)
pari.c:392:37: error: ‘buchfu’ undeclared (first use in this function)
pari.c:415:37: error: ‘torsell’ undeclared (first use in this function)
pari.c:496:37: error: ‘factpol’ undeclared (first use in this function)
pari.c:500:37: error: ‘discsr’ undeclared (first use in this function)
pari.c:552:37: error: ‘polylogd’ undeclared (first use in this function)
pari.c:553:37: error: ‘polylogdold’ undeclared (first use in this function)
pari.c:554:37: error: ‘polylogp’ undeclared (first use in this function)
make[1]: *** [pari.o] Error 1

See https://bugs.gentoo.org/show_bug.cgi?id=376673 for more details. Is there a hope this will be fixed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610521&group_id=1355

[ clisp-Bugs-3610521 ] pari module fails to compile with pari-2.5.x

[SourceForge.net <no...@so...>]

Bugs item #3610521, was opened at 2013-04-10 21:52
Message generated for change (Tracker Item Submitted) made by grozin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610521&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: grozin (grozin)
Assigned to: Nobody/Anonymous (nobody)
Summary: pari module fails to compile with pari-2.5.x

Initial Comment:
The current stable version is pari-2.5.3. Starting from 2.5.0, compilation of pari.c fails:

gcc -I/usr/include/db4.8  -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/gllib -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir -I/usr/include/db4.8 -O2 -march=native -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/linkkit -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/modules/pari  -c pari.c
pari.c: In function ‘get_entry_doc’:
pari.c:7:58: warning: return discards qualifiers from pointer target type
pari.c: In function ‘subres0’:
pari.c:10:1: warning: implicit declaration of function ‘subres’
pari.c:10:30: warning: return makes pointer from integer without a cast
pari.c: In function ‘module__pari__init_function_2’:
pari.c:136:37: error: ‘gpi’ undeclared (first use in this function)
pari.c:136:37: note: each undeclared identifier is reported only once for each function it appears in
pari.c:137:37: error: ‘geuler’ undeclared (first use in this function)
pari.c:142:37: error: ‘gi’ undeclared (first use in this function)
pari.c:146:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:147:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:149:37: error: ‘ordvar’ undeclared (first use in this function)
pari.c:150:37: error: ‘polvar’ undeclared (first use in this function)
pari.c:152:37: error: ‘varentries’ undeclared (first use in this function)
pari.c:160:37: error: ‘allocatemoremem’ undeclared (first use in this function)
pari.c:164:37: error: ‘gscalmat’ undeclared (first use in this function)
pari.c:178:37: error: ‘caradj0’ undeclared (first use in this function)
pari.c:186:37: error: ‘extract’ undeclared (first use in this function)
pari.c:187:37: error: ‘matextract’ undeclared (first use in this function)
pari.c:192:37: error: ‘matrixqz’ undeclared (first use in this function)
pari.c:193:37: error: ‘matrixqz2’ undeclared (first use in this function)
pari.c:194:37: error: ‘matrixqz3’ undeclared (first use in this function)
pari.c:197:37: error: ‘kerint1’ undeclared (first use in this function)
pari.c:204:37: error: ‘racine’ undeclared (first use in this function)
pari.c:218:37: error: ‘phi’ undeclared (first use in this function)
pari.c:219:37: error: ‘smallfact’ undeclared (first use in this function)
pari.c:226:37: error: ‘gener’ undeclared (first use in this function)
pari.c:230:37: error: ‘fundunit’ undeclared (first use in this function)
pari.c:231:37: error: ‘regula’ undeclared (first use in this function)
pari.c:232:37: error: ‘compimag’ undeclared (first use in this function)
pari.c:236:37: error: ‘sqcompreal’ undeclared (first use in this function)
pari.c:237:37: error: ‘sqcompimag’ undeclared (first use in this function)
pari.c:246:37: error: ‘comprealraw’ undeclared (first use in this function)
pari.c:247:37: error: ‘powrealraw’ undeclared (first use in this function)
pari.c:254:37: error: ‘mu’ undeclared (first use in this function)
pari.c:257:37: error: ‘hil’ undeclared (first use in this function)
pari.c:259:37: error: ‘base’ undeclared (first use in this function)
pari.c:260:37: error: ‘smallbase’ undeclared (first use in this function)
pari.c:261:37: error: ‘discf’ undeclared (first use in this function)
pari.c:262:37: error: ‘smalldiscf’ undeclared (first use in this function)
pari.c:267:37: error: ‘factoredbase’ undeclared (first use in this function)
pari.c:268:37: error: ‘factoreddiscf’ undeclared (first use in this function)
pari.c:276:37: error: ‘galoisconj2’ undeclared (first use in this function)
pari.c:277:37: error: ‘galoisconj4’ undeclared (first use in this function)
pari.c:284:37: error: ‘element_mul’ undeclared (first use in this function)
pari.c:285:37: error: ‘element_pow’ undeclared (first use in this function)
pari.c:298:37: error: ‘principalideal’ undeclared (first use in this function)
pari.c:299:37: error: ‘principalidele’ undeclared (first use in this function)
pari.c:308:37: error: ‘nfhermite’ undeclared (first use in this function)
pari.c:309:37: error: ‘nfhermitemod’ undeclared (first use in this function)
pari.c:314:37: error: ‘element_div’ undeclared (first use in this function)
pari.c:316:37: error: ‘element_reduce’ undeclared (first use in this function)
pari.c:319:37: error: ‘element_val’ undeclared (first use in this function)
pari.c:351:37: error: ‘changevar’ undeclared (first use in this function)
pari.c:354:37: error: ‘reorder’ undeclared (first use in this function)
pari.c:387:37: error: ‘buchall’ undeclared (first use in this function)
pari.c:392:37: error: ‘buchfu’ undeclared (first use in this function)
pari.c:415:37: error: ‘torsell’ undeclared (first use in this function)
pari.c:496:37: error: ‘factpol’ undeclared (first use in this function)
pari.c:500:37: error: ‘discsr’ undeclared (first use in this function)
pari.c:552:37: error: ‘polylogd’ undeclared (first use in this function)
pari.c:553:37: error: ‘polylogdold’ undeclared (first use in this function)
pari.c:554:37: error: ‘polylogp’ undeclared (first use in this function)
make[1]: *** [pari.o] Error 1

See https://bugs.gentoo.org/show_bug.cgi?id=376673 for more details. Is there a hope this will be fixed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610521&group_id=1355

[ clisp-Bugs-3610518 ] pari module fails to compile with pari-2.5.x

[SourceForge.net <no...@so...>]

Bugs item #3610518, was opened at 2013-04-10 21:15
Message generated for change (Tracker Item Submitted) made by grozin
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610518&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: grozin (grozin)
Assigned to: Nobody/Anonymous (nobody)
Summary: pari module fails to compile with pari-2.5.x

Initial Comment:
The current stable version is pari-2.5.3. Starting from 2.5.0, compilation of pari.c fails:

gcc -I/usr/include/db4.8  -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/gllib -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir -I/usr/include/db4.8 -O2 -march=native -pipe -Wa,--noexecstack -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DENABLE_UNICODE -DDYNAMIC_FFI -I. -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/builddir/linkkit -I/var/tmp/portage/dev-lisp/clisp-2.49-r3/work/clisp-2.49/modules/pari  -c pari.c
pari.c: In function ‘get_entry_doc’:
pari.c:7:58: warning: return discards qualifiers from pointer target type
pari.c: In function ‘subres0’:
pari.c:10:1: warning: implicit declaration of function ‘subres’
pari.c:10:30: warning: return makes pointer from integer without a cast
pari.c: In function ‘module__pari__init_function_2’:
pari.c:136:37: error: ‘gpi’ undeclared (first use in this function)
pari.c:136:37: note: each undeclared identifier is reported only once for each function it appears in
pari.c:137:37: error: ‘geuler’ undeclared (first use in this function)
pari.c:142:37: error: ‘gi’ undeclared (first use in this function)
pari.c:146:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:147:59: warning: invalid application of ‘sizeof’ to a function type
pari.c:149:37: error: ‘ordvar’ undeclared (first use in this function)
pari.c:150:37: error: ‘polvar’ undeclared (first use in this function)
pari.c:152:37: error: ‘varentries’ undeclared (first use in this function)
pari.c:160:37: error: ‘allocatemoremem’ undeclared (first use in this function)
pari.c:164:37: error: ‘gscalmat’ undeclared (first use in this function)
pari.c:178:37: error: ‘caradj0’ undeclared (first use in this function)
pari.c:186:37: error: ‘extract’ undeclared (first use in this function)
pari.c:187:37: error: ‘matextract’ undeclared (first use in this function)
pari.c:192:37: error: ‘matrixqz’ undeclared (first use in this function)
pari.c:193:37: error: ‘matrixqz2’ undeclared (first use in this function)
pari.c:194:37: error: ‘matrixqz3’ undeclared (first use in this function)
pari.c:197:37: error: ‘kerint1’ undeclared (first use in this function)
pari.c:204:37: error: ‘racine’ undeclared (first use in this function)
pari.c:218:37: error: ‘phi’ undeclared (first use in this function)
pari.c:219:37: error: ‘smallfact’ undeclared (first use in this function)
pari.c:226:37: error: ‘gener’ undeclared (first use in this function)
pari.c:230:37: error: ‘fundunit’ undeclared (first use in this function)
pari.c:231:37: error: ‘regula’ undeclared (first use in this function)
pari.c:232:37: error: ‘compimag’ undeclared (first use in this function)
pari.c:236:37: error: ‘sqcompreal’ undeclared (first use in this function)
pari.c:237:37: error: ‘sqcompimag’ undeclared (first use in this function)
pari.c:246:37: error: ‘comprealraw’ undeclared (first use in this function)
pari.c:247:37: error: ‘powrealraw’ undeclared (first use in this function)
pari.c:254:37: error: ‘mu’ undeclared (first use in this function)
pari.c:257:37: error: ‘hil’ undeclared (first use in this function)
pari.c:259:37: error: ‘base’ undeclared (first use in this function)
pari.c:260:37: error: ‘smallbase’ undeclared (first use in this function)
pari.c:261:37: error: ‘discf’ undeclared (first use in this function)
pari.c:262:37: error: ‘smalldiscf’ undeclared (first use in this function)
pari.c:267:37: error: ‘factoredbase’ undeclared (first use in this function)
pari.c:268:37: error: ‘factoreddiscf’ undeclared (first use in this function)
pari.c:276:37: error: ‘galoisconj2’ undeclared (first use in this function)
pari.c:277:37: error: ‘galoisconj4’ undeclared (first use in this function)
pari.c:284:37: error: ‘element_mul’ undeclared (first use in this function)
pari.c:285:37: error: ‘element_pow’ undeclared (first use in this function)
pari.c:298:37: error: ‘principalideal’ undeclared (first use in this function)
pari.c:299:37: error: ‘principalidele’ undeclared (first use in this function)
pari.c:308:37: error: ‘nfhermite’ undeclared (first use in this function)
pari.c:309:37: error: ‘nfhermitemod’ undeclared (first use in this function)
pari.c:314:37: error: ‘element_div’ undeclared (first use in this function)
pari.c:316:37: error: ‘element_reduce’ undeclared (first use in this function)
pari.c:319:37: error: ‘element_val’ undeclared (first use in this function)
pari.c:351:37: error: ‘changevar’ undeclared (first use in this function)
pari.c:354:37: error: ‘reorder’ undeclared (first use in this function)
pari.c:387:37: error: ‘buchall’ undeclared (first use in this function)
pari.c:392:37: error: ‘buchfu’ undeclared (first use in this function)
pari.c:415:37: error: ‘torsell’ undeclared (first use in this function)
pari.c:496:37: error: ‘factpol’ undeclared (first use in this function)
pari.c:500:37: error: ‘discsr’ undeclared (first use in this function)
pari.c:552:37: error: ‘polylogd’ undeclared (first use in this function)
pari.c:553:37: error: ‘polylogdold’ undeclared (first use in this function)
pari.c:554:37: error: ‘polylogp’ undeclared (first use in this function)
make[1]: *** [pari.o] Error 1

See https://bugs.gentoo.org/show_bug.cgi?id=376673 for more details. Is there a hope this will be fixed?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3610518&group_id=1355

[ clisp-Bugs-3485514 ] Cygwin & Pipes

[SourceForge.net <no...@so...>]

Bugs item #3485514, was opened at 2012-02-07 14:46
Message generated for change (Comment added) made by toddcpierce
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Todd Pierce (toddcpierce)
Assigned to: Bruno Haible (haible)
Summary: Cygwin & Pipes

Initial Comment:
Hello CLISP crew!

This is not really a bug.  After all, Cygwin just started supporting named pipes.  It appears, though, that the build of CLISP being distributed along with Cygwin doesn't recognize them.  The version of CLISP is this:

Welcome to GNU CLISP 2.48 (2009-07-28) 

Since CLISP is turrning out to be the most comfy place for my artificial intelligence to, well... think.

The behavior I noticed is that CLISP would just lock when trying to write to a pipe.  Writing to files works fine.  Reading from the pipe in another terminal window invoked an error in the CLISP session.

I'll mention this to the Cygwin guys too.  I just want you to be on the same page.

Thanks for all the help.

Sincerely, 

-Todd



----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2013-04-09 11:34

Message:
Hi All, 

I managed to install CLISP for Cygwin manually (it doesn't seem to install
with the new Cygwin installer).  Pipes are working great for all of the
Cygwin utilities now, but still not for CLISP.  Just thought I'd mention
that.  I'm considering compiling it myself... still gotta figure out how to
do that.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2013-03-30 10:27

Message:
Hi all, 

So, it looks like the Cygwin people fixed the pipes but then forgot to
include clisp in their distribution.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-03-05 15:45

Message:
Crew:

Opening the file binary or not seems to cause the open file to lock.  Here
(the open hidden in my own function):

[2]> (setf stream (open-sparser "../stanford-parser/fifoin"))

locks the repl.  However, if I try to read from the other end of the pipe,
I do get this error (binary or not):

*** - UNIX error 22 (EINVAL): Invalid argument
The following restarts are available:
ABORT          :R1      Abort main loop

*** - UNIX error 11 (EWOULDBLOCK): Operation would block
The following restarts are available:
ABORT          :R1      Abort main loop

So, I'm not sure what is going on there.  I'm hoping I can just port my
whole project to a real unix system soon.  Whatever happens, I'll mention
this stuff to the cygwin guys.

Thanks for keeping an eye out for me.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be permanently
closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
Someone mentioned that this could be a CRLF issue in the mailing list. 

This is not an issue that occurs when reading or writing to the pipe, this
is something that happens when opening it..  If you can even call Cygwin
having pipes yet.  

As I mentioned before, all the file open/close read/write happens fine. 
It's just when dealing with these new Cygwin pipes that things get
strange.

And no, I still haven't posted this matter with the Cygwin guys...  hell...
I'm homeless.

-Todd cambio y fuera

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2012-02-08 07:07

Message:
Todd: maybe you could try binary i/o with pipes? 

Reini: clisp accepts all 3 line terminators (cr, lf, crlf) on input, 
please see http://clisp.org/impnotes/clhs-newline.html

----------------------------------------------------------------------

Comment By: Reini Urban (rurban)
Date: 2012-02-07 17:34

Message:
Maybe because clisp upstream decided to read from pipes with crlf
line-endings, so \n will not end a line. Only the cygwin release reads from
pipes binary. Which makes more sense to cygwin, since we (cygwin) cannot
deal with crlf and we want to pipe streams with line endings to clisp.

Otherwise I see no difference but i haven't tested the new named pipes yet.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

[ clisp-Bugs-3485514 ] Cygwin & Pipes

[SourceForge.net <no...@so...>]

Bugs item #3485514, was opened at 2012-02-07 14:46
Message generated for change (Comment added) made by toddcpierce
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: build problems
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Todd Pierce (toddcpierce)
Assigned to: Bruno Haible (haible)
Summary: Cygwin & Pipes

Initial Comment:
Hello CLISP crew!

This is not really a bug.  After all, Cygwin just started supporting named pipes.  It appears, though, that the build of CLISP being distributed along with Cygwin doesn't recognize them.  The version of CLISP is this:

Welcome to GNU CLISP 2.48 (2009-07-28) 

Since CLISP is turrning out to be the most comfy place for my artificial intelligence to, well... think.

The behavior I noticed is that CLISP would just lock when trying to write to a pipe.  Writing to files works fine.  Reading from the pipe in another terminal window invoked an error in the CLISP session.

I'll mention this to the Cygwin guys too.  I just want you to be on the same page.

Thanks for all the help.

Sincerely, 

-Todd



----------------------------------------------------------------------

>Comment By: Todd Pierce (toddcpierce)
Date: 2013-03-30 10:27

Message:
Hi all, 

So, it looks like the Cygwin people fixed the pipes but then forgot to
include clisp in their distribution.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-03-05 15:45

Message:
Crew:

Opening the file binary or not seems to cause the open file to lock.  Here
(the open hidden in my own function):

[2]> (setf stream (open-sparser "../stanford-parser/fifoin"))

locks the repl.  However, if I try to read from the other end of the pipe,
I do get this error (binary or not):

*** - UNIX error 22 (EINVAL): Invalid argument
The following restarts are available:
ABORT          :R1      Abort main loop

*** - UNIX error 11 (EWOULDBLOCK): Operation would block
The following restarts are available:
ABORT          :R1      Abort main loop

So, I'm not sure what is going on there.  I'm hoping I can just port my
whole project to a real unix system soon.  Whatever happens, I'll mention
this stuff to the cygwin guys.

Thanks for keeping an eye out for me.

-Todd

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
This bug report is now marked as "pending"/"invalid".
This means that we think that the problem you report is not a problem with
CLISP.
Unless you - the reporter - act within 2 weeks, the bug will be permanently
closed.
Sorry about the inconvenience - we hope your silence means that you agree
that this is not a bug in CLISP.

----------------------------------------------------------------------

Comment By: Todd Pierce (toddcpierce)
Date: 2012-02-08 15:49

Message:
Someone mentioned that this could be a CRLF issue in the mailing list. 

This is not an issue that occurs when reading or writing to the pipe, this
is something that happens when opening it..  If you can even call Cygwin
having pipes yet.  

As I mentioned before, all the file open/close read/write happens fine. 
It's just when dealing with these new Cygwin pipes that things get
strange.

And no, I still haven't posted this matter with the Cygwin guys...  hell...
I'm homeless.

-Todd cambio y fuera

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2012-02-08 07:07

Message:
Todd: maybe you could try binary i/o with pipes? 

Reini: clisp accepts all 3 line terminators (cr, lf, crlf) on input, 
please see http://clisp.org/impnotes/clhs-newline.html

----------------------------------------------------------------------

Comment By: Reini Urban (rurban)
Date: 2012-02-07 17:34

Message:
Maybe because clisp upstream decided to read from pipes with crlf
line-endings, so \n will not end a line. Only the cygwin release reads from
pipes binary. Which makes more sense to cygwin, since we (cygwin) cannot
deal with crlf and we want to pipe streams with line endings to clisp.

Otherwise I see no difference but i haven't tested the new named pipes yet.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3485514&group_id=1355

[ clisp-Bugs-3608300 ] Link change

[SourceForge.net <no...@so...>]

Bugs item #3608300, was opened at 2013-03-17 05:30
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3608300&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: doc
Group: web pages
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Mark Carter (comcol)
>Assigned to: Sam Steingold (sds)
Summary: Link change

Initial Comment:
On page http://www.clisp.org/resources.html the reference to 
http://www.markcarter.me.uk/computing/lisp/lisp.htm
is broken, and should now read
http://www.markcarter.me.uk/programming/lisp/lisp.htm

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2013-03-17 07:30

Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3608300&group_id=1355

[ clisp-Bugs-3608300 ] Link change

[SourceForge.net <no...@so...>]

Bugs item #3608300, was opened at 2013-03-17 05:30
Message generated for change (Tracker Item Submitted) made by comcol
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3608300&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: doc
Group: web pages
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mark Carter (comcol)
Assigned to: Bruno Haible (haible)
Summary: Link change

Initial Comment:
On page http://www.clisp.org/resources.html the reference to 
http://www.markcarter.me.uk/computing/lisp/lisp.htm
is broken, and should now read
http://www.markcarter.me.uk/programming/lisp/lisp.htm

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3608300&group_id=1355

[ clisp-Bugs-3603480 ] unless test ignored when compiling

[SourceForge.net <no...@so...>]

Bugs item #3603480, was opened at 2013-02-05 17:49
Message generated for change (Tracker Item Submitted) made by ksvanhorn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3603480&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: clisp
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Kevin S. Van Horn (ksvanhorn)
Assigned to: Bruno Haible (haible)
Summary: unless test ignored when compiling

Initial Comment:
The following file gives an error (can't redefine setq) when compiled, but not when loaded:

--- foo.lisp --
(unless t
  (defmacro setq (a b) nil))

(setq var 'value)
--- end ---

This is a simplified version of code that occurs in the paiprolog system, and this problem causes  (ql:quickload "paiprolog") to fail.

I encountered this problem with CLISP 2.49 running on Windows. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3603480&group_id=1355

[ clisp-Bugs-3603421 ] glibc update

[SourceForge.net <no...@so...>]

Bugs item #3603421, was opened at 2013-02-05 06:36
Message generated for change (Comment added) made by sds
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3603421&group_id=1355

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: build problems
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Vladimír Čunát (vcunat)
>Assigned to: Sam Steingold (sds)
Summary: glibc update

Initial Comment:
At nixos.org we're stabilizing a branch containing glibc-2.17. The problem is that the C type __swblk_t has been removed.

I made a quick fix by removing the (def-c-type __swblk_t) line from modules/bindings/glibc/linux.lisp, which made it build (clisp-2.49 with patched <bits/ipctypes.h> usage).

Is this a correct way? Are you going solve this problem as well?

----------------------------------------------------------------------

>Comment By: Sam Steingold (sds)
Date: 2013-02-05 07:02

Message:
looks like removing it is the only sensible approach.
http://article.gmane.org/gmane.comp.lib.glibc.alpha/25618

----------------------------------------------------------------------

Comment By: Sam Steingold (sds)
Date: 2013-02-05 07:02

Message:
thank you for your bug report.
the bug has been fixed in the source tree (mercurial/hg).
you can either wait for the next release (recommended)
or check out the current mercurial tree (see http://clisp.org)
and build CLISP from the sources (be advised that between
releases the source tree is very unstable and may not even build
on your platform).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=101355&aid=3603421&group_id=1355

clisp-cvs Digest, Vol 71, Issue 1

[<cli...@li...>]

Send clisp-cvs mailing list submissions to
	cli...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/clisp-cvs
or, via email, send a message with subject or body 'help' to
	cli...@li...

You can reach the person managing the list at
	cli...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of clisp-cvs digest..."


CLISP CVS commits for today

Today's Topics:

   1. clisp: handle <ulink url="usenet"> in XSL
      (cli...@li...)
   2. clisp: set compile-command in d-mode
      (cli...@li...)
   3. clisp: (wr_by_array_iau8_buffered): pin the source buffer
      before... (cli...@li...)
   4. clisp: wr_by_array_iau8_buffered: pin_unprotect_varobject
      with j... (cli...@li...)
   5. clisp: (per_thread): TLS (i.e. __thread qualifier) is
      supported ... (cli...@li...)
   6. clisp: comment (cli...@li...)
   7. clisp: implement feature request #3545986
      (cli...@li...)
   8. clisp: faq-debugger==>repl
      (cli...@li...)
   9. clisp: (clisp-repo-p): check for vc-hg-program
      (cli...@li...)
  10. clisp: remove $Id$ (cli...@li...)
  11. clisp: code clean-up for better performance and error
      reporting (cli...@li...)
  12. clisp: when/not->unless (cli...@li...)
  13. clisp: indentation (cli...@li...)
  14. clisp: PCRE-EXEC returns character positions instead of byte
      pos... (cli...@li...)
  15. clisp: (ALL_CFLAGS): new variable, accumulate all C flags
      here, ... (cli...@li...)
  16. clisp: * pathname.d (unix_user_pwd): Don't use getlogin().
      (cli...@li...)
  17. clisp: * modules/bindings/glibc/linux.lisp (__swblk_t):
      remove t... (cli...@li...)


----------------------------------------------------------------------

Message: 1
Date: Mon, 18 Jun 2012 15:53:39 +0000
From: cli...@li...
Subject: clisp: handle <ulink url="usenet"> in XSL
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b0a37787cb93
changeset: 15588:b0a37787cb93ff581a32ae97b53077b02b865dad
user:      Sam Steingold <sd...@po...>
date:      2012-06-18 11:53:02 -0400
description:
handle <ulink url="usenet"> in XSL

diffstat:

 doc/common.xsl  |  5 +++++
 doc/faq.xml     |  6 ++----
 doc/history.xml |  4 ++--
 3 files changed, 9 insertions(+), 6 deletions(-)



------------------------------

Message: 2
Date: Wed, 27 Jun 2012 15:15:01 +0000
From: cli...@li...
Subject: clisp: set compile-command in d-mode
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b689a1c1565e
changeset: 15589:b689a1c1565e656d8ef3f792a3b92f00b9f66114
user:      Sam Steingold <sd...@po...>
date:      2012-06-27 11:08:08 -0400
description:
set compile-command in d-mode

diffstat:

 emacs/d-mode.el |  6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)



------------------------------

Message: 3
Date: Fri, 03 Aug 2012 11:38:09 +0000
From: cli...@li...
Subject: clisp: (wr_by_array_iau8_buffered): pin the source buffer
	before...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9979167880f2
changeset: 15590:9979167880f2d4a06a506737eb53fa5ed22c3588
user:      Vladimir Tzankov <vtz...@gm...>
date:      2012-08-03 14:37:43 +0300
description:
(wr_by_array_iau8_buffered): pin the source buffer before performing actual write

diffstat:

 src/ChangeLog |  5 +++++
 src/stream.d  |  2 ++
 2 files changed, 7 insertions(+), 0 deletions(-)



------------------------------

Message: 4
Date: Sun, 05 Aug 2012 21:25:10 +0000
From: cli...@li...
Subject: clisp: wr_by_array_iau8_buffered: pin_unprotect_varobject
	with j...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/a54e2c41e396
changeset: 15591:a54e2c41e396c3b46d3cc3c3779780973cd388ca
user:      Vladimir Tzankov <vtz...@gm...>
date:      2012-08-06 00:24:47 +0300
description:
wr_by_array_iau8_buffered: pin_unprotect_varobject with just PROT_READ permission

diffstat:

 src/stream.d |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

Message: 5
Date: Mon, 20 Aug 2012 20:27:17 +0000
From: cli...@li...
Subject: clisp: (per_thread): TLS (i.e. __thread qualifier) is
	supported ...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/841294878182
changeset: 15592:84129487818247b2e1857f260b653dfe53cd9175
user:      Vladimir Tzankov <vtz...@gm...>
date:      2012-08-20 23:26:51 +0300
description:
(per_thread): TLS (i.e. __thread qualifier) is supported by gcc 4.5+ on MacOSX and results in significant performance gain

diffstat:

 src/ChangeLog  |  5 +++++
 src/lispbibl.d |  2 +-
 2 files changed, 6 insertions(+), 1 deletions(-)



------------------------------

Message: 6
Date: Fri, 14 Sep 2012 20:20:00 +0000
From: cli...@li...
Subject: clisp: comment
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b07971b03354
changeset: 15593:b07971b033545bf696dc9fdb292d721e467aae55
user:      Vladimir Tzankov <vtz...@gm...>
date:      2012-09-14 23:16:01 +0300
description:
comment

diffstat:

 src/zthread.d |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

Message: 7
Date: Fri, 14 Sep 2012 20:20:02 +0000
From: cli...@li...
Subject: clisp: implement feature request #3545986
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/54e37a538c6c
changeset: 15594:54e37a538c6c20c137fdb22c2db43143f9782043
user:      Vladimir Tzankov <vtz...@gm...>
date:      2012-09-14 23:19:39 +0300
description:
implement feature request #3545986

diffstat:

 src/ChangeLog    |   7 +++++++
 src/threads.lisp |  14 ++++++++++++--
 2 files changed, 19 insertions(+), 2 deletions(-)



------------------------------

Message: 8
Date: Thu, 08 Nov 2012 17:01:04 +0000
From: cli...@li...
Subject: clisp: faq-debugger==>repl
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/fecf363a6cdb
changeset: 15595:fecf363a6cdba4cb039e9fd8600577dd780f5e61
user:      Sam Steingold <sd...@po...>
date:      2012-11-08 11:59:10 -0500
description:
faq-debugger==>repl

diffstat:

 doc/faq.xml |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)



------------------------------

Message: 9
Date: Thu, 08 Nov 2012 17:01:05 +0000
From: cli...@li...
Subject: clisp: (clisp-repo-p): check for vc-hg-program
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/16265dda2b0f
changeset: 15596:16265dda2b0f21699791c2edbbc43276febeeb84
user:      Sam Steingold <sd...@po...>
date:      2012-11-08 11:59:40 -0500
description:
(clisp-repo-p): check for vc-hg-program

diffstat:

 emacs/misc.el |  3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)



------------------------------

Message: 10
Date: Thu, 29 Nov 2012 17:12:55 +0000
From: cli...@li...
Subject: clisp: remove $Id$
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/8e9fab08c09d
changeset: 15597:8e9fab08c09db5bec9e4e2b3f099016b6dc44402
user:      Sam Steingold <sd...@po...>
date:      2012-11-29 10:34:31 -0500
description:
remove $Id$

diffstat:

 modules/oracle/README |  2 --
 1 files changed, 0 insertions(+), 2 deletions(-)



------------------------------

Message: 11
Date: Thu, 29 Nov 2012 17:12:57 +0000
From: cli...@li...
Subject: clisp: code clean-up for better performance and error
	reporting
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/8323b8de7fe4
changeset: 15598:8323b8de7fe40f33f9e36345b44e2485fc74f4e2
user:      Sam Steingold <sd...@po...>
date:      2012-11-29 11:53:23 -0500
description:
code clean-up for better performance and error reporting

diffstat:

 modules/oracle/oracle.lisp |  339 +++++++++++++++++++++-----------------------
 src/ChangeLog              |   14 +-
 2 files changed, 177 insertions(+), 176 deletions(-)



------------------------------

Message: 12
Date: Thu, 29 Nov 2012 17:12:58 +0000
From: cli...@li...
Subject: clisp: when/not->unless
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/404f29609ed6
changeset: 15599:404f29609ed66b78231291e25a1d2e323b308a28
user:      Sam Steingold <sd...@po...>
date:      2012-11-29 11:56:00 -0500
description:
when/not->unless

diffstat:

 modules/oracle/oracle.lisp |  41 ++++++++++++++++++++---------------------
 1 files changed, 20 insertions(+), 21 deletions(-)



------------------------------

Message: 13
Date: Thu, 29 Nov 2012 17:12:59 +0000
From: cli...@li...
Subject: clisp: indentation
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/eab80ba15b7d
changeset: 15600:eab80ba15b7d2450535f782517ca86521ce11bee
user:      Sam Steingold <sd...@po...>
date:      2012-11-29 12:07:15 -0500
description:
indentation

diffstat:

 modules/oracle/oracle.lisp |  626 ++++++++++++++++++++++----------------------
 1 files changed, 311 insertions(+), 315 deletions(-)



------------------------------

Message: 14
Date: Thu, 29 Nov 2012 18:24:26 +0000
From: cli...@li...
Subject: clisp: PCRE-EXEC returns character positions instead of byte
	pos...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/9f4d28091397
changeset: 15601:9f4d28091397fa00ded04e495d665285630ad88e
user:      Sam Steingold <sd...@po...>
date:      2012-11-29 13:23:58 -0500
description:
PCRE-EXEC returns character positions instead of byte positions

diffstat:

 modules/pcre/cpcre.c  |  48 +++++++++++++++++++++++++-----------------------
 modules/pcre/test.tst |   4 ++++
 src/ChangeLog         |   9 +++++++++
 src/NEWS              |   1 +
 src/lispbibl.d        |   1 +
 5 files changed, 40 insertions(+), 23 deletions(-)



------------------------------

Message: 15
Date: Mon, 03 Dec 2012 16:22:52 +0000
From: cli...@li...
Subject: clisp: (ALL_CFLAGS): new variable, accumulate all C flags
	here, ...
To: cli...@li...
Message-ID:
	<hg....@vz...>
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/696bfff6e3d1
changeset: 15602:696bfff6e3d19c461795efe6ae445a60948f9707
user:      Sam Steingold <sd...@po...>
date:      2012-12-03 11:22:27 -0500
description:
(ALL_CFLAGS): new variable, accumulate all C flags here, move -I$(srcdir)
here from CPPFLAGS which is overridden by clisp-link invocation from Makefile

diffstat:

 modules/oracle/Makefile.in |  12 +++++++-----
 src/ChangeLog              |   6 ++++++
 2 files changed, 13 insertions(+), 5 deletions(-)



------------------------------

Message: 16
Date: Sun, 06 Jan 2013 13:35:52 +0000
From: cli...@li...
Subject: clisp: * pathname.d (unix_user_pwd): Don't use getlogin().
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/b29d57d32e38
changeset: 15603:b29d57d32e38b25ae2ab7bfbca6b187fdcd9ba8a
user:      Bruno Haible <br...@cl...>
date:      2013-01-06 14:35:43 +0100
description:
* pathname.d (unix_user_pwd): Don't use getlogin().
Reported by Alberto Riva <al...@ch...> in
<http://article.gmane.org/gmane.lisp.clisp.general:13995>

diffstat:

 src/ChangeLog  |   6 ++++++
 src/pathname.d |  17 +++++++----------
 2 files changed, 13 insertions(+), 10 deletions(-)



------------------------------

Message: 17
Date: Tue, 05 Feb 2013 15:01:22 +0000
From: cli...@li...
Subject: clisp: * modules/bindings/glibc/linux.lisp (__swblk_t):
	remove t...
To: cli...@li...
Message-ID:
	<hg....@sf...>
	
Content-Type: text/plain; charset="us-ascii"

details:   http://clisp.hg.sourceforge.net/hgweb/clisp/clisp/clisp/rev/4cb7fbcb2523
changeset: 15604:4cb7fbcb252312217b0fce402a9c2d4dacfa5979
user:      Sam Steingold <sd...@po...>
date:      2013-02-05 10:00:46 -0500
description:
* modules/bindings/glibc/linux.lisp (__swblk_t): remove the unused
`def-c-type' (removed from glibc too); fixes bug#3603421;
see also http://article.gmane.org/gmane.comp.lib.glibc.alpha/25618

diffstat:

 modules/bindings/glibc/linux.lisp |  1 -
 src/ChangeLog                     |  6 ++++++
 2 files changed, 6 insertions(+), 1 deletions(-)



------------------------------

------------------------------------------------------------------------------
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013 
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb

------------------------------

_______________________________________________
clisp-cvs mailing list
cli...@li...
https://lists.sourceforge.net/lists/listinfo/clisp-cvs


End of clisp-cvs Digest, Vol 71, Issue 1
****************************************