JOSE quicklisp ASDF loading error

I'm assuming this system definition works on other Lisps since it is in the quicklisp repository. It fails for me using 7.0.0 Mac 64-bit. Is there an obvious fix I'm overlooking?

(defsystem "jose"
  :class :package-inferred-system
  :version "0.1.0"
  :author "Eitaro Fukamachi"
  :license "BSD 2-Clause"
  :description "JSON Object Signing and Encryption (JOSE) implementation"
  :depends-on ("jose/main")
  :in-order-to ((test-op (test-op "jose/tests"))))


(ql:quickload :jose)

; Loading "jose"

Error: Expected a logical pathname word character at "jose/main" :start 4.
1 (continue) Retry ASDF operation.
2 Retry ASDF operation after resetting the configuration.
3 (abort) Give up on "jose"
4 Return to level 0.
5 Return to top loop level 0.

John DeSoi, Ph.D.


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: JOSE quicklisp ASDF loading error

Where are you getting ASDF from? What is the version? If you are relying on the ASDF version that is packaged with quicklisp, it's ancient and I can't help you.

I also don't know what version of ASDF is included with 7.0.0 Mac.

What does (asdf:asdf-version) return?

On 31 Jan 2019, at 14:16, John DeSoi wrote:

I'm assuming this system definition works on other Lisps since it is in the quicklisp repository. It fails for me using 7.0.0 Mac 64-bit. Is there an obvious fix I'm overlooking?

(defsystem "jose"
:class :package-inferred-system
:version "0.1.0"
:author "Eitaro Fukamachi"
:license "BSD 2-Clause"
:description "JSON Object Signing and Encryption (JOSE) implementation"
:depends-on ("jose/main")
:in-order-to ((test-op (test-op "jose/tests"))))

(ql:quickload :jose)

; Loading "jose"

Error: Expected a logical pathname word character at "jose/main" :start 4.
1 (continue) Retry ASDF operation.
2 Retry ASDF operation after resetting the configuration.
3 (abort) Give up on "jose"
4 Return to level 0.
5 Return to top loop level 0.

John DeSoi, Ph.D.

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

Re: JOSE quicklisp ASDF loading error

I have my students follow these steps to upgrade ASDF in Lispworks and make sure Quicklisp uses it. Ignore the other set up parts.

http://www.cs.northwestern.edu/academics/courses/325/admin/lisp-setup.php#upgrade-asdf

On 1/31/2019 2:20 PM, Robert Goldman wrote:

Where are you getting ASDF from? What is the version? If you are relying on the ASDF version that is packaged with quicklisp, it's ancient and I can't help you.

I also don't know what version of ASDF is included with 7.0.0 Mac.

What does (asdf:asdf-version) return?

On 31 Jan 2019, at 14:16, John DeSoi wrote:

I'm assuming this system definition works on other Lisps since it is in the quicklisp repository. It fails for me using 7.0.0 Mac 64-bit. Is there an obvious fix I'm overlooking?

(defsystem "jose"
:class :package-inferred-system
:version "0.1.0"
:author "Eitaro Fukamachi"
:license "BSD 2-Clause"
:description "JSON Object Signing and Encryption (JOSE) implementation"
:depends-on ("jose/main")
:in-order-to ((test-op (test-op "jose/tests"))))

(ql:quickload :jose)

; Loading "jose"

Error: Expected a logical pathname word character at "jose/main" :start 4.
1 (continue) Retry ASDF operation.
2 Retry ASDF operation after resetting the configuration.
3 (abort) Give up on "jose"
4 Return to level 0.
5 Return to top loop level 0.

John DeSoi, Ph.D.

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

-- 
.................................................
Christopher Riesbeck (he/him/his)
Associate Professor, Computer Science & Engineering
McCormick School of Engineering
Northwestern University

2233 Tech Drive
Seeley Mudd, Rm 3117
Evanston, IL 60208

Home page: http://www.cs.northwestern.edu/~riesbeck/
Calendar: http://www.cs.northwestern.edu/~riesbeck/calendar-weekly.html

Re: JOSE quicklisp ASDF loading error

 > (asdf:asdf-version)
"3.1.4"

This the version included with LispWorks 7.0.

John DeSoi, Ph.D.


> On Jan 31, 2019, at 2:20 PM, Robert Goldman <rpgoldman@sift.net> wrote:
> 
> Where are you getting ASDF from? What is the version? If you are relying on the ASDF version that is packaged with quicklisp, it's ancient and I can't help you.
> 
> I also don't know what version of ASDF is included with 7.0.0 Mac.
> 
> What does (asdf:asdf-version) return?
> 


_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: JOSE quicklisp ASDF loading error

Yes, that one is old enough that it won't do what you want. You need at least a 3.2 version, e. g., Allegro is shipping with 3.2.0, and even that is pretty old.

Best,
R

On 31 Jan 2019, at 15:44, John DeSoi wrote:

(asdf:asdf-version)

"3.1.4"

This the version included with LispWorks 7.0.

John DeSoi, Ph.D.

On Jan 31, 2019, at 2:20 PM, Robert Goldman rpgoldman@sift.net wrote:

Where are you getting ASDF from? What is the version? If you are relying on the ASDF version that is packaged with quicklisp, it's ancient and I can't help you.

I also don't know what version of ASDF is included with 7.0.0 Mac.

What does (asdf:asdf-version) return?

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

Re: JOSE quicklisp ASDF loading error

I upgraded to the latest and still had the error. I looked at the long backtrace (for the third time) and finally noticed that there was a ASDF customization function for locating .asd files that was the cause of the error because of the "/" in the name. After removing that, it loads with quicklisp even using 3.1.4.

Thanks to all for the help and responses.

John DeSoi, Ph.D.

> On Jan 31, 2019, at 4:09 PM, Robert Goldman <rpgoldman@sift.net> wrote:
> 
> Yes, that one is old enough that it won't do what you want. You need at least a 3.2 version, e. g., Allegro is shipping with 3.2.0, and even that is pretty old.
> 
> Best,
> R
> 
> On 31 Jan 2019, at 15:44, John DeSoi wrote:
> 
> (asdf:asdf-version)
> 
> "3.1.4"
> 
> This the version included with LispWorks 7.0.
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: JOSE quicklisp ASDF loading error

The slash in the name is supposed to indicate a subsidiary system that 
is defined in the same file as the main system.  So that "foo/test" 
would be a subsidiary system of "foo" and ASDF would know that it should 
look for the definition of "foo/test" in the file "foo.asd".

I'm not sure what customization function that would be; I do know that 
Xach does something to change ASDF's system search behavior for 
Quicklisp. I don't use QL enough myself to know exactly what that is.

On 1 Feb 2019, at 8:22, John DeSoi wrote:

> I upgraded to the latest and still had the error. I looked at the long 
> backtrace (for the third time) and finally noticed that there was a 
> ASDF customization function for locating .asd files that was the cause 
> of the error because of the "/" in the name. After removing that, it 
> loads with quicklisp even using 3.1.4.
>
> Thanks to all for the help and responses.
>
> John DeSoi, Ph.D.
>
>
>> On Jan 31, 2019, at 4:09 PM, Robert Goldman <rpgoldman@sift.net> 
>> wrote:
>>
>> Yes, that one is old enough that it won't do what you want. You need 
>> at least a 3.2 version, e. g., Allegro is shipping with 3.2.0, and 
>> even that is pretty old.
>>
>> Best,
>> R
>>
>> On 31 Jan 2019, at 15:44, John DeSoi wrote:
>>
>> (asdf:asdf-version)
>>
>> "3.1.4"
>>
>> This the version included with LispWorks 7.0.
>>
>
>
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> lisp-hug@lispworks.com
> http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice:	(612) 326-3934
Email:    rpgoldman@SIFT.net

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: JOSE quicklisp ASDF loading error

Quicklisp add functions to asdf:*system-definition-search-functions* to look for Quicklisp-provided systems and local-projects systems.

Zach

On Fri, Feb 1, 2019 at 10:35 AM Robert Goldman <rpgoldman@sift.net> wrote:

The slash in the name is supposed to indicate a subsidiary system that
is defined in the same file as the main system. So that "foo/test"
would be a subsidiary system of "foo" and ASDF would know that it should
look for the definition of "foo/test" in the file "foo.asd".

I'm not sure what customization function that would be; I do know that
Xach does something to change ASDF's system search behavior for
Quicklisp. I don't use QL enough myself to know exactly what that is.

On 1 Feb 2019, at 8:22, John DeSoi wrote:

> I upgraded to the latest and still had the error. I looked at the long
> backtrace (for the third time) and finally noticed that there was a
> ASDF customization function for locating .asd files that was the cause
> of the error because of the "/" in the name. After removing that, it
> loads with quicklisp even using 3.1.4.
>
> Thanks to all for the help and responses.
>
> John DeSoi, Ph.D.
>
>
>> On Jan 31, 2019, at 4:09 PM, Robert Goldman <rpgoldman@sift.net>
>> wrote:
>>
>> Yes, that one is old enough that it won't do what you want. You need
>> at least a 3.2 version, e. g., Allegro is shipping with 3.2.0, and
>> even that is pretty old.
>>
>> Best,
>> R
>>
>> On 31 Jan 2019, at 15:44, John DeSoi wrote:
>>
>> (asdf:asdf-version)
>>
>> "3.1.4"
>>
>> This the version included with LispWorks 7.0.
>>
>
>
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> lisp-hug@lispworks.com
> http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Re: JOSE quicklisp ASDF loading error

There's no reason that this would break finding the "slashy" systems that I described in my email?

I don't really understand that question -- was the "foo/test" system that was broken found in foo.asd or foo/test.asd?

Also, I'm not sure what "broken" means in this context...

On 1 Feb 2019, at 10:03, Zach Beane wrote:

Quicklisp add functions to asdf:*system-definition-search-functions* to look for Quicklisp-provided systems and local-projects systems.

Zach

On Fri, Feb 1, 2019 at 10:35 AM Robert Goldman <rpgoldman@sift.net> wrote:
The slash in the name is supposed to indicate a subsidiary system that
is defined in the same file as the main system. So that "foo/test"
would be a subsidiary system of "foo" and ASDF would know that it should
look for the definition of "foo/test" in the file "foo.asd".

I'm not sure what customization function that would be; I do know that
Xach does something to change ASDF's system search behavior for
Quicklisp. I don't use QL enough myself to know exactly what that is.

On 1 Feb 2019, at 8:22, John DeSoi wrote:

> I upgraded to the latest and still had the error. I looked at the long
> backtrace (for the third time) and finally noticed that there was a
> ASDF customization function for locating .asd files that was the cause
> of the error because of the "/" in the name. After removing that, it
> loads with quicklisp even using 3.1.4.
>
> Thanks to all for the help and responses.
>
> John DeSoi, Ph.D.
>
>
>> On Jan 31, 2019, at 4:09 PM, Robert Goldman <rpgoldman@sift.net>
>> wrote:
>>
>> Yes, that one is old enough that it won't do what you want. You need
>> at least a 3.2 version, e. g., Allegro is shipping with 3.2.0, and
>> even that is pretty old.
>>
>> Best,
>> R
>>
>> On 31 Jan 2019, at 15:44, John DeSoi wrote:
>>
>> (asdf:asdf-version)
>>
>> "3.1.4"
>>
>> This the version included with LispWorks 7.0.
>>
>
>
> _______________________________________________
> Lisp Hug - the mailing list for LispWorks users
> lisp-hug@lispworks.com
> http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html

Robert P. Goldman
Research Fellow
Smart Information Flow Technologies (d/b/a SIFT, LLC)

319 N. First Ave., Suite 400
Minneapolis, MN 55401

Voice: (612) 326-3934
Email: rpgoldman@SIFT.net

Re: JOSE quicklisp ASDF loading error

Let me clarify. This was *my* customization function for asdf:*system-definition-search-functions* which existed long before quicklisp and probably pre-dated ASDF 2.0. It looks for .asd files deeper than the top level directory based on the system name. It would also look for the name with "-test" or "-tests" appended in the same folder because in older ASDF versions there was no provision for having the test system in the same directory (or asd file). My function did not account for a "/" in the name when building a pathname to check for a .asd file causing the error.

John DeSoi, Ph.D.

> On Feb 1, 2019, at 10:11 AM, Robert Goldman <rpgoldman@sift.net> wrote:
> 
> There's no reason that this would break finding the "slashy" systems that I described in my email?
> 
> I don't really understand that question -- was the "foo/test" system that was broken found in foo.asd or  foo/test.asd?
> 
> Also, I'm not sure what "broken" means in this context...
> 

_______________________________________________
Lisp Hug - the mailing list for LispWorks users
lisp-hug@lispworks.com
http://www.lispworks.com/support/lisp-hug.html