config.guess file produces different canonical system

[moralesjohnny]

Hi,

I am trying to run a code using parallel processing and I get this message:

The canonical system as returned by config.guess (x86_64-unknown-linux-gnu) is 
not the same as the one found in the config file (linux64).

I went to the linux64.conf file in /EGSnrc/HEN_HOUSE/specs/ folder and it clearly says canonical_system=linux64.

So why does the /EGSnrc/HEN_HOUSE/scripts/config.guess file return x86_64-unknown-linux-gnu?

I would appreciate it very much if any one out there might know why this is happening in my installation?

I checked the following (I am logged in as egsuser): $EGS_CONFIG=./home/egsuser/EGSnrc/HEN_HOUSE/specs/linux64.conf

Any help will be appreciated.

[rtownson]

This could happen if you ran the configuration script (installer) on a different computer than your are trying to run your codes on. If you use multiple machine architectures, you need to run the HEN_HOUSE/scripts/configure script (or the installer) for each machine type, creating a different "configuration", which is pointed to by $EGS_CONFIG. Then, when you run jobs on a given machine you need to set $EGS_CONFIG to point to the correct file.

If you run the configure script and then still get this message on the same machine, let me know and I will re-open the issue.

[rtownson]

After looking again I believe this is a bug that occurs when you install with the GUI. The default canonical system is generated differently than in config.guess so they don't match.

[mainegra]

@moralesjohnny and @rtownson this is only a warning issued by the job submission script run_user_code_batch. Jobs must still be running though. The script config.guess is used to determine the computer triplets ‘cpu-vendor-os’ to create an identifier string for your system. In this way a user could be notified that there could be an issue if running on a different system. In the past, the configuration GUI would suggest to users the canonical name as the configuration name. Since these strings were getting very long, I inverted the process in the GUI and started using the config name as the canonical system. A fix would be to enable the use of config.guess in the GUI again to determine the canonical name on Linux.

[rtownson]

From a follow up post on google+ it sounds like the jobs don't run:

"I am running simulations on a unique computer with 8 processors. I have run the configure script, but when I try to run a code with exb still appears the advice

canonical system returned by config.guess (x86_64_unknown-linux-gnu) is not the same as the one found in the config file (linux64)

and the run stops"

[merbsandspices]

Hi @moralesjohnny,

How did you resolve this issue? I am currently experiencing same.

[thanhtaiphys]

Hello everyone,

I installed the egs_mird and it failed to run after installing DOSXYZnrc.

"The canonical system as returned by config.guess (x86_64-unknown-linux-gnu) is not the same as the one found in the config file (linux64). I hope you know what you are doing. No egs_mird executable on your area or on HEN_HOUSE"

[rtownson]

@thanhtaiphys do you get this error during installation, or while running run_user_code_batch? For the latter, try using egs-parallel instead for job submissions. If it's an installation warning, post the rest of your installation log from HEN_HOUSE/log. Does the installation otherwise go successfully? Maybe you can ignore the warning. How do you go about installing egs_mird - do you install EGSnrc first and then copy/paste it into egs_home, or are you installing a special EGSnrc disto that includes it?