Analyzer for Python returns error: command 'gcc' failed with exit status 1

[alex4200]

Upon trying to run the analyzer on a project, I get an error

   ....
    gcc: fatal error: cannot execute ?cc1plus?: execvp: No such file or directory
    compilation terminated.
    error: command 'gcc' failed with exit status 1

two times. Is that a known issue? I though the analyzer works only passive?

I did run the command

docker run -v ${PROJECT}:/project -v ${PWD}/output:/output ort --force-overwrite --info analyze -i /project -o /output/analyze_mime

where PROJECT points to a folder BluePyOpt, checked out with git clone https://github.com/BlueBrain/BluePyOpt.git.

Let me know any further information that are helpful to solve this problem

[sschuberth]

Is that a known issue?

It's known, yes, but so far was not documented as a public issue. Thanks for filing one.

I though the analyzer works only passive?

It tries very hard to be, yes. Unfortunately, some languages / build systems are very limited in their features to just query all required metadata without actually building anything. Python / Pip is one of these limited systems.

So in general, we have problems analyzing Python projects that depend on native-code packages. For Ruby / Bundler we were recently able to solve that problem. For Python / Pip, we are currently investigating a proper solution.

FYI, @pombredanne, this is also something that should get solved by the "Project-Multi Python-version dependencies resolver".

[alex4200]

Is there any workaround I can apply?

[sschuberth]

The only work-around I can think of is to install gcc (and any subsequently missing development library) on the system running ORT.

[alex4200]

Thanks, the workaround (installing gcc) did actually work for me.
I had to install the following packages for the docker image to get things work:

gcc g++ python3-dev python3-pip libxml2-dev libxslt1-dev zlib1g-dev

[pombredanne]

FYI, @pombredanne, this is also something that should get solved by the "Project-Multi Python-version dependencies resolver".

This is a league of its own, complexity-wise IMHO. This would best done in a second step

[pombredanne]

But in the specific case at hand here, a resolver would work assuming we get this fixed aboutcode-org/scancode-toolkit#2742 to feed it the direct, immediate dependencies parsed and collected from https://github.com/BlueBrain/BluePyOpt/blob/6d4185479bc6dddb3daad84fa27e0b8457d69652/setup.py#L35

[sschuberth]

I'll close this in favor of the more general #4637 as the immediate question has been answered and there is a work-around.

[sschuberth]

Reopening as #4637 now actually is a epic that refers to this issue.

[mnonnenmacher]

I assume the gcc error happens during pip install, so this could be closed as we don't run pip install anymore.

[sschuberth]

I assume the gcc error happens during pip install, so this could be closed as we don't run pip install anymore.

@alex4200 could you verify this please with the latest ORT version?

[heliocastro]

This happens when a package is not available on specific abi on machine, so it calls wheel module to compile the native "binding".
Even not been used anymore with python-inspector, this could become an issue if we do need specific arch install.
So, in the end we need set a basic devel environment on the executor. Today's docker we don't have gcc enabled on the runner image

[sschuberth]

checked out with git clone https://github.com/BlueBrain/BluePyOpt.git.

I've verified that this works now with the latest ORT that uses python-inspector.