Well, I've uploaded a binary release for Solaris 11 64-bit (should run on OI too), with a working Gettext module. Both libintl and libiconv seems to be the GNU versions (from OpenCSW).
Oh, and Bill, please change your umask to 002... :-)
Ah, sorry, I haven't made any changes to the environment when I built those... guess I should have a set of drop-in config files for my throw-away vms.
Bill
On Mon, 30 Jul 2012, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Oh, and Bill, please change your umask to 002... :-)
No, I meant on pelix, not on the build machine. pub/pike/beta/7.8.696/ was not group-writable.
Ah, ok. That makes a little more sense, though I wasn't sure if the export build preserved permissions when it tars up the installation.
Bill
On Mon, 30 Jul 2012, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
No, I meant on pelix, not on the build machine. pub/pike/beta/7.8.696/ was not group-writable.
There's a script bin/tarfilter.pike which cleans up the persmissions of the generated tarfiles, so that's taken care of. :-)
Makes sense. I realized that the umask problem on pelix (is it still called pelix?) is because I created the directories and uploaded them using sftp. Getting sftp to honor my umask is probably a losing battle (and I've fixed permissions for other directories created by different folks there, as well). I guess the solution is simply to log in directly and fix them up afterward.
Or perhaps a cron job to keep the ftp site fixed up, in general.
Bill
On Tue, 31 Jul 2012, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
There's a script bin/tarfilter.pike which cleans up the persmissions of the generated tarfiles, so that's taken care of. :-)
Hm, you mean that you used the "mkdir" command in sftp? Weird if that doesn't honour umask... Or maybe it's just that you set the umask in a script that is not run by non-interactive logins?
pike-devel@lists.lysator.liu.se