Hello

Where are the .so files for libm and libdl?

twobitsahead: libm.so is delivered by pkg:/system/library/math and is in /lib/amd64 & /lib, with compat symlinks in /usr/lib/amd64, /usr/lib

Thank you

libdl.so is in pkg:/system/library; like libm, the actual library is in /lib/amd64 and /lib with compat symlinks in /usr/lib

And thank you again

There's one more library that has been causing issue; in which package might librt be?

you can find it with "pkg search librt.so"; I see it in pkg:/system/library, and again, actual library is in /lib/amd64 and /lib with compat links in /usr/lib

Noted. Thanks again :)

twobitsahead: oh sorry.. I thought you meant where the source is for those, not the packages :)

jbk The source was interesting to peak over. I am helping someone find some of these files and their locations and contents have been front and center so far. I appreciate your sending either way :)

I feel a bit silly getting stuck on step #1, please point me in the right direction. Tried following the directions at: illumos.org/docs/developers/build to build Illumos without changing anything, just seeing if I can compile it in the first place. Using OmniOS I was unable to successfully compile on a freshly updated system running under VirtualBox. At first couldn't find python so I did an "sudo ln -s /usr/bin/python /usr/bin/python3.5"

but still see an error in the logs, "mv: cannot access ../__pycache__/CStyle.cpython-39.pyc" followed by "*** Error code 2". Logs were one directory deeper located in "/code/illumos-gate/log/latest/nightly.log" rather than "/code/illumos-gate/log/nightly.log" for whatever that's worth. OpenIndiana successfully compiled and installed but then firefox segfaults and crashes whereas the downloaded and updated distro, firefox works fine.

Could it be because I tried under VBox? I never really got any networking to operate correctly under VBox but had success on the bare metal.

iprog4u: So, you absolutely shouldn't have to do things like create links in /usr/bin

I would go and remove any manual stuff like that to avoid confusion

In the "Configuring the build" section, how did you construct your "illumos.sh"? Did you pick one of the "/opt/onbld/env/omnios-*" files and just use that to start?

Noted and will do. Trying right now to follow OmniOS-specific build instructions at: omnios.org/dev/build_instructions.html and it is going but I am on building (25/247) on a Ryzen 7 so not goin gto be fast.

In the "Configuring the build" section I copied the appropriate sections and pasted them at the end of my illumos.sh for each attempt with OpenIndiana and OmniOS.

Alright. I would be inclined to use the files in /opt/onbld/env/omnios-*

e.g., "/opt/onbld/env/omnios-illumos-gate" for a stock illumos-gate build

As they're basically ready to go, without having to understand too much else

I thought that was what I was doing, using the stock environment template. I will try again from scratch unless there is a smarter way to re-attempt?

The docs do not reference "/opt/onbld/env/omnios-illumos-gate" by the way.

They do, in: illumos.org/docs/developers/build/#omnios_1

But I agree it could be a bit clearer

ugh, perhaps they could be clearer or perhaps I could follow them better. I will re-attempt from a fresh installation.