March 2004 - openSUSE Programming - openSUSE Mailing Lists

Is anybody here using this? http://www.boost.org/
by Steven T. Hatton 15 Mar '04

15 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 http://www.boost.org/ The Boost web site provides free peer-reviewed portable C++ source libraries. The emphasis is on libraries which work well with the C++ Standard Library. The libraries are intended to be widely useful, and are in regular use by thousands of programmers across a broad spectrum of applications. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFATLk7wX61+IL0QsMRAhrjAJsEcbwrAnVQeYm6hnbp0KC9LDVq1wCfcyw9 ZTz9vLq83vlkcJzl/zB3hTE= =wIYX -----END PGP SIGNATURE-----

8 14

Getting GCC to tell me what it sees?
by Steven T. Hatton 14 Mar '04

14 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a way to get GCC to show all the information relevant to building? IOW, the include path it will use, the places it will look for libraries, etc? I'm not really sure what I'm asking, but I'll know it when I see it. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAU5GBwX61+IL0QsMRAjHMAJ96EG/mMlLd/gwREzEnKZQhxqrsXQCgzfd0 W5Jfhcs3gAiJWFZiRhUHc20= =0qav -----END PGP SIGNATURE-----

2 1

Ant compared to Autotools
by Steven T. Hatton 14 Mar '04

14 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have to admit, I have never gained a good sense of how to use the gnu Autotools, though I've spent far more time trying than I have with Ant. TrollTech's qmake, OTOH, is very easy to learn. It may simply be the case that Ant hasn't attempted the more complex things Autotools address. I can see some things in Ant which if not addressed soon will lead to the same kinds of obscurity I find in the Autotools. One of the problems I had with Autotools is that the Cygwin install I used had two different versions installed, and I was reading man pages from one version while working with another. /That/ is not a reflection on the difficulty of using Autotools. Nonetheless, when I do look at the documentation, I find myself following references to other documents which are not consistent with the reffering document. KDevelop will generate the files I need for this task, and thus far, I've been able to use the generated results without a problem. However, when I try to understand what all of it means, I am at a loss. Is there a problem brewing with this system? When one script generates another, which generates yet another, it seems there is a potential for the result to become incomprehensible even to the creators of the tools. Does anybody share my concern? STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAQWNFwX61+IL0QsMRAi+HAKCSbJ1qUSd7XB9+f/dHAoK5t1vwfQCcDTg7 UYxEAlpymyIgr1eVT930Svw= =9N51 -----END PGP SIGNATURE-----

9 32

New installation :-)
by Michel Briand 12 Mar '04

12 Mar '04

Dear SuSE users, I've used SuSE since version 6.x, five or six years ago, and now I'm coming back to version 9.0. I've installed Suse 9 on a Serial bases system and installation DVD/CD can't handle such hardware configuration. I've been forced to turn my SATA controler in compatibility mode for Suse to install. Note: on my DVD the media.1/* and media.2/* files are somewhat corrupted and Yast complained about I/O error. I copied those file from CD1. Then I copied entire DVD to my hard disk. I set up a kernel myself (2.6.4-rc2) with my old Linux installation and I modified Grub accordingly. Everything went fine. Except a few warning during init due to Suse init scripts wanting to set up minor console ioctl pertaining to Suse modified kernel. Note about NVIDIA: I own an NVIDIA Quadro 4 XGL. I wanted to use NVIDIA provided drivers. But neither Yast2 nor YOU succeded in installing NVIDIA drivers displayed in patch listing. Although Yast installed correctly the nvidia.o driver for the Suse kernel, it didn't installed the remaining stuff of NVIDIA provided files (libraries and X11 driver). I installed theses files extracting manually the NVIDIA package and executing manually "make install". What was my surprise when I discovered that Suse didn't provide neither MPlayer neither transcode ! I'll have to build those things myself ;-). I needed GLEW library for my developments so I tried krpmbuilder to create one from sources. I went into an ugly issue : dependencies. Although I specified libGL.so.1 in dependencies through krpmbuilder (and I checked the spec file : libGL.so.1 was in Requires string), rpm complained about missing libGL.so.1. Whereas it was installed by XFree86-mesa-devel on my system. Here is what rpm says: error: Failed dependencies: libGL.so.1(LIBGL) is needed by glew-1.2.0-SuSE9.0 I wonder why I was force to say "-SuSE9.0" in krpmbuilder. And I wonder why rpm searches for (LIBGL) tag ??? Anyone master "build" and rpm to help me create a robust spec file for GLEW ? And it would be nice to discuss with GLEW team about tarball naming convention, and installation directories conventions... I attached my somewhat "alpha" spec file. Regards, M.B. Name: glew Summary: OpenGL Extension Wrangler Library Version: 1.2.0 Release: SuSE9.0 License: GPL Group: Développement/Bibliothèques/X11 Source: %{name}-%{version}.tar.gz BuildRoot: %{_tmppath}/build-root-%{name} Packager: Michel Briand Distribution: SuSE Prefix: /usr Url: http://glew.sourceforge.net Provides: libGLEW.so.1 Vendor: GLEW Requires: ld-linux.so.2 %description The goal of the OpenGL Extension Wrangler Library (GLEW) is to assist C/C++ OpenGL developers with two tedious tasks: initializing and using extensions and writing portable applications. GLEW provides an efficient run-time mechanism to determine whether a certain extension is supported by the driver or not. OpenGL core and extension functionality is exposed via a single header file. GLEW currently supports a variety of platforms and operating systems, including Windows, Linux, Darwin, Irix, and Solaris. %prep rm -rf $RPM_BUILD_ROOT mkdir $RPM_BUILD_ROOT %setup -q %build CFLAGS="$RPM_OPT_FLAGS" CXXFLAGS="$RPM_OPT_FLAGS" \ ./configure --prefix=%{prefix} make %install make GLEW_DEST=$RPM_BUILD_ROOT/usr install cd $RPM_BUILD_ROOT find . -type d -fprint $RPM_BUILD_DIR/file.list.%{name}.dirs find . -type f -fprint $RPM_BUILD_DIR/file.list.%{name}.files.tmp sed '/\/man\//s/$/.gz/g' $RPM_BUILD_DIR/file.list.%{name}.files.tmp > $RPM_BUILD_DIR/file.list.%{name}.files find . -type l -fprint $RPM_BUILD_DIR/file.list.%{name}.libs sed '1,2d;s,^\.,\%attr(-\,root\,root) \%dir ,' $RPM_BUILD_DIR/file.list.%{name}.dirs > $RPM_BUILD_DIR/file.list.%{name} sed 's,^\.,\%attr(-\,root\,root) ,' $RPM_BUILD_DIR/file.list.%{name}.files >> $RPM_BUILD_DIR/file.list.%{name} sed 's,^\.,\%attr(-\,root\,root) ,' $RPM_BUILD_DIR/file.list.%{name}.libs >> $RPM_BUILD_DIR/file.list.%{name} %clean rm -rf $RPM_BUILD_ROOT rm -rf $RPM_BUILD_DIR/file.list.%{name} rm -rf $RPM_BUILD_DIR/file.list.%{name}.libs rm -rf $RPM_BUILD_DIR/file.list.%{name}.files rm -rf $RPM_BUILD_DIR/file.list.%{name}.files.tmp rm -rf $RPM_BUILD_DIR/file.list.%{name}.dirs %files -f ../file.list.%{name} %defattr(-,root,root,0755)

2 1

newbie qmake issue - multi threading package?
by Allen Seelye 12 Mar '04

12 Mar '04

I really have two issues here but I think they both are symptoms of the same problem so I've stuck them both in the same message here. I'm trying to compile the famous 'hello world' program. The first issue I'm running into is tellng qmake the location of qapplication.h or any include files at all. I have QTDIR set, as well as the appropriate entry in ld.so.conf but it still cannot find those files unless I include the complete path in the #include entry. Then I run into the second issue. When compiling I get this error: .../bin/ld: cannot find -lqt-mt collect2: ld returned 1 exit status make: *** [hello_world] Error 1 My googling has led me to believe that I need to install the qt-mt package (or something along those lines) but I have been unable to find any such package. I'm using suse 9.0 and qt is installed from the suse 9.0 packages, NOT from sources. Any hint is appreciated. -- Allen Seelye Alleninmt(a)yahoo.com A Linux user since 1999. --------------- "It's a trick, get an axe."

7 13

A short yet complete set of C++ pointer examples?
by Steven T. Hatton 12 Mar '04

12 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I am interested to know if there is a web site, or howto that presents all the different forms of pointer and reference usage in the C++ language. I would also like to know if there is a short accurate discussion of Class instantiation mechanics. Not one focusing on the language rules, but one focusing on the runtime structure and its relationship the the source code. I've found understanding such concepts helps me understand a language better. Any suggestions? STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFARyJIwX61+IL0QsMRAjsIAJ4ovYeo+iVnW2Oa0KT3eMuVLvS1dACg2bTj qDviEqePS2bkWAWTrkij9co= =9hv2 -----END PGP SIGNATURE-----

5 13

wxWindows looks terrible
by Kenneth Payne 09 Mar '04

09 Mar '04

I'm just experimenting with wxPython coding with wxWindows on SuSE 9.0. However, my application looks awful. And it's not my code - the demo apps look awful too. The font is ugly (every font you pick looks just the same) and the general look and feel is terrible. Since wxWindows on Linux is based on gtk, I assume this is because my gtk installation isn't properly themed or set up. Does anyone know how to fix this? My desktop is KDE so I do not have Gnome installed, but I run gtk-based apps like Gimp and Eclipse and they look fine. Best wishes - Ken

1 0

C/C++ according to IBM
by Steven T. Hatton 09 Mar '04

09 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I haven't had much opportunity to read from this, but I recognize the presentation style as similar to that used by Cooper in his Pascal book. I happen to like that style. hpcf.nersc.gov/vendor_docs/ibm/vac/sc094957.pdf I also broke down and purchased the ISO C++ standard in PDF. Believe it or not, it /is/ the kind of document that I tend to gain a lot from reading. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFATiTDwX61+IL0QsMRAs0eAJ0TJJro3PbDiARIq0CSn8CfFO/HbwCeLBmg ufGyg/FzJn9jOHhEDaM9jk0= =6lIF -----END PGP SIGNATURE-----

1 0

Purchase the Syntactic Metalanguage. Extended BNF Standard
by Steven T. Hatton 07 Mar '04

07 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 24 pages! Information technology. Syntactic Metalanguage. Extended BNF Document Number: BS ISO/IEC 14977:1996 British Standard / ISO/IEC 15-Feb-1998 ISBN: 0 580 29189 8 24 pages (English) $129.50 USD http://www.techstreet.com/cgi-bin/detail?product_id=1123162 How do *you* spell photocopy? STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAS1VFwX61+IL0QsMRAm1vAJ0Y/C/Akev2NOYvvSMYc58ecZqhWQCfZy77 ltefIWP+UQaCyFytxqKuXCc= =QPxb -----END PGP SIGNATURE-----

1 0

05 Mar '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There's some good stuff here if you like to know about the innere workings of programs/languages such as bash. http://www.opengroup.org/onlinepubs/007908799/ BTW, I haven't bailed on the pointer thread. I'll be back in about a day. Hint: I'm thinking operator _binding_priority_, and order of execution are essential to understanding this stuff. But that really should go with the other thread. STH -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFASKPgwX61+IL0QsMRAvd8AKDVX7p+db1unfweq/JLVBd6wajtWQCg7Ny1 Y2mgcbRWf/oLdUORp/kvYVk= =0sbw -----END PGP SIGNATURE-----

1 0