Comments on: Using Alternate Compilers

Comment on Using Alternate Compilers by: Prabhu

Mon, 11 Jun 2007 11:02:57 +0000

Hi,
Could you please tell me how do we disable auto configuration ( stateless
FE80::) address in linux. Do we have any command or need to change any of config file in linux.

Thanks,
Prabhu

Comment on Using Alternate Compilers by: Moritz Barsnick

Wed, 10 Jan 2007 15:24:41 +0000

All autoconf based packages support
PROMPT> CC=mycompiler CXX=myothercompiler ./configure
These variables therefore also work with rpmbuild (if exported).

Most regular Makefiles also support CC/CXX make variables (note: not environment variables). But there’s no default rpmbuild method to pass them in, without modifying at least the SPEC file. Therefore, IMHO, there should be a requirement for SPEC files to properly evaluate CC/CXX.

E.g. (not-autoconf based):
Modify the SPEC file line
make
to read
make CC=${CC:-gcc} CXX=${CXX:-g++}

I have stumbled across this tens of times while trying to (re)build with the Intel C++ Compiler (with programs called “icc” and “icpc”). (Autoconf-based packages are fine, as I’d like to stress again, and these make up some 90% or so of the distribution, I guess.)

Is it fair to submit bugzilla bugs against these SPEC files? Could there be a common understanding (especially among the build system folks) that this is a necessity?

Thanks,
Moritz

Comment on Using Alternate Compilers by: Krolyn

Fri, 01 Sep 2006 14:34:37 +0000

Hi all,

I’ve had a similar problem. I needed to compile a program with gcc-3.2.3 and so installed compat-gcc-32. the compiler works perfectly (must use gcc32 instead og gcc) but I have no java support since gcj is only installed in the 4.1 version. Any idea how to use gcj with gcc-3.2.3??

thans in adv

Comment on Using Alternate Compilers by: Awais

Sat, 22 Jul 2006 18:02:04 +0000

Changing Default GCC
I have to change the gcc version from the default 3.x or 4.x to gcc2.95 as I am working in NS which does not even comple with gcc3.x.
What I do is install the gcc2.95 in /opt and change the system variables for path etc in /etc/bashrc to include the /opt before /usr/bin/blah_blah
Furthermore the gcc2.95 doesnt compile with gcc4.x so I have to first compile it with gcc3.x and then use it to install the version of NS I usually work on.

For further inquiries or details you can contact me at awais(dot)lodhi(at)gmail(dot)com

Comment on Using Alternate Compilers by: Mauriat

Wed, 12 Apr 2006 13:29:21 +0000

Dinh:
How did you install gcc3.4.3? (Did you install yourself? Or did you use a supported RPM?)
What program are you trying to compile?

You can only run ‘make c++=g++34′ if the ‘Makefile’ you are using supports the variable ‘c++’. Open ‘Makefile’ and look for that variable.

Comment on Using Alternate Compilers by: Dinh

Wed, 12 Apr 2006 13:24:09 +0000

I have a gcc4.0 on my Mandriva and I need to run programs with gcc3.4.3. I installed gcc3.4.3 but then I dont know how to change gcc3.4.3 as default compiler? Any help please?

In the discussion below, did u mean: If I use “make c++=g++34″, my program will be compiled with gcc3.4?

Thanks

Comment on Using Alternate Compilers by: Chris

Wed, 22 Mar 2006 21:43:20 +0000

Finally, FINALLY someone explains this. I have had a migraine since 4.x was released. In most cases this works. “Some” is an understatement when it comes to software that does not compile on Suse 10 or Fedora 4 if you ask me, its about 95%. Thanks for Posting this I am very greatful for the information!!!

Comment on Using Alternate Compilers by: Mauriat

Fri, 27 Jan 2006 12:59:20 +0000

Aaron: You are correct. Thanks

Comment on Using Alternate Compilers by: Aaron

Fri, 27 Jan 2006 04:28:08 +0000

# export CC=gcc32
# export CPP=g++32
# ./configure

Please note, it only worked for me when I used CXX (C++ compiler) instead of CPP (pre-processor).