Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

HowToBuild doesn't have to mention missing libssl #186

Merged
merged 1 commit into from
Oct 18, 2018
+18 −13
Merged

HowToBuild doesn't have to mention missing libssl #186

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 18 additions & 13 deletions build.macos32x86/HowToBuild
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -172,23 +172,28 @@ enough to build the system. The 32-bit build requires at least the 10.9 SDK.
To obtain SDKs it is best to web search for "obtaining older sdks for Xcode",
and follow the instructions you find.

On Sierra people have reported that the support libraries for the SSLPlugin
(libssl.dylib and libcrypto.dylib) are missing. The symptom is an error
message such as this in the output (and the LOG file produced) of the make:
If some library is missing, as indicated by an error message in the console,
(and the LOG file produced), say for example foobar:

ld: library not found for -lssl
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [build/vm/SqueakSSL.bundle/Contents/MacOS/SqueakSSL] Error 1
ld: library not found for -lfoobar
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[1]: *** [build/vm/SqueakFoobar.bundle/Contents/MacOS/SqueakFoobar] Error 1

These libraries should be in the /usr/lib directory for the SDK being used. Use
Then you might search if some libfoobar.dylib is present in the system
(for example in places like /usr/lib or /usr/local/lib).
If so, copy them or link them to the SDK directory.

make print-sdks
You can locate the SDK that you are using with:

to print the SDK, which might be e.g. /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk.
Libraries would then be found in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib.
If they, or any other Apple support libraries, are missing, locate them (they
may be in /usr/lib) and copy or link them into the SDK /usr/lib and retry the
build.
make print-sdks

If it answers e.g.

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk

then libfoobar.dylib should then be copied/linked in

/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/usr/lib


Signing Problems
Expand Down