Issue when compiling with "make all"

[Davide Sangalli]

The three dots are purely cosmetics, it's just a search and replace in the log files. They have nothing to do with the compilation itself.

Just a comment on this.
In the configure there are some operations triggered by a check if the "srcdir" and the "compdir", i.e. the folder from which the configure is executed in the form "srcdir/configure" are different.

[remi.lacroix]

Just a comment on this.
In the configure there are some operations triggered by a check if the "srcdir" and the "compdir", i.e. the folder from which the configure is executed in the form "srcdir/configure" are different.

I am sorry this is causing so much confusions. For security reasons, I have manually modified a copy of the logs before sending them but it really cannot have affected the compilation itself.

I hope this clear things up.

[andrea marini]

Hi. I just entered now the discussion. I hope I did not miss anything important.

I read the posts and could not really understand where the problem is.

Can you, please, just do the following steps?

1. the config.log obtained at configuration (you can change the configuration command with all options you generally use)

   Code: Select all

   > ./configure >& config.log

2. the report and setup files after configuration in the config folder
3. after the configuration for each of the following values of ACTION: download-all, int-libs, ext-libs, yambo-int-libs, yambo-ext-libs just do

   Code: Select all

   > make ACTION >& ACTION.log

4. if none of the actions above fail just try compiling and linking the code
5. after the configuration for each of the following values of OBJECT: yambo ypp a2y c2y p2y yambo_ph ypp_ph yambo_sc ypp_sc yambo_rt ypp_rt yambo_nl ypp_nl just do

   Code: Select all

   > make OBJECT >& OBJECT.log

You can prepare a simple shell script to do everything.

Thx

Andrea

[remi.lacroix]

Hi,

if none of the actions above fail just try compiling and linking the code

The whole question here is "with which make targets?" because depending what I choose compiling will fail as I tried to explain in my last message.

I'm attaching the "report" from configure for the attempts in that message.

Rémi

[andrea marini]

Hi,

The whole question here is "with which make targets?" because depending what I choose compiling will fail as I tried to explain in my last message.

I am sorry but I cannot understand what do you mean.

Can you be more precise? Are you saying that the full procedure depends on the make you are using?

This is mine. What's yours?

Code: Select all

>make -v
GNU Make 4.2.1
Built for x86_64-pc-linux-gnu
Copyright (C) 1988-2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

[remi.lacroix]

I am sorry but I cannot understand what do you mean.

Can you be more precise? Are you saying that the full procedure depends on the make you are using?

What I am trying to say is compilation might or might not be successful depending on which targets I am compiling (i.e. which "make <targets>" command I run).

For example "make ypp" will fail but "make core" won't (although it includes "ypp"), "make core ypp_ph" will fail but "make ypp_ph" won't.

It all comes down to dependency issues in the Makefile I guess.

[andrea marini]

Hi,

can you please do what I have asked you to do? Without all the logs I have asked you to provide it is almost impossible to understand what's going on.

In addition please add to the configure the option

Code: Select all

--enable-msgs-comps

Thx

Andrea

Can you, please, just do the following steps?

1. the config.log obtained at configuration (you can change the configuration command with all options you generally use)

   Code: Select all

   > ./configure >& config.log

2. the report and setup files after configuration in the config folder
3. after the configuration for each of the following values of ACTION: download-all, int-libs, ext-libs, yambo-int-libs, yambo-ext-libs just do

   Code: Select all

   > make ACTION >& ACTION.log

4. if none of the actions above fail just try compiling and linking the code
5. after the configuration for each of the following values of OBJECT: yambo ypp a2y c2y p2y yambo_ph ypp_ph yambo_sc ypp_sc yambo_rt ypp_rt yambo_nl ypp_nl just do

   Code: Select all

   > make OBJECT >& OBJECT.log

You can prepare a simple shell script to do everything.

Thx

Andrea

[remi.lacroix]

can you please do what I have asked you to do? Without all the logs I have asked you to provide it is almost impossible to understand what's going on.

Sure, it's just that I have already provided some logs earlier and I'm still not sure what you want me to run at step 4, "make all"?

I will start running steps 1 to 3 in the meantime.

[andrea marini]

can you please do what I have asked you to do? Without all the logs I have asked you to provide it is almost impossible to understand what's going on.

Sure, it's just that I have already provided some logs earlier and I'm still not sure what you want me to run at step 4, "make all"?

I will start running steps 1 to 3 in the meantime.

Hi. Forget point 4 and move to step 5.

Andrea

[remi.lacroix]

Hi. Forget point 4 and move to step 5.

Ok, here are all the requested files (note that some paths were partially redacted for security reasons).

Compilation worked for yambo, ypp, a2y, c2y, p2y" (in that order, I know for a fact that if I compile ypp first it will fail) and failed for yambo_ph, ypp_ph, yambo_sc, ypp_sc, yambo_rt, ypp_r,t yambo_nl and ypp_nl.

I haven't check all logs but in many cases the issue is the same as the one I described before, "el-ph" fails to compil because a module cannot be found.

Thanks,
Rémi