Mark Wright wrote: > Hello Morten, > > I will answer things in reverse order from your email: > > Sun C++ and g++ object incompatible > -----------------------------------
I have read and understood all of it, I prefer if possible to do the upgrades through blastwave, which is the common way to and to me the easiest way to upgrade. I had nothing more to do than contact the maintainers. Mr Robin Kay is now informed. The main goal is obviously to use DTrace and sun studio. first for cxxtools, then for tntnet. And to port that to Nexenta. That is helpful for me if I can succesfully contribute, understand, use and promote tntnet on opensolaris, and to document and maintain that. I had hoped that compiling cxxtools on the very latest solaris express developer edition, which basically is opensolaris, could be an easy job. <Mark> I've never tried compiling it with g++ on Solaris. If you like I can try compiling it with SFEgcc: </Mark> I prefer that the Blastwave maintainers can comment on that. Most linux users like and prefer gcc, which is good for ANSI C and kernel compilation, but not for templates and C++. The error messages and warnings I get from Sun studio C++ are superior. If most Linux Gnu software runs fine with the current versions I can see no reason to change that. On sun microsystem meetings and from the sun webpage we don't even need to download anything, I simply click and get the software next day through post. Including Sun Studio and DTrace. So I think we can forget gcc for this job and port the source code to solaris, open solaris and later to nexenta. I'm looking for an easy way to prepare the compiler for that. A workaround could be to create a solaris zone or container and create a debian virtualized, but that is not what I'm looking for. <Mark> The Blastwave stuff is probably great for some software packages, however for development tools it does not seem up to date enough. In particular, the Blastwave libtool is also too old. Hence I think you will need to remove the Blastwave autotools. pkgrm CSWlibtool pkgrm CSWautomake pkgrm CSWautoconf Then you need pkgbuild from the CBD JDS: http://www.opensolaris.org/os/project/jds/contributing/building/ However the subversion in CBS JDS 1.6.0 is too old, so you need to uinstall it, something like pkgrm CBEsvn </Mark> This is most likely true, but I prefer to discuss that with the blastwave maintainers first. the situation is similar between debian and fedora, fedora has the latest updates, good for developers. debian has better tested and generally more stable tools, but not the latest versions. It also has SID unstable | stable brandings. The way we can now get solaris out of the box could need an update. pkgbuild from the CBD JDS: I found, which is new to me. OpenSolaris Project: Java Desktop System: A GNOME-based desktop http://www.opensolaris.org/isearch.jspa?query=tntnet&Submit=Search Site Search Sorry, there were no matches for tntnet. Discussions Search Sorry, there were no matches for tntnet. I'd like to see OpenSolaris Project: TNTnet a new web application server. Which could mean even more work (for me). Best regards Morten ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
