According to issue #9799 configuring --without-computed-gotos might
solve the AIX compile error.

I tested --without-computed-gotos on the AIX machine and that solves
the problem.


Antoine, I understood that ./configure parameters can only be changed
on the build master. Could you add --without-computed-gotos?

> Antoine, I understood that ./configure parameters can only be changed
> on the build master. Could you add --without-computed-gotos?

Done.

Thanks!

The compile errors are fixed, let's open separate issues for the
test failures.

Hi Stefan, quick question: how did you invoke ./configure on the AIX box?  The reason for asking is that a7/arsenic is a little quirky, you need to run a zsh subroutine via `_xlc 12` to set up the right CC env (see ~/buildslave/start.zsh).

Once you've done that, you need ./configure --without-gcc --with-pydebug to get the same environment as the build slave.

(I haven't set up a buildslave for gcc on that box.)

Hi Trent, nice setup BTW!

Trent Nelson <report@bugs.python.org> wrote:
> Hi Stefan, quick question: how did you invoke ./configure on the AIX box?
> The reason for asking is that a7/arsenic is a little quirky, you need to
> run a zsh subroutine via `_xlc 12` to set up the right CC env (see
> ~/buildslave/start.zsh).

That's good to know. I did the whole thing manually and pasted the ./configure
environment from

   http://buildbot.python.org/all/builders/RS6000%20AIX%207.1%20%5BSB%5D%203.x/builds/85/steps/configure/logs/stdio

to a file "build_env" in the home directory. Perhaps we can put that subroutine
in the file instead.

> (I haven't set up a buildslave for gcc on that box.)

I think that's not so important right now. It's good to have more diversity
w.r.t compilers.

For the commercial compilers it might be good to switch to optimized builds
in order to see if there are either optimizer bugs or Python bugs that don't
show up with gcc.