My personal feeling here is, that this problem is produced by the laziness of the Linux
folks, who did create a "Unix"-like OS, which sadly is a bad mix of BSDishness
and some SYSV-ness. At least in Solaris those have always been clearly separated, whereas
in Linux, they were mixed, without clear hints, what's been used when and why...
But, this is nothing new, nor a fault of OpenSolaris, that started, when most
PD-software was started or continued on Linux, and no longer on Solaris as the
first platform...
Remember AIX days, when read() did return an int? And not a char? Hell in
porting to that platform... Been through those nightmares close to 2 decades
ago...
It's never been easy to write real portable software, is, I guess, what I've
experienced...
Matthias
-----Ursprüngliche Nachricht-----
Von: Marion Hakanson <[email protected]>
An: [email protected], [email protected],
[email protected]
Gesendet: 30.4.'10, 21:10
On Fri, Apr 30, 2010 at 02:16:14PM -0400, Dennis Clarke wrote:
Enough of this .. I think you can see what I was saying.
[email protected] said:
Not .. in the slightest.
What Dennis is saying is that compiling open-source software on Solaris
is hard. Even trivial little programs take both effort and nontrivial
knowledge to get beyond just "./configure" followed by "make". I've been
doing this kind of task since around 1990, and it just keeps getting harder.
The popularity of Linux and gcc seem to have produced a generation of
developers who are unfamiliar with the standards and hardly even consider
the existence of another platform.
My personal opinion is that now that Oracle is making folks pay for
security patches on what used to be free to use for development and
evaluation, they're going to make Solaris into an even more marginalized
platform than before.
Regards,
Marion
_______________________________________________
opensolaris-discuss mailing list
[email protected]
_______________________________________________
opensolaris-discuss mailing list
[email protected]
