[Slackbuilds-users] Atlas

[Christoph Willing]

I am trying to build Atlas. On my system (S64-14.2) the procedure it
goes through to pick a compiler comes up with
/usr/bin/g++-gcc-5.5.0
rather than
/usr/bin/gcc-5.5.0
or
/usr/bin/gcc
This causes the compilation to crash and burn when it hits some code
that isn't (also) valid C++ code.
Anyone else seen this? I'm sort of curious as to whether I have
something weird going on in my system, or ... ?
A quick hack-around is to temporarily move /usr/bin/g++-gcc-5.5.0 out
of any directory in my path. But that is only one issue.

No problem with that here (64bit 14.2) - gcc is found and used.

...
make atlas_run atldir=/tmp/SBo/atlas-3.10.3/BuildDir exe=xprobe_comp redir=config
1.out \
args="-v 0 -o atlconf.txt -O 1 -A 32 -Si nof77 0 -V 976 -b 64 -
d b /tmp/SBo/atlas-3.10.3/BuildDir"
make[1]: Entering directory '/tmp/SBo/atlas-3.10.3/BuildDir'
cd /tmp/SBo/atlas-3.10.3/BuildDir ; ./xprobe_comp -v 0 -o atlconf.txt -O 1 -A 32
-Si nof77 0 -V 976 -b 64 -d b /tmp/SBo/atlas-3.10.3/BuildDir > config1.out
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
sh: -c: line 0: unexpected EOF while looking for matching ``'
sh: -c: line 1: syntax error: unexpected end of file
If anyone has read along this far and built Atlas, can they offer any
insight?

Yes I see those messages too. However compilation continues OK without
(apparent) ill effect.

One problem I did see was a linking failure right near the end of
compilation. However running 'make build' again after that failure
completed OK. I fixed this by running the SlackBuild with MAKEFLAGS=-j1

chris
_______________________________________________
SlackBuilds-users mailing list
SlackBuilds-***@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Serban Udrea]

I am trying to build Atlas. On my system (S64-14.2) the procedure it
goes through to pick a compiler comes up with
/usr/bin/g++-gcc-5.5.0
rather than
/usr/bin/gcc-5.5.0
or
/usr/bin/gcc
...

Hello,

this is an issue I know about. I'm pretty sure I proposed a patch to upstream but
never got an answer. One reason is that find is called and find doesn't guarantee
the ordering of found items. If you are brave, apply the attached patch, if not,
temporarily rename irrelevant executables containing gcc in their names to
something that doesn't contain gcc, but not as simply as g++, example:
g++-gcc-5.5.0 to g++-bbc-5.5.0.

Regarding the other issue, as much as I know it's harmless.

Best regards,
Serban Udrea

[Serban Udrea]

Post by Serban Udrea

I am trying to build Atlas.  On my system (S64-14.2) the procedure it
goes through to pick a compiler comes up with
         /usr/bin/g++-gcc-5.5.0
rather than
         /usr/bin/gcc-5.5.0
or
         /usr/bin/gcc
...

Hello,
this is an issue I know about. I'm pretty sure I proposed a patch to upstream but
never got an answer...

Hello,

It would be nice to know if this issue is solved or not.

And I have to correct myself: on Sourceforge there is an answer to my sending the
patch. Unfortunately I didn't notice it for a long time :-(

Best regards,
Serban Udrea