[ matlisp-Bugs-3604763 ] configure.ac assumes "." is in PATH

Bugs item #3604763, was opened at 2013-02-14 15:03
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3604763&group_id=4511

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: compilation bugs
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: configure.ac assumes "." is in PATH

Initial Comment:
There is a type in configure.ac line 380: "if a.out; then" should be "if ./a.out; then".

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3604763&group_id=4511

------------------------------------------------------------------------------
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.

Re: [Matlisp-commit] [matlisp-git]matlisp branch tensor updated. 2012-02-23-129-g2b87e86

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
Matlisp-devel mailing list
Matlisp-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matlisp-devel

[ matlisp-Bugs-3513323 ] SBCL does not like constant definition of +ffi-types+

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Comment added) made by akssri
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&group_id=4511

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: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in
src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya

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

Comment By: Akshay  Srinivasan (akssri)
Date: 2012-05-29 11:10

Message:
Yes, this happens to me on SBCL. I've been lazy and keep ignoring this. 
Will fix this.

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

Comment By: Ilya Perminov (iperminov1)
Date: 2012-04-23 10:29

Message:
The problem happens when ASDF compiles and then loads the file, because
SBCL evaluates DEFCONSTANTs in both compile time and load time.

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

Comment By: Raymond Toy (rtoy)
Date: 2012-04-22 21:43

Message:
Are you getting this because you are reloading src/ffi-cffi into your lisp?

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&group_id=4511

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ matlisp-Bugs-3527162 ] SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&group_id=4511

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: Tzaddi (tzaddi)
Assigned to: Nobody/Anonymous (nobody)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job
:a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

Comment By: Nobody/Anonymous (nobody)
Date: 2012-05-29 10:59

Message:
You should be doing:
 (copy! s (diag~ s1 0))

I'll add a setf-able method to the branch. 

We decided to use "~" (like the "!")  to refer to functions 
which give out matrix-slices.

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

Comment By: Tzaddi (tzaddi)
Date: 2012-05-15 23:28

Message:
I found the definition in tensor.lisp, but am not sure why it can't be used
in svd.lisp.  So, I substituted the expansion in place in the svd method
definition and now I get a new error when running svd with job :a

Arguments X,Y to COPY! are of different dimensions.

Where I substutite I found the definition in tensor.lisp, but am not sure
why it can't be used in svd.lisp.  So, I substituted the expansion in place
in the svd method definition and now I get a new error when running svd
with job :a

Arguments X,Y to COPY! are of different dimensions.

Where I substutite (copy! s (diag s1 0)) for (setf (diag s1) s).

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&group_id=4511

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ matlisp-Bugs-3527162 ] SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Bugs item #3527162, was opened at 2012-05-15 23:15
Message generated for change (Tracker Item Submitted) made by tzaddi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&group_id=4511

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: Tzaddi (tzaddi)
Assigned to: Nobody/Anonymous (nobody)
Summary: SVD gives an error: The function (COMMON-LISP:SETF MATLISP:D

Initial Comment:
It looks like setf (diag ...) is not defined properly or is not in the correct package.  When I run svd with job
:a I get:

The function (COMMON-LISP:SETF MATLISP:DIAG) is undefined.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3527162&group_id=4511

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Merging matlisp-cffi to master branch?

Are we in a good enough state that we can merge the matlisp-cffi branch
to master?

Ray

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ matlisp-Bugs-3514241 ] config.lisp puts its symbols into CL-USER

Bugs item #3514241, was opened at 2012-04-02 12:39
Message generated for change (Comment added) made by rtoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&group_id=4511

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: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: config.lisp puts its symbols into CL-USER

Initial Comment:
config.lisp puts its functions (MATLISP-VERSION and MATLISP-HERALD) into package CL-USER, but these
functions are expected to be in 
MATLISP.

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

>Comment By: Raymond Toy (rtoy)
Date: 2012-04-24 20:58

Message:
Fixed.

Thanks.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&group_id=4511

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[ matlisp-Bugs-3513318 ] Wrong type declarations in src/quadpack.lisp

Bugs item #3513318, was opened at 2012-03-30 10:42
Message generated for change (Comment added) made by rtoy
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

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: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong type declarations in src/quadpack.lisp

Initial Comment:
Array IWORK is passed to functions that expect an array of F2CL-LIB:INTEGER4, but in initialization its
element type is specified as (SIGNED-BYTE 32), 
In SBCL x64 F2CL-LIB:INTEGER4 and (SIGNED-BYTE 32) are different types.

Ilya

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

>Comment By: Raymond Toy (rtoy)
Date: 2012-04-22 21:42

Message:
Thanks.  That's an oversight in the f2cl macros.l where no one bothered to
put in support for sbcl where integer4 should be (signed-byte 32).

However, with the upcoming ffi support, we can probably simply things and
get rid of the translated quadpack routines.  I'll have to think whether we
want to do that or not.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2

[ matlisp-Bugs-3514241 ] config.lisp puts its symbols into CL-USER

Bugs item #3514241, was opened at 2012-04-02 12:39
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&group_id=4511

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: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: config.lisp puts its symbols into CL-USER

Initial Comment:
config.lisp puts its functions (MATLISP-VERSION and MATLISP-HERALD) into package CL-USER, but these
functions are expected to be in 
MATLISP.

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3514241&group_id=4511

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

[ matlisp-Bugs-3513323 ] SBCL does not like constant definition of +ffi-types+

Bugs item #3513323, was opened at 2012-03-30 10:59
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&group_id=4511

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: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: SBCL does not like constant definition of +ffi-types+

Initial Comment:
SBCL signals "constant is being redefined " errors for +ffi-types+ and +ffi-styles+ in
src/ffi-cffi.lisp, because the values of the constants are lists.
SBCL documentation explains the problem: http://www.sbcl.org/manual/Defining-Constants.html.

Ilya

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513323&group_id=4511

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure

[ matlisp-Bugs-3513318 ] Wrong type declarations in src/quadpack.lisp

Bugs item #3513318, was opened at 2012-03-30 10:42
Message generated for change (Tracker Item Submitted) made by iperminov1
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

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: Ilya Perminov (iperminov1)
Assigned to: Nobody/Anonymous (nobody)
Summary: Wrong type declarations in src/quadpack.lisp

Initial Comment:
Array IWORK is passed to functions that expect an array of F2CL-LIB:INTEGER4, but in initialization its
element type is specified as (SIGNED-BYTE 32), 
In SBCL x64 F2CL-LIB:INTEGER4 and (SIGNED-BYTE 32) are different types.

Ilya

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

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=104511&aid=3513318&group_id=4511

------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure