conda-forge / gdb-feedstock

A conda-smithy repository for gdb.
BSD 3-Clause "New" or "Revised" License
17 stars 62 forks source link

v9.2 #27

Closed marcelotrevisani closed 4 years ago

marcelotrevisani commented 4 years ago

Checklist

conda-forge-linter commented 4 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

conda-forge-linter commented 4 years ago

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

marcelotrevisani commented 4 years ago

@conda-forge-admin , please rerender

marcelotrevisani commented 4 years ago

the error message is not helpful @gqmelo do you have any hints here?

gqmelo commented 4 years ago

the error message is not helpful @gqmelo do you have any hints here?

So, the message is:

x86_64-conda_cos6-linux-gnu-c++: fatal error: no input files
compilation terminated.
make[4]: *** [alloc-ipa.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `$SRC_DIR/build/gdb/gdbserver'
make[3]: *** [subdir_do] Error 1
make[2]: make[3]: Leaving directory `$SRC_DIR/build/gdb'
*** [all] Error 2
make[2]: Leaving directory `$SRC_DIR/build/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `$SRC_DIR/build'
make: *** [all] Error 2

Looks like the compiler is being called without any input files at some point. Maybe some env var is not set, making a path blank?

gqmelo commented 4 years ago

But there is also this warning before the error:

x86_64-conda_cos6-linux-gnu-c++: warning: '-x c++' after last input file has no effect

Maybe this is causing the error? Is there a chance that this -x c++ is added by conda-forge compiler?

marcelotrevisani commented 4 years ago

the error message is not helpful @gqmelo do you have any hints here?

So, the message is:

x86_64-conda_cos6-linux-gnu-c++: fatal error: no input files
compilation terminated.
make[4]: *** [alloc-ipa.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `$SRC_DIR/build/gdb/gdbserver'
make[3]: *** [subdir_do] Error 1
make[2]: make[3]: Leaving directory `$SRC_DIR/build/gdb'
*** [all] Error 2
make[2]: Leaving directory `$SRC_DIR/build/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `$SRC_DIR/build'
make: *** [all] Error 2

Looks like the compiler is being called without any input files at some point. Maybe some env var is not set, making a path blank?

Don't know, I just checked on "linux from scratch" and the steps are similar, I will try to add the verbose mode to the makefile to see if it is going to be helpful

marcelotrevisani commented 4 years ago

But there is also this warning before the error:

x86_64-conda_cos6-linux-gnu-c++: warning: '-x c++' after last input file has no effect

Maybe this is causing the error? Is there a chance that this -x c++ is added by conda-forge compiler?

Probably, but I am not sure that it is causing the problem. However, we can check it

marcelotrevisani commented 4 years ago

I was searching and it seems to see somekind of race condition But I am not sure, I will try to compile it with just one core, let's see

marcelotrevisani commented 4 years ago

There is a small problem here

make[4]: Circular alloc-ipa.o <- ../alloc.c dependency dropped.

it seems as it found a circular dependency, the makefile removed it from the list of files to be compiled, and it is failing exatcly with this file. Well, that is a guess, but lets see how is it going to work when compiling with just one thread

marcelotrevisani commented 4 years ago

Just saw that, it will not work for make <=3.81, so I updated the build section

marcelotrevisani commented 4 years ago

@conda-forge-admin , please rerender

github-actions[bot] commented 4 years ago

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

Thus the PR was passing and merged! Have a great day!

phil-blain commented 4 years ago

@marcelotrevisani why did you delete run_test.sh and process_to_debug.py ?