setting default compiler version
Hi all, I'm using debian sid (updated approx. twice a week) and I want to use gcc 3.4 (to me more specific: g++ 3.4) instead of 3.3.x as my default compiler. It's no problem to install the packages (e.g. g++-3.4), but in /usr/bin the executables gcc and g++ are still linked to the old version (3.3.6 by now). I could change these symlinks by hand, but I dont want to do this because I like the apt-get/dpkg way of handling such things. Is there a way to tell debian to use g++-3.4 as the default compiler and set all symlinks (at least /usr/bin/gcc, /usr/ bin/g++ and /usr/lib/cpp) to the right version using the normal dpkg tools (like dpkg-reconfigure or something like that)? Tnx in advance Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: setting default compiler version
Robert Vangel wrote: > When using Makefile's, look at the CC & GCC environmental variables (I'm > not actually sure if G++ is included there... sorry...) What is the environment variable to set the preprocessor to cpp-3.4 instead of cpp? Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: setting default compiler version
Michael Marsh wrote: > On 5/12/05, Martin Henne <[EMAIL PROTECTED]> wrote: >> What is the environment variable to set the preprocessor to cpp-3.4 >> instead of cpp? > > Often, a Makefile will use the $(CC) variable as its C compiler and > $(CXX) as its C++ compiler, I know that. But what about the preprocessor? > If you only want to run the preprocessor, use "$(CC) -E" > and redirect the output to a file. This is not what I want. Usually, g++ and gcc call a preprocessor. I found, that some configure scripts recognize g++/gcc-3.4 as the compiler, when I set the environment variables CXX and CC, but they complain about /usr/lib/cpp, which is linked to version 3.3.x . In other words, they don't use /usr/lib/cpp-3.4 automatically when using gcc/g++-3.4 . How can I change that? > To try a specific compiler once (with a clean source code directory), > the following should work: > make CC=gcc-3.4 CXX=g++-3.4 Yes, Thats well known. But your answers refer to the compiler, and I asked for the preprocessor! Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: setting default compiler version
Michael Marsh wrote: > The configure scripts are referring to directly to /usr/lib/cpp? If > so, that's a bug. The compiler knows what the right preprocessor to > use is, and it should be making that decision. I agree. But finally I found, that setting the environment variable 'CPP' helped the configure script. So besides CC and CXX, I now set CPP to use the *-3.4 version. Thanx for helping anyway. Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: setting default compiler version
Lee Braiden wrote: > I'm sure there's an official way to do this. If nothing else, you can > edit the global make defaults (probably in /usr/share somewhere?), and > redefine CC > etc. that way. Otherwise, you can set the CC variable and similar > variables in the system-wide profile. O.k., I consider doing that. > I just use a shell script that sets up the variables, then gives me an new > interactive shell to do compilations etc. > > Note that not everything compiles on GCC 4 yet, so even when you get this > working, it might not be as useful as you expect :( As for now, I just need to test gcc 3.4, not gcc 4. But what you said could, of course, apply to gcc 3.4, too. One problem is, that e.g. the nvidia modules does not load into the kernel when compiled with 3.4, for the kernel was compiled using 3.3.x. Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
file/dir rights management
Hi all, On my system I want to keep users from browsing the '/home' directory. Unfortunately, when I do a 'chmod o-r /home', the user can't login via ftp anymore. When the user logs in via ssh, he gets the root directory as its home. He can, however, do a 'cd /home/myhome' then, and then he is in his homedirectory. Similiar with the '/etc' directory. I know, that a normal user cannot change or read passwords, but I want him not to to browse the contents of '/etc'. Can I do this without breaking his ability to login? Tnx in advance Martin -- martin.henne web.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Sid: latest upgrade broke kmail
Hi all, I upgraded my sid today and kmail crashes when started. The debugger says, there's a segfault in QString in libqt-mt.so.3, but while knode and e.g. kdevelop3 is not affected, I could not believe it's QString, because this class is used almost everywhere at KDE (at least I think it is). The problem has been reported in an italian newsgroup, but as I dont speak italien, I posted it here. Does anyone else have this problem? Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
