Re: mksh on OS X and MacPorts
Ryan Schmidt dixit: which you can get with $CC -v. (Depending on the version of OS X and We have $CC -v in some other place already, but I’ve added all the others for now (in mksh CVS HEAD). Thanks for your contribution, //mirabilos -- „Cool, /usr/share/doc/mksh/examples/uhr.gz ist ja ein Grund, mksh auf jedem System zu installieren.“ -- XTaran auf der OpenRheinRuhr, ganz begeistert (EN: “[…]uhr.gz is a reason to install mksh on every system.”)
Re: mksh on OS X and MacPorts
Ryan Schmidt dixit: Hello, I'm a developer with the MacPorts project. An mksh package was submitted to MacPorts today, and I just committed it. Thank you very much! So if you wanted to list that on your web site, you could do that. OK will do. You currently list Homebrew and Fink packages, and have a note Missing packaging: DarwinPorts/MacPorts (none at all). Note that you should not refer to the name DarwinPorts anymore; we changed our name to MacPorts in 2008. Okay, thanks. I’ll add/change this. I also wanted to report a bug I found. When building, it says: Hi from $MirOS: src/bin/mksh/Build.sh,v 1.655 2014/01/05 21:57:21 tg Exp $ on: $ hwprefs machine_type os_type os_class 2 | ./Build.sh: line 211: hwprefs: command not found It seems you're deliberately targeting Darwin OS (i.e. OS X) and in Actually, I was just trying to shove some information about the environment the shell was built in into the log, in case I get asked questions by packagers. I’ve gathered information from a friend who is a Macintosh user, and from what I could try out when he gave me ssh access to his laptop and his iPhone. that case running the hwprefs command, but no such command exists. If you want to get info about an OS X system, system_profiler, sw_vers or sysctl would be good commands to use. For example: Will add these (I’ll keep hwprefs for people building on older systems though). Thanks a lot. If there's other information you want to gather, let me know what information you want it to print and I'll see what I can do. Basically anything you can imagine either upstream or a porter or packager could want to know about the operating environment when debugging a build “post-mortem”, from the build log. Please Cc me on replies; I'm not subscribed to the list. Sure. http://news.gmane.org/gmane.os.miros.mksh also exists, feel free to use it. (The list is rather new; older mksh- related questions are at gmane.os.miros.general intermixed with generic MirBSD stuff. miros-mksh is forwarded to all miros-discuss subscribers.) bye, //mirabilos -- ah, that reminds me, thanks for the stellar entertainment that you and certain other people provide on the Debian mailing lists │ sole reason I subscribed to them (I'm not using Debian anywhere) is the entertainment factor │ Debian does not strike me as a place for good humour, much less German admin-style humour
Re: mksh on OS X and MacPorts
Ryan Schmidt dixit: Oh, I see now, yes, hwprefs does exist on older Mac OS X systems. But a survey of my systems says it only existed on Intel Macs running Mac OS X 10.4, 10.5, and 10.6 -- not later Intel systems, and not earlier PowerPC systems -- so it's not terribly portable. Right – I used what I got my hands on. version or CPU, so I'd use that instead. I don't know a command to In addition to, not instead. mksh is, by intent, portable to many many old OSes. The OS version is important, as is knowing what compiler was used, which you can get with $CC -v. (Depending on the version of OS X and Right, but that’s a separate part in the code. You might also care to know what version of sh is being used, since your build script depends on it. Yes, but the script does not know with which shell it was invoked. Could even be the previous /sw/bin/mksh from the last time it was built… outputting the shell used in a script and then continuing with it is *hard*. (Most of the shell detection code is invalid syntax in other shells, so my shell detection script uses 'exit' as soon as possible, per shell.) ah, that reminds me, thanks for the stellar entertainment that you and certain […] Must be a different person! I'm not on any Debian lists. No, that’s just one of my eMail signatures – it was behind sigdashes. Sorry if it confused you. bye, //mirabilos -- theftf Ich gebs zu, jupp ist cool -- theftf zu Natureshadow beim Fixen von Debian
