From ghenry at cmi.univ-mrs.fr Thu Apr 8 10:08:30 2010 From: ghenry at cmi.univ-mrs.fr (gerard) Date: Thu, 08 Apr 2010 10:08:30 +0200 Subject: [csw-users] evince seg fault In-Reply-To: <4BACE15C.9040305@opencsw.org> References: <4BACB0B8.3050408@cmi.univ-mrs.fr> <4BACDB18.1040400@opencsw.org> <4BACE15C.9040305@opencsw.org> Message-ID: <4BBD8EFE.9010206@cmi.univ-mrs.fr> hello all, any news for this problem? gerard From ja at opencsw.org Sun Apr 11 21:54:28 2010 From: ja at opencsw.org (Juergen Arndt) Date: Sun, 11 Apr 2010 21:54:28 +0200 Subject: [csw-users] Packages for nagios, nrpe and nsca in experimental Message-ID: Hello, there are new packages for Nagios, NRPE and NSCA available from http://mirror.opencsw.org/experimental.html#ja Be aware that config files were moved to /etc/opt/csw - for Nagios this is not automatically done. You have to change the path names in your config files too. Look at [1] for more instructions. Feedback is very welcome. Juergen [1] http://wiki.opencsw.org/nagios -- Juergen Arndt From jplana at gmail.com Sat Apr 17 15:02:52 2010 From: jplana at gmail.com (=?iso-8859-15?Q?Jos=E9_Plana?=) Date: Sat, 17 Apr 2010 15:02:52 +0200 Subject: [csw-users] Problems with python hashlib Message-ID: Hi all, I wonder if anybody has had problems with the hashlib library of python used mainly for its md5 functions. After installing CSWpython (python 2.6.4), I go this error: "ImportError: No module named _md5" It can be reproduced with: /opt/csw/lib # python Python 2.6.4 (r264:75706, Feb 15 2010, 16:34:20) [C] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from hashlib import md5 Traceback (most recent call last): File "", line 1, in File "/opt/csw/lib/python/hashlib.py", line 136, in md5 = __get_builtin_constructor('md5') File "/opt/csw/lib/python/hashlib.py", line 63, in __get_builtin_constructor import _md5 ImportError: No module named _md5 digging a little I found that python uses /opt/csw/lib/python/lib-dynload/_hashlib.so so I did # ldd /opt/csw/lib/python/lib-dynload/_hashlib.so libssl.so.0.9.8 => (archivo no encontrado) libcrypto.so.0.9.8 => (archivo no encontrado) libpython2.6.so.1.0 => /opt/csw/lib/libpython2.6.so.1.0 libresolv.so.2 => /lib/libresolv.so.2 libsocket.so.1 => /lib/libsocket.so.1 libnsl.so.1 => /lib/libnsl.so.1 librt.so.1 => /lib/librt.so.1 libdl.so.1 => /lib/libdl.so.1 libpthread.so.1 => /lib/libpthread.so.1 libm.so.1 => /lib/libm.so.1 libc.so.1 => /lib/libc.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libaio.so.1 => /lib/libaio.so.1 libdoor.so.1 => /lib/libdoor.so.1 libuutil.so.1 => /lib/libuutil.so.1 libgen.so.1 => /lib/libgen.so.1 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Sun-Blade-T6320/lib/libc_psr.so.1 /platform/SUNW,Sun-Blade-T6320/lib/libmd_psr.so.1 I searched for libssl.so.0.9.8 and libcrypto.so.0.9.8, provided by openssl (already installed): /opt/csw/lib/python # pkg-get install openssl No worries... you already have version 0.9.8n,REV=2010.03.25 of openssl If you doubt this message, run 'pkg-get -U', then run 'pkg-get upgrade openssl' # find / -name "libssl.so.0.9.8" /opt/csw/lib/sparcv8plus+vis/libssl.so.0.9.8 /opt/csw/lib/sparcv9/libssl.so.0.9.8 # find / -name "libcrypto.so.0.9.8" /opt/csw/lib/sparcv8plus+vis/libcrypto.so.0.9.8 /opt/csw/lib/sparcv9/libcrypto.so.0.9.8 as both libraries where already installed, I sym-linked where they could be found: # ln -s /opt/csw/lib/sparcv8plus+vis/libcrypto.so.0.9.8 /opt/csw/lib/libcrypto.so.0.9.8 # ln -s /opt/csw/lib/sparcv8plus+vis/libssl.so.0.9.8 /opt/csw/lib/libssl.so.0.9.8 # ldd /opt/csw/lib/python/lib-dynload/_hashlib.so libssl.so.0.9.8 => /opt/csw/lib/libssl.so.0.9.8 libcrypto.so.0.9.8 => /opt/csw/lib/libcrypto.so.0.9.8 libpython2.6.so.1.0 => /opt/csw/lib/libpython2.6.so.1.0 libsocket.so.1 => /lib/libsocket.so.1 libnsl.so.1 => /lib/libnsl.so.1 libdl.so.1 => /lib/libdl.so.1 libresolv.so.2 => /lib/libresolv.so.2 librt.so.1 => /lib/librt.so.1 libpthread.so.1 => /lib/libpthread.so.1 libm.so.1 => /lib/libm.so.1 libc.so.1 => /lib/libc.so.1 libmp.so.2 => /lib/libmp.so.2 libmd.so.1 => /lib/libmd.so.1 libscf.so.1 => /lib/libscf.so.1 libaio.so.1 => /lib/libaio.so.1 libdoor.so.1 => /lib/libdoor.so.1 libuutil.so.1 => /lib/libuutil.so.1 libgen.so.1 => /lib/libgen.so.1 libm.so.2 => /lib/libm.so.2 /platform/SUNW,Sun-Blade-T6320/lib/libc_psr.so.1 /platform/SUNW,Sun-Blade-T6320/lib/libmd_psr.so.1 which seems to work fine: # python Python 2.6.4 (r264:75706, Feb 15 2010, 16:34:20) [C] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> from hashlib import md5 >>> am I missing something? Is this the correct behaviour? From maciej at opencsw.org Sat Apr 17 15:23:31 2010 From: maciej at opencsw.org (Maciej (Matchek) Blizinski) Date: Sat, 17 Apr 2010 14:23:31 +0100 Subject: [csw-users] Problems with python hashlib In-Reply-To: References: Message-ID: No dia 17 de Abril de 2010 14:02, Jos? Plana escreveu: > # find / -name "libssl.so.0.9.8" > /opt/csw/lib/sparcv8plus+vis/libssl.so.0.9.8 > /opt/csw/lib/sparcv9/libssl.so.0.9.8 Looking at http://www.opencsw.org/search/openssl_rt it seems like the files are indeed missing from the package. I'd say it's a bug in the openssl package. Yann, what do you think? Maciej From maciej at opencsw.org Sat Apr 17 15:29:29 2010 From: maciej at opencsw.org (Maciej (Matchek) Blizinski) Date: Sat, 17 Apr 2010 14:29:29 +0100 Subject: [csw-users] Problems with python hashlib In-Reply-To: References: Message-ID: No dia 17 de Abril de 2010 14:23, Maciej (Matchek) Blizinski escreveu: > Looking at http://www.opencsw.org/search/openssl_rt it seems like the > files are indeed missing from the package. No, I'm blind. The package is OK. I was looking for /opt/csw/lib/sparcv8, I don't know why. The /opt/csw/lib/libssl.so.0.9.8 file is in the package, and the others are too. This would point to a problem with your installation. Perhaps the files were accidentally removed? The removal could happen during an upgrade, for example when you use pkg-get and files are moved from one package to another. Here's a case that might be similar to yours: http://www.opencsw.org/mantis/view.php?id=4004 Maciej From jplana at gmail.com Sat Apr 17 16:27:01 2010 From: jplana at gmail.com (=?iso-8859-15?Q?Jos=E9_Plana?=) Date: Sat, 17 Apr 2010 16:27:01 +0200 Subject: [csw-users] Problems with python hashlib References: Message-ID: En Sat, 17 Apr 2010 15:29:29 +0200, Maciej (Matchek) Blizinski escribi?: Hi > No dia 17 de Abril de 2010 14:23, Maciej (Matchek) Blizinski > escreveu: >> Looking at http://www.opencsw.org/search/openssl_rt it seems like the >> files are indeed missing from the package. > > No, I'm blind. The package is OK. I was looking for > /opt/csw/lib/sparcv8, I don't know why. The > /opt/csw/lib/libssl.so.0.9.8 file is in the package, and the others > are too. This would point to a problem with your installation. > Perhaps the files were accidentally removed? > The files are present, in /opt/csw/lib/sparcv8plus+vis/, however my installation procedure was non standard, as I upgraded from blastwave to opencsw packages. > The removal could happen during an upgrade, for example when you use > pkg-get and files are moved from one package to another. Here's a > case that might be similar to yours: > http://www.opencsw.org/mantis/view.php?id=4004 > The curious thing is that I removed openssl with pkgrm and then tried to install again with pkg-get. If there's nobody else reporting the same problem then it's probably just my installation. Thanks for your help! > Maciej From George.Wyche at pw.utc.com Thu Apr 22 21:31:05 2010 From: George.Wyche at pw.utc.com (Wyche, George PW) Date: Thu, 22 Apr 2010 15:31:05 -0400 Subject: [csw-users] mesalibs mglu versus glu Message-ID: <239E996F5C620A4E8A369B7D818326B20117BF91@PUSMNEI1.pwemail.us> As a sparc Solaris8 user today I did "pkg-get -I mesalibs glut" I compiled a c program against (sparc) /opt/csw/lib/libGLU.so which left numerous, suspicious undefined symbols all starting with mglu. I spent some time looking around the internet and this is not an uncommon problem, but I do not understand how I can solve it. None of the messages went into detail about the nature of the problem, but nearly all solutions had to do with modifying the ***library*** makefile, taking that solution out of my ballpark. Things like glu.exports glu.exports.in mangle.h were mentioned. There were mumbles that the mglu... were meant to be internal library references, but somehow our Solar loader (and other unix loaders) sees them as unsatisfied externals and won't make my executable. To whom might I address this issue further? George Wyche From George.Wyche at pw.utc.com Tue Apr 27 17:33:33 2010 From: George.Wyche at pw.utc.com (Wyche, George PW) Date: Tue, 27 Apr 2010 11:33:33 -0400 Subject: [csw-users] mesalibs mglu versus glu Message-ID: <239E996F5C620A4E8A369B7D818326B2011A43E9@PUSMNEI1.pwemail.us> Paul Lanken suggests checking out BlastWave which, presciently it would seem, now uses Solaris10 as its base level, instead of pursuing my wonderment here at opencsw which very recently abandoned Solaris8 as its base level. I don't like mixing and matching. I get into trouble (faster) when I do that. But following Mr. Lanken's lead I suppose I should investigate Mr. Christensen's sunfreeware, too. I started with them lo' these many years ago. Bigger picture efforts would be to fight (much) harder to get all these Sun workstations redone with Solaris10 to try and stay (not ahead) up with the game. However, management, rightly so, is not interested in such activity unless it translates rather directly into "positive" cash flow. As a programmer I am not highly motivated to put together a "business plan" whose myopic goal is attempting to link a rather simple glut program. ggw From dam at opencsw.org Tue Apr 27 17:43:24 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 27 Apr 2010 17:43:24 +0200 Subject: [csw-users] mesalibs mglu versus glu In-Reply-To: <239E996F5C620A4E8A369B7D818326B2011A43E9@PUSMNEI1.pwemail.us> References: <239E996F5C620A4E8A369B7D818326B2011A43E9@PUSMNEI1.pwemail.us> Message-ID: <53A0C43D-4693-4072-AEA7-4DCCC6F5C70F@opencsw.org> Hi George, Am 27.04.2010 um 17:33 schrieb Wyche, George PW: > Paul Lanken suggests checking out BlastWave Please notice that Paul Lanken is heavily biased towards Blastwave and IMHO uses unacceltable wording. Please take a look at his last postings at > I don't like mixing and matching. I get into trouble (faster) when I > do > that. But following Mr. Lanken's lead I suppose I should investigate > Mr. > Christensen's sunfreeware, too. I started with them lo' these many > years > ago. I started writing a comparison of Solaris packages distributions at It is currently at draft level, but feel free to take a look and comment. In fact, SFW is very much different from OpenCSW as outlined there. Best regards -- Dago From dam at opencsw.org Tue Apr 27 17:45:00 2010 From: dam at opencsw.org (Dagobert Michelsen) Date: Tue, 27 Apr 2010 17:45:00 +0200 Subject: [csw-users] mesalibs mglu versus glu In-Reply-To: <239E996F5C620A4E8A369B7D818326B20117BF91@PUSMNEI1.pwemail.us> References: <239E996F5C620A4E8A369B7D818326B20117BF91@PUSMNEI1.pwemail.us> Message-ID: <04D28497-1007-4B58-98D7-B5F6AE14F265@opencsw.org> Hi George, Am 22.04.2010 um 21:31 schrieb Wyche, George PW: > As a sparc Solaris8 user today I did "pkg-get -I mesalibs glut" > > I compiled a c program against (sparc) /opt/csw/lib/libGLU.so which > left > numerous, suspicious undefined symbols all starting with mglu. I spent > some time looking around the internet and this is not an uncommon > problem, but I do not understand how I can solve it. > > None of the messages went into detail about the nature of the problem, > but nearly all solutions had to do with modifying the ***library*** > makefile, taking that solution out of my ballpark. Things like > glu.exports glu.exports.in mangle.h were mentioned. There were mumbles > that the mglu... were meant to be internal library references, but > somehow our Solar loader (and other unix loaders) sees them as > unsatisfied externals and won't make my executable. > > To whom might I address this issue further? James is maintaining mesa and he may suggest something. I have put him on cc'. Best regards -- Dago