Bug 727902 – dev-lisp/sbcl-2.0.5 - Unhandled PACKAGE-DOES-NOT-EXIST in thread #<SB-THREAD:THREAD "main thread" RUNNING {10009C8083}>: The name "SB-BSD-SOCKETS" does not designate any package.

• Status: UNCONFIRMED
• Product: Gentoo Linux

[Description Lee Starnes 2020-06-11 02:21:16 UTC]

Created attachment 644336 [details]
build.log

This error happens while building contrib/sb-bsd-sockets/sockets.lisp:

; compiling file "/var/tmp/portage/dev-lisp/sbcl-2.0.5/work/sbcl-2.0.5/contrib/sb-bsd-sockets/sockets.lisp" (written 31 MAY 2020 08:16:48 AM):
Unhandled PACKAGE-DOES-NOT-EXIST in thread #<SB-THREAD:THREAD "main thread" RUNNING
                                              {10009C8083}>:
  The name "SB-BSD-SOCKETS" does not designate any package.


This is causing the following condition to be false:

'[' -d contrib/sb-bsd-sockets -a -f contrib/sb-bsd-sockets/Makefile -a '!' -f obj/asdf-cache/sb-bsd-sockets/test-passed.test-report ']'


Which is causing make.sh to report:

WARNING! Some of the contrib modules did not build successfully or pass
their self-tests. Failed contribs:"
+ HEADER_HAS_BEEN_PRINTED=true
+ echo '  sb-bsd-sockets'
  sb-bsd-sockets

[Comment 1 Lee Starnes 2020-06-11 02:22:38 UTC]

Created attachment 644338 [details]
emerge --info

[Comment 2 Paul Jewell 2020-06-13 13:03:52 UTC]

I have exactly the same issue here on my desktop PC. This is a new install, and SBCL is being installed for the first time. I have also successfully installed 2.0.5 on my laptop, but in this case, it was an upgrade from earlier versions.

- 2.0.4 compiled OK, but doesn't run - complains it can't find sbcl.core
- the laptop has the latest version of asdf and uiop installed (3.3.2)

Installing the same versions on the desktop PC, and sbcl-2.0.5  builds successfully. 

Therefore the ebuild should have a dependency on:
>=dev-lisp/asdf-3.3.2
>=dev-lisp/uiop-3.3.2

Install these versions now, and then the existing ebuild for sbcl will work.

Now I need to find out why my installation still isn't finding the core file in /usr/lib64/sbcl/ !

[Comment 3 Paul Jewell 2020-06-13 13:13:10 UTC]

For completeness: my problem with finding the core was a simple result of not reloading the current profile. 

Running: # . /etc/profile

resolved my issues.

[Comment 4 Lee Starnes 2020-06-13 22:16:03 UTC]

I had dev-lisp/asdf-3.1.5 and dev-lisp-uiop-3.1.5 installed. Both are keyworded for amd64.

If I upgrade to dev-lisp/asdf-3.3.2-r1 and dev-lisp/uiop-3.3.2 like Paul suggested, then sbcl-2.0.5 compiles successfully and passes all tests. Those two versions are keyworded for ~amd64.

I agree with Paul that >=dev-lisp/sbcl-2.0.5 should probably depend on >=dev-lisp/asdf-3.3.2 and >=dev-lisp/uiop-3.3.2.

[Comment 5 Jeroen Roovers (RETIRED) 2020-06-27 04:41:38 UTC]

*** Bug 729748 has been marked as a duplicate of this bug. ***