00:31:34 Hey people! I'm here again with questions xD 00:31:35 Does the size of `dirent.d_name` dynamic or there is a maximum size like in BSDs and Darwin? 07:13:35 GrayJack it is dynamic, see d_reclen 08:30:43 This weekend I've been having one of my random-ish looks at Valgrind on Illumos 08:30:56 I see that there are quite a lot of signal related errors 08:33:15 among the many others:D 08:33:56 I once looked into it too. 08:34:07 Has anything changed in illumos regarding ucontext or mcontext? 08:34:21 tsoome: it's not as bad as macOS 08:35:01 oooh joy, that hack I reported yesterday as working, with -R/some/path tacked via progname_LDFLAGS - it worked only for gcc (as compiler and by default linker); clang builds still fail to find the libnss3.so and friends :\ 08:35:04 that I do not know:D 08:35:47 I guess mcontext is the same 08:36:34 git blame will help:) 08:37:39 so I guess my question still stands, whether there's a known reliable way of using Mozilla NSS in Solaris-derived OSes (tucked under /usr/lib/mps{,/64} out of sight) with autotools/libtool wrapped projects? 08:38:24 alternately, if the OSes themselves would provide some hacked libtool that does not remove "-R/some/path" from the linker flags it is given on input :) 08:50:05 ucontext has changed but only using 2 of the 5 uc_filler fields 09:05:00 tsoome: and did you find anything related to signals? 09:06:24 it was a while ago, and since I have other stuff in long queues, I left it as is:D 09:08:33 you aren't alone 09:27:49 yea, as we all. 09:51:23 this issue looks fairly old, it's also present on Solaris 11.4 11:19:02 somewhere along the path, if I stick `-Wl,rpath,/usr/lib/mps` instead of (or in addition to) `-R/usr/lib/mps` into LDFLAGS or CFLAGS or wherever, libtools strips that into `-Wl,rpath -Wl,/usr/lib/mps` and then ld (ld: Software Generation Utilities - Solaris Link Editors: 5.11-1.1790 (illumos)) is upset: 11:19:04 ld: fatal: file rpath: open failed: No such file or directory 11:19:06 ld: elf error: file /usr/lib/mps: elf_begin: I/O error: region read: Is a directory 11:21:50 So I guess this is treated as an argument-less rpath and then an attempt to link the directory as one of objects into the binary?.. 11:22:53 hm, other docs spell it as "-rpath" 11:22:54 lost in markup I guess 11:24:22 Something's broken, because those are gcc options and something appears to be invoking the linker directly 11:24:48 I think gcc/clang serve as frontends to a linker 11:25:29 Would not be surprised if to two linkers, gnu ld and system (illumos) ld respectively - based on how they behave differently 11:27:11 so the autotools-processed Makefile calls a libtool script (generated by autoreconf) to link libs and bins, which are treated differently (lose or not the -R/some/path in particular), and the resulting prepared command line is passed to $CC or $LD 11:28:46 "-Wl,-,/some/path" seems much more promising now that I found the "minus" part ;) 11:29:35 So if you use gcc as the linker it'll rewrite that into the correct ld invocation 11:31:23 Well, as far as NUT recipes go, ideally I use "a compiler", "a linker" etc. and libtools or whatever should handle the nuances; but it seems I'm adding more workarounds about its mis-handling of those :\ 11:31:59 But yes, a quick test without the minus is a bit broken, although I'm a little surprised that gcc doesn't complain about the syntax because its has -Xlinker to pass through options gcc doesn't handle itself 11:33:43 Not sure if you were online when I originally posted - the general subject is building and linking an autotools-managed project against Mozilla NSS whose *.so files are in a "hidden" location. Something of the layout that was in Solaris since I was young, so I hoped that in these 20-30 years this is a long-solved non-issue. But here I am today... 11:36:30 they provide a pkgconfig file, so it's likely most auto* will find them that way 11:36:36 Hm, almost everything I build correctly handles nss/nspr, I think it might be just pidgin or one of its plugins that needs extra help 11:37:19 we cheat a little in pkgsrc and inject lib/nss through buildlink for anything that doesn't find them correctly 11:38:09 That's odd now... in NUT, I do take the CFLAGS and LIBS from `pkg-config` (and those include -R/path) but then libtools either removes it or slaps to the end of command-line when linking a program 20:01:36 ptribble: -R and some stuff is special cased to not require -Wl, for tradition reasons