On 28/12/2009 07:28 PM, Carl (CBM) wrote: > 1) An easy-to-use compilation environment for C and C++. I am not > really able to compile Perl modules on willow, despite spending quite > a while hacking at it.
I know some people had issues with this but I never really saw a proper
description of the problem (it's always worked okay for me)... can you
give an example of a module that you weren't able to compile?
Apart from Perl modules, our standard Solaris build has two C and C++
compilers (GCC and Sun Studio), GNU make (which is invoked as 'make'
with the default $PATH), and most other standard Unix development
programs. Is there something in particular that's missing?
> 2) The version of script(1) that comes with solaris doesn't recognize
> the -f option like GNU one. This I did fix for myself, by downloading
> the source from opensolaris, changing it, and compiling.
We already have a backport of OpenSolaris' /usr/bin/ps to provide
BSD-compatible syntax for Linux users. It shouldn't be a problem to
install or backport additional GNU or Linux utilities.
> In general, people who have only used linux might be more comfortable
> if you put more of the linux command line utilities somewhere
Yes - what I'm trying to find out is which utilities those are ;-)
> 3) On the linux server, /bin/sh is bash. On the solaris servers, it
> isn't.
I wonder how many people this actually affects... even on Linux, many
systems have a /bin/sh which isn't bash, so any pre-made scripts should
work okay. Most simple scripts should also work fine under Solaris
/bin/sh. The most noticable missing feature is $()... this should be
fixed in Solaris 11 (which replaces /bin/sh with ksh), but it's not
exactly clear if/when that will be released.
- river.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Toolserver-l mailing list ([email protected]) https://lists.wikimedia.org/mailman/listinfo/toolserver-l Posting guidelines for this list: https://wiki.toolserver.org/view/Mailing_list_etiquette
