[psycopg] Build issue with Advance Toolchain - Mailing list psycopg

Hi,

I'm trying to compile psycpg2 on Power. For full optimization, I use Advance
Toolchain (AT), which is an extended version of GCC for Power.


The problem is: Parts of the code honors CC variable, part of does not.

Here is what I'm getting (see the difference between lines 1&2 and 3)

/opt/at10.0/bin/gcc -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong--param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mcpu=power7 -mtune=power8 -D_GNU_SOURCE
-fPIC-fwrapv -O3 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4-grecord-gcc-switches -m64 -mcpu=power7 -mtune=power8 -D_GNU_SOURCE -fPIC -fwrapv -O3 -fPIC
-DPSYCOPG_DEFAULT_PYDATETIME=1-DPSYCOPG_VERSION="2.7.1 (dt dec pq3 ext lo64)" -DPG_VERSION_NUM=90603 -DHAVE_LO64=1
-I/usr/include/python2.7-I. -I/usr/pgsql-9.6/include -I/usr/pgsql-9.6/include/server -c psycopg/microprotocols_proto.c
-obuild/temp.linux-ppc64le-2.7/psycopg/microprotocols_proto.o -Wdeclaration-after-statement 
/opt/at10.0/bin/gcc -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions
-fstack-protector-strong--param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mcpu=power7 -mtune=power8 -D_GNU_SOURCE
-fPIC-fwrapv -O3 -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong
--param=ssp-buffer-size=4-grecord-gcc-switches -m64 -mcpu=power7 -mtune=power8 -D_GNU_SOURCE -fPIC -fwrapv -O3 -fPIC
-DPSYCOPG_DEFAULT_PYDATETIME=1-DPSYCOPG_VERSION="2.7.1 (dt dec pq3 ext lo64)" -DPG_VERSION_NUM=90603 -DHAVE_LO64=1
-I/usr/include/python2.7-I. -I/usr/pgsql-9.6/include -I/usr/pgsql-9.6/include/server -c psycopg/typecast.c -o
build/temp.linux-ppc64le-2.7/psycopg/typecast.o-Wdeclaration-after-statement 
gcc -pthread -shared -Wl,-z,relro build/temp.linux-ppc64le-2.7/psycopg/psycopgmodule.o
build/temp.linux-ppc64le-2.7/psycopg/green.obuild/temp.linux-ppc64le-2.7/psycopg/pqpath.o
build/temp.linux-ppc64le-2.7/psycopg/utils.obuild/temp.linux-ppc64le-2.7/psycopg/bytes_format.o
build/temp.linux-ppc64le-2.7/psycopg/libpq_support.obuild/temp.linux-ppc64le-2.7/psycopg/win32_support.o
build/temp.linux-ppc64le-2.7/psycopg/connection_int.obuild/temp.linux-ppc64le-2.7/psycopg/connection_type.o
build/temp.linux-ppc64le-2.7/psycopg/cursor_int.obuild/temp.linux-ppc64le-2.7/psycopg/cursor_type.o
build/temp.linux-ppc64le-2.7/psycopg/replication_connection_type.o
build/temp.linux-ppc64le-2.7/psycopg/replication_cursor_type.o
build/temp.linux-ppc64le-2.7/psycopg/replication_message_type.obuild/temp.linux-ppc64le-2.7/psycopg/diagnostics_type.o
build/temp.linux-ppc64le-2.7/psycopg/error_type.obuild/temp.linux-ppc64le-2.7/psycopg/lobject_int.o
build/temp.linux-ppc64le-2.7/psycopg/lobject_type.obuild/temp.linux-ppc64le-2.7/psycopg/notify_type.o
build/temp.linux-ppc64le-2.7/psycopg/xid_type.obuild/temp.linux-ppc64le-2.7/psycopg/adapter_asis.o
build/temp.linux-ppc64le-2.7/psycopg/adapter_binary.obuild/temp.linux-ppc64le-2.7/psycopg/adapter_datetime.o
build/temp.linux-ppc64le-2.7/psycopg/adapter_list.obuild/temp.linux-ppc64le-2.7/psycopg/adapter_pboolean.o
build/temp.linux-ppc64le-2.7/psycopg/adapter_pdecimal.obuild/temp.linux-ppc64le-2.7/psycopg/adapter_pint.o
build/temp.linux-ppc64le-2.7/psycopg/adapter_pfloat.obuild/temp.linux-ppc64le-2.7/psycopg/adapter_qstring.o
build/temp.linux-ppc64le-2.7/psycopg/microprotocols.obuild/temp.linux-ppc64le-2.7/psycopg/microprotocols_proto.o
build/temp.linux-ppc64le-2.7/psycopg/typecast.o-L. -L/usr/pgsql-9.6/lib -lpython2.7 -lpq -o
build/lib.linux-ppc64le-2.7/psycopg2/_psycopg.so
unable to execute gcc: No such file or directory
error: command 'gcc' failed with exit status 1

Can you please let me know how I can fix this?

Thanks!

Regards,
--
Devrim Gündüz
EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR