From [EMAIL PROTECTED] Fri Feb 22 11:48:35 2008
Thanks for the responses guys. And yeah, I know what the problem is
and how to get around it.
My point was why go through the effort to include the web stack (AMP)
and not bother to make sure they're compatible with each other?
Because sometimes
From [EMAIL PROTECTED] Thu Jan 17 19:49:25 2008
6633860 svn broken on snv_78, suspect apache change
Fixed in 79.
Do these bug fixes also contribute testsuite updates.
This one did not, no. Assuming you mean to the svn testsuite
(assuming there is one in there, I haven't checked,
Manish Chakravarty wrote:
bash-3.2$ svn co http://svn2.cvsdude.com/kdesolaris /trunk/Build/
svn: Valid UTF-8 data
(hex:)
followed by invalid UTF-8 sequence
(hex: 83 c4 0c 85)
Is the svn command in b78 known to be broken?
yes.
6633860 svn broken on snv_78, suspect apache change
S h i v wrote:
Hi,
The tcl version in in Solaris Express is quite dated (version 8.3)
Also, SX doesn't seem to bundle expect a very useful tcl extension for
automation.
Currently it resides at /usr/sfw/bin/tclsh8.3
Where do I propose a move to tcl8.4.x and also a request to bundle
From [EMAIL PROTECTED] Fri Feb 23 12:43:46 2007
You can't build a sandwich of SFW - spec - SFW - spec without
potentially breaking something. For example samba (in SFW) linked
against gnutls (in JDS) by mistake and when JDS updated gnutls,
it broke samba. If they were built together, this
Ivan Buetler wrote:
I solved the problem by just upgrading to snv_54, where everything
works as expected. I do not know details, why my self-compiled progs
are corrupt with snv_53. I tested different gcc versions, from
sunfreeware and from the CDROM. While the binaries worked, if
compiled on
James C. Cotillier wrote:
README.opensolaris version 1.46 is still clear that Studio 10 is the preferred compiler [presumably, as opposed to gcc].
My Studio 11 build of ON (20060619) running under snv_41 on an Intel P4 is breaking
in a way similar to that of a discuss poster in November '05,
Stephen Harpster wrote:
What you're proposing is the Companion CD. Check out the
a href=http://www.opensolaris.org/os/project/companion/;Companion Project/a.
You can add the stuff you want there where it will automatically show up in
Solaris
Express.
The companion CD isn't part of Solaris
From: Mike Kupfer [EMAIL PROTECTED]
Gavin == Gavin Maltby [EMAIL PROTECTED] writes:
Gavin I'm pretty near certain that dmake also looks at .make.machines.
It looks like you're right. The man page doesn't say anything about it,
but strings(1) does report
%s/.make.machines
And in any
