Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-19 Thread Joerg Schilling
Bart Smaalders [EMAIL PROTECTED] wrote: Both the original SPARC 64 bit port and the amd64 bit port were started with gcc. Solaris 10's x64 binaries are I thought that in 1996, there was no 64 bit sparc support in GCC. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-19 Thread Darren J Moffat
Joerg Schilling wrote: Bart Smaalders [EMAIL PROTECTED] wrote: Both the original SPARC 64 bit port and the amd64 bit port were started with gcc. Solaris 10's x64 binaries are I thought that in 1996, there was no 64 bit sparc support in GCC. maybe not in the publically available GCC but

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-18 Thread Darren J Moffat
[EMAIL PROTECTED] wrote: Perhaps engineering resources that went into making OpenSolaris GCC-friendly would have been better spent porting SS10 to other platforms? Were I the manager that had the power to decide, I would have certainly pushed in that direction, not the other way around. The

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-18 Thread Martin Bochnig
Darren J Moffat wrote: [EMAIL PROTECTED] wrote: Perhaps engineering resources that went into making OpenSolaris GCC-friendly would have been better spent porting SS10 to other platforms? Were I the manager that had the power to decide, I would have certainly pushed in that direction, not

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-18 Thread Martin Bochnig
Martin Bochnig wrote: Darren J Moffat wrote: We also now have a fantastic system for building the source with multiple compliers. Using multiple different compliers is a great way to find interesting bugs in the compiler and in the code you are building. Also the Studio compilers are free

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-18 Thread Martin Bochnig
And ON's gcc-shadow compilation does indeed uncover potential bugs, that might not have been detected otherwise. ___ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-18 Thread Martin Bochnig
Perhaps engineering resources that went into making OpenSolaris GCC-friendly would have been better spent porting SS10 to other platforms? Were I the manager that had the power to decide, I would have certainly pushed in that direction, not the other way around. I heavily doubt, this would

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-17 Thread Casper . Dik
Perhaps engineering resources that went into making OpenSolaris GCC-friendly would have been better spent porting SS10 to other platforms? Were I the manager that had the power to decide, I would have certainly pushed in that direction, not the other way around. The reasons those engineering

RE: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-17 Thread george r smith
Why would Sun be so keen to pay people to port Solaris (which has a price tag = FREE) and help HP, IBM etc to sell their hardware? It would end up being Sun paying to port the code. HP and IBM selling the hardware, and HP and IBM getting support contracts for maintaining Solaris on HP and

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-17 Thread Bart Smaalders
UNIX admin wrote: Perhaps engineering resources that went into making OpenSolaris GCC-friendly would have been better spent porting SS10 to other platforms? Were I the manager that had the power to decide, I would have certainly pushed in that direction, not the other way around. Both the

Re: [osol-discuss] Re: Re: Porting Virtualbox to Opensolaris X86

2007-01-17 Thread Patrick Mauritz
george r smith wrote: My question is why isn't Sun keen in porting Eclipse to Solaris 10 (x86) and help those of us who bought Sun boxes. I know about Netbeans but do a search it is not used nearly as much as Ecliplse. Maybe because Eclipse isn't pure java (trademark or not), so the guards