[osol-help] RE: [osol-discuss] RE: usr/src/tools/proto (was Installing Solaris Sources, onbld tools, compilers)
Hi Rod, Thanks for this help. Actually as given in the steps of the installing the Solaris Source and building it. I performed the following steps. I am sorry but basically I am not able to get the point related to building /sgs/packages. # cd /var/tmp (if you are not currently in this directory) # bzip2 -d SUNWonbld-b47.i386.tar.bz2 (You will get SUNWonbld-b47.i386.tar file as the result of above) # tar xvf SUNWonbld-b47.i386.tar # su (if you haven?t logged in as root) Password: # pkgadd -d onbld SUNWonbld Also request you to please help in using DBG_CALL Functions in the Solaris OS functions which should help me debugging the Solaris OS. Regards Deepak Bhatia -Original Message- From: Rod Evans [mailto:rod.ev...@sun.com] Sent: Thursday, January 11, 2007 1:57 AM To: Deepak Bhatia Cc: opensolaris-help at opensolaris.org; opensolaris-discuss at opensolaris.org Subject: Re: [osol-discuss] RE: usr/src/tools/proto (was Installing Solaris Sources, onbld tools, compilers) Deepak Bhatia wrote: #bldenv -d ./opensolaris.sh Then I goto particular directory to do dmake all. It says sh:/usr/src/cmd/sgs/tools/i386/sgsmsg It looks like this is the continuation of a previous post where you're trying to build the runtime linker :-) As with many subsystems under usr/src, there are dependencies on other components under the source tree. If you run nightly, a full build is carried out in the correct order to make each component follow the build of any of its dependencies. If you have a clean workspace, and descend into a subcomponent area, a make/dmake might not find all the dependencies that are necessary for that subcomponent. If you do a full nightly first, and then descend into the subcomponent area, then the make/dmake should work fine. There are even some tricks under the sgs area that can help you build the runtime linker and all its friends. You'll need a libc_pic.a first - go to usr/src/lib/libc and build the libc targets (make install). Under sgs/packages there are some makefiles and tools that allow the creation of a $MACH/SUNWonld package. This is not part of the product, and isn't exercised by a normal nightly build. This is a special target that allows us to create a package of linker related components for testing. Basically it is simple mechanism of allowing us to create sgs environments without the need for a full nightly. Once you've built a SUNWonld package, you can install it with pkdadd -d SUNWonld, and remove it with pkrm SUNWonld. Take care - it's very easy to turn your system into a brick with just a few ld.so.1 modifications. You might try creating a zone and adding you experimental package to that zone - it's a little easier to recover :-) Hope this helps. Oh, and if you get more linker related issues perhaps you should move your discussion over to tools-linking at opensolaris.org. -- Rod. -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20070113/a768a748/attachment.html
[osol-help] DBG_CALL
Hi Bart, Thanks for your reply. How do I use DBG_CALL to print something on screen or file when running the dynamic linker so that I can track the progress of the dynamic linker ? gards Deepak Bhatia -Original Message- From: Bart Smaalders [mailto:bart.smaald...@sun.com] Sent: Saturday, January 13, 2007 3:41 AM To: DEEPAK BHATIA Cc: opensolaris-help at opensolaris.org Subject: Re: [osol-help] DBG_CALL DEEPAK BHATIA wrote: Hi, There are DBG_CALL statements in the Open Solaris Code. How do we enable them to debug the Solaris OS ? Thanks in advance. Deepak Bhatia You're going to have to be a little more detailed than this. Are you asking what DBG_CALL does? Or how to debug Solaris (which is already far too broad a question to be answered reasonably)? If you examine the source browser, you'll find that DBG_CALL is a macro used for debugging in the linker code: http://src.opensolaris.org/source/xref/scm-migration/onnv-scm/usr/src/cmd/sgs/include/debug.h#143 #define DBG_CALL(func) if (DBG_ENABLED) func - Bart -- Bart Smaalders Solaris Kernel Performance barts at cyber.eng.sun.com http://blogs.sun.com/barts -- next part -- An HTML attachment was scrubbed... URL: http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20070113/ceb844fd/attachment.html
[osol-help] Compose key/unicode problems
Hello all, I'm having some problems with the Compose key, and something related. Here are all the symptoms: - In the C locale, the Compose key doesn't work. - In the en_GB.ISO8859-15 locale, it works (at least with Evolution) - In the en_GB.UTF-8 locale, it doesn't: * firefox, with Compose,A,B only prints character A * evolution prints [?} instead of composed characters * with gaim, when I try to enter a composed character, I get Gtk: file gtktextbuffer.c: line 698: assertion `g_utf8_validate (text, len, NULL)' failed - In any locale, gaim crashes when someone tries to send a composed character to me. I'm not sure what information to send, but: the machine I'm doing this on is an Ultra 60 with a type 5 keyboard, OpenSolaris is a (non-debug) build from November 3, 2006, I'm using Gnome/JDS from build 55. 'locale' says the following: LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 LC_NUMERIC=en_GB.UTF-8 LC_TIME=en_GB.UTF-8 LC_COLLATE=en_GB.UTF-8 LC_MONETARY=en_GB.UTF-8 LC_MESSAGES=en_GB.UTF-8 LC_ALL= Does anybody have any idea what is going on? Kind regards, Jaap Boender This message posted from opensolaris.org
