Ubuntu
gcc-5 package

  1. Bug #1783252
  2. Comment #9

Comment 9 for bug 1783252

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2018-08-01 12:04 EDT-------
sure, but how do I control that? I just run `pip install greenlet` to reproduce this. I'm not specifying a gcc version.

From the error, it is using powerpc64le-linux-gnu-gcc, so I located that and tracked it back to the gcc package:

myuser@myhost:~$ which powerpc64le-linux-gnu-gcc
/usr/bin/powerpc64le-linux-gnu-gcc
myuser@myhost:~$ dpkg -S /usr/bin/powerpc64le-linux-gnu-gcc
gcc: /usr/bin/powerpc64le-linux-gnu-gcc

And confirmed that I already have the latest version of that installed, with no other candidates that might cause it to use a newer version of gcc:

myuser@myhost:~$ sudo apt-cache policy gcc
gcc:
Installed: 4:5.3.1-1ubuntu1
Candidate: 4:5.3.1-1ubuntu1
Version table:
*** 4:5.3.1-1ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports xenial/main ppc64el Packages
100 /var/lib/dpkg/status

------- Comment From <email address hidden> 2018-08-01 12:09 EDT-------
You have to figure out the build process and whether you can override the selection of the compiler. Often this is done with a CC macro. There's no magic bullet that I can give you, I don't have package build expertise or any knowledge of greenlet.