Out of curiousity, why?
We build our current platform (QNX) and apps using gcc4.2. I've got an
outstanding message posted to tool-compilers wondering if anyone has
experience builing ONNV with 4.2. We have done some test builds of ONNV
using gcc (3.4 I think) and it seems to boot x86 anyway.
Hello all, I am trying to get my openoffice code to wkr under opensolaris
without a monitor (a.k.a headless), so far I have tried the following
connection string in my Java code (I am using the Java SDK 3.1 kit):
oooCommand = /opt/openoffice.org3/program/soffice| -nologo -nodefault
-norestore
Supermicro AOC-USASLP-L8i has been confirmed to work flawlessly on OpenSolaris
by several users on these forums already and is AFAIK widely considered the
best controller for building custom Opensolaris ZFS NAS servers
price/performance/compatibility wise in both SOHO NAS and HD HTPC scenarios.
Here's a quick dump on how to get Solaris 10 and OpenSolaris
on the same rpool.
http://blogs.sun.com/mrj/entry/solaris_10_and_opensolaris_on
MRJ
___
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
Here's a quick dump on how to get Solaris 10 and
OpenSolaris
on the same rpool.
ttp://blogs.sun.com/mrj/entry/solaris_10_and_opensolar
is_on
MRJ
Thanks for the plug, will give it a try.
ps. Currently, I have Sol10 installed on the bare metal and OpenSolaris on an
external
On 01/18/10 06:36 AM, solarg wrote:
On 01/15/10 11:51 PM, Norm Jacobs wrote:
On 01/15/10 04:04 PM, Guy Woolley wrote:
Thanks Norm - my build 130 (updated earlier this month from my
original 111) has LP as the default. I see from pkg manager that
CUPS and CUPS-manager are there but not
Hi Mark,
Mark Maule píše v po 18. 01. 2010 v 16:15 -0800:
Out of curiousity, why?
Every compiler has bugs. SUN is doing very large testing of every build
based on binaries produced by Sun Studio. If bug is found, it is fixed.
GCC builds are done (shadow builds) but the results are not tested
Hello,
while developing C++ based applications on OS 2009.06 I'm curious if there is
any reliable tool I may use for checking memory leaks of my C++
libraries/applications. I've tried to use:
1) libumem/mdb -- this does not work, i.e. it reports none C++ memory leak
2) librtc/dbx check -- this
I'm trying to compile a pidgin-sipe plugin for MS Communicator compatibility.
So far it's failing. I'm running snv_130 and have installed
SUNWgcc
SUNW-gnome-common-devel
SUNWgnu-gettext and
SUNWgmake
$pfexec ./configure from the pidgin-sipe directory completes normally then
$pfexec make
On Tue, Jan 19, 2010 at 8:59 PM, Jeff Lawlor jeff.law...@va.gov wrote:
I'm trying to compile a pidgin-sipe plugin for MS Communicator compatibility.
So far it's failing. I'm running snv_130 and have installed
SUNWgcc
SUNW-gnome-common-devel
SUNWgnu-gettext and
SUNWgmake
$pfexec
Here below are the environment properties when I run my enable glassfish script:
g...@opensolaris:/opt/gf21$ pargs -e 20482
20482: /usr/jdk/instances/jdk1.6.0/bin/java
-Dcom.sun.aas.instanceRoot=/opt/gf21/glass
envp[0]: XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt
envp[1]:
And lastly the pargs -e for the openoffice script, when starting manually (not
through SMF), I get:
envp[0]: URE_BOOTSTRAP=file:///opt/openoffice.org3/program/fundamentalrc
envp[1]: _=*20644*/opt/openoffice.org3/program/soffice.bin
envp[2]: DISPLAY=192.168.1.10:1.0
envp[3]:
There is one superb tool which you can't find on any other OS. DTrace ;-)
Take a look eg. here:
http://developers.sun.com/solaris/articles/dtrace_cc.html
--
This message posted from opensolaris.org
___
opensolaris-discuss mailing list
SOLVED folks... perseverance is key...:
I added the following envars to my GlassFish SMF one by one comparing manual to
the SMF way and seeing what happens...:
method_environment
envvar name='DISPLAY' value='192.168.1.10:1.0'/
envvar name='TERM' value='xterm-color'/
Only one of those addresses automatic/stack variables: Purify. Even then, for
Solaris you have to go back to Solaris 10u4 or so to get Purify support.
Yes, dtrace can find memory leaks. But that's kind of like using a crowbar as
a paperweight: it works, but there are a lot easier tools to
kgardas, check out this blog entry that's called Finding memory leaks on
Solaris systems:
http://prefetch.net/blog/index.php/2006/02/19/finding-memory-leaks-on-solaris-systems/
Basically, there's live kernel debugging tool in Solaris called mdb that will
let you debug a live kernel with the
Hi All,
On behalf of the Nexenta project, I'd like to announce the
availability of the Nexenta Core Platform 3.0 Alpha4, the fourth
release in the NCP3 cycle.
You can download the latest iso image from
http://www.nexenta.org/projects/site/wiki/DownloadUnstable
The main changes over the Alpha3
this is confusing to me. The pool was made on all EFI labeled drives
Basically, i did this:
7 raw drives brand new, never formated.
using a OpenSolaris LiveCD i labeled all 7 EFI (format -e then fdisk creat a
single 100% solaris partition, then label EFI)
After doing that, i added the 7
18 matches
Mail list logo
