1

I'm trying to build python 2.6.8 from source code on an AIX 6.5 machine, but several modules can't build successful. In the build process, there is a XLC man page jumps out and stucks. I have to press q to end the man page and the process will continue. So I'm thinking whether is because the build invokes the default XLC compiler, and I'm trying to change the default compiler to g++:

make clean
CC=/bin/gcc CXX=/bin/g++ ./configure
make

But it seems doesn't work, the XLC man page still pops up, and the moduls fail to build.

How can I make sure it will use g++ instead of XLC? Thanks.

Update

This is the log after CC=/bin/gcc CXX=/bin/g++ ./configure

-bash-3.2$ CC=/bin/gcc CXX=/bin/g++ ./configure
checking for --enable-universalsdk... no
checking for --with-universal-archs... 32-bit
checking MACHDEP... aix6
checking EXTRAPLATDIR... 
checking machine type as reported by uname -m... 00F63F144C00
checking for --without-gcc... 
checking for gcc... cc_r
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... no
checking whether cc_r accepts -g... yes
checking for cc_r option to accept ISO C89... -qlanglvl=extc89
checking for --with-cxx-main=<compiler>... no
checking how to run the C preprocessor... cc_r -qlanglvl=extc89 -E
checking for grep that handles long lines and -e... /opt/freeware/bin/grep
checking for egrep... /opt/freeware/bin/grep -E

In that I see the line checking whether we are using the GNU C compiler... no, does that mean it is not using the gcc?

And also in the log of make 

checking for __attribute__((visibility("hidden")))... no
cc_r: 1501-210 (W) command option t contains an incorrect subargument

right after the above log, the man page of xlc pops up.

xslittlegrass
  • 4,826
  • 4
  • 26
  • 32
  • Look at the logs, are you sure xlc is still used? Generally, `CC` should be `gcc` and `CXX` should be `g++`. Does your machine really have `g++` installed in `/bin`? – n. m. could be an AI Mar 18 '13 at 16:32
  • @n.m. Thanks. I'm not sure xlc is in using. Yes it has g++. In the log I see lines like `for gcc... cc_r`,`whether the C compiler works... yes`, `whether we are using the GNU C compiler... no`, does that mean it will not using gcc? – xslittlegrass Mar 18 '13 at 17:53
  • The script thinks `gcc` is called `cc_r`. Perhaps real gcc was not found. Use `./configure CC=gcc`, look [here](http://www.gnu.org/prep/standards/html_node/Configuration.html). – n. m. could be an AI Mar 18 '13 at 19:10
  • @n.m. I use `./configure CC=gcc` and everything is exactly the same. Any ideas? – xslittlegrass Mar 18 '13 at 19:59
  • Do you really really really have gcc installed in `/bin`? Not `/usr/bin`, not `/usr/local/bin`? If so there's very little one can do beside opening up the `configure` script and starting to debug it line by line. – n. m. could be an AI Mar 19 '13 at 09:31
  • @n.m. Yes, it has `gcc` and `g++` in `/bin`:`-bash-3.2$ ls /bin/gcc /bin/gcc -bash-3.2$ ls /bin/g++ /bin/g++`. – xslittlegrass Mar 19 '13 at 15:06

1 Answers1

0

The cc_r compiler is the IBM compiler. The IBM C compiler (and the C++ one) have several ways of being invoked. xlc is one, the _r variants (which mean they link to reentrant/threadsafe libraries) is another. There are also the cc and c99 ones. Why so many you ask? Well, each is provided as a shorthand for common options, in this case each is for different language standards. c99, for instance, supports the C99 standard. So just because the compiler doesn't have an 'xl' prefix doesn't mean it is not an IBM compiler.

Note that the reason you are getting the man page shown is that somewhere you are invoking the compiler without any arguments or an incorrect argument. This is the cause of the message

cc_r: 1501-210 (W) command option t contains an incorrect subargument

The -t flag allows you to swap out parts of your compiler and it's rare that you'd actually want to do that. It takes a subargument e.g.

cc_r -tI ...

Says you're going to swap out the compile-time phase of the IPA optimizer (usually specifying the new component's location with -B).

Somewhere in your makefile you are specifying -t and confusing the poor compiler mightily.

Btw, if you want to override the compiler in make, you can specify it directly in the makefile by the CC, CXX and CCC variables. You can experiment by specifying it on the command line before editing your makefile. Note that these changes would be lost if you run ./configure again.

make CC=/bin/gcc CCC=/bin/g++ CXX=/bin/g++
TheDuke
  • 750
  • 1
  • 7
  • 22