00:34:02 Hello 00:34:16 Where are the .so files for libm and libdl? 01:33:03 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 01:35:02 Thank you 01:35:03 libdl.so is in pkg:/system/library; like libm, the actual library is in /lib/amd64 and /lib with compat symlinks in /usr/lib 01:35:55 And thank you again 01:37:48 There's one more library that has been causing issue; in which package might librt be? 02:05:47 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 02:08:42 Noted. Thanks again :) 02:42:52 twobitsahead: oh sorry.. I thought you meant where the source is for those, not the packages :) 02:48:55 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 :) 20:19:20 I feel a bit silly getting stuck on step #1, please point me in the right direction. Tried following the directions at: https://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" 20:19:20 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. 20:21:07 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. 21:35:34 iprog4u: So, you absolutely shouldn't have to do things like create links in /usr/bin 21:35:46 I would go and remove any manual stuff like that to avoid confusion 21:37:41 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? 21:39:08 Noted and will do. Trying right now to follow OmniOS-specific build instructions at: https://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. 21:40:31 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. 21:41:38 Alright. I would be inclined to use the files in /opt/onbld/env/omnios-* 21:42:06 e.g., "/opt/onbld/env/omnios-illumos-gate" for a stock illumos-gate build 21:42:43 As they're basically ready to go, without having to understand too much else 21:44:48 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? 21:45:31 The docs do not reference "/opt/onbld/env/omnios-illumos-gate" by the way. 21:48:01 They do, in: https://illumos.org/docs/developers/build/#omnios_1 21:48:10 But I agree it could be a bit clearer 21:49:39 ugh, perhaps they could be clearer or perhaps I could follow them better. I will re-attempt from a fresh installation.