A little CentOS 7 help please :)

[4wd]

I hope one of our Linux gurus can give me a hand with this.

I've just installed CentOS 7 Minimal on a VPS and I'm trying to get SoftEther VPN server working on it, for which I need to download and compile it, (which I've done on 3 other CentOS 5 & 6 VPSs).

However, when I run the make command I get:

[root@wc vpnserver]# make
"grep" command not found.
Installation is aborted.
make: *** [default] Error 1

Which is a bit strange as I can use grep from the command line without a problem.

Output of $PATH and whereis:

[root@wc vpnserver]# echo $PATH
/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin
[root@wc vpnserver]# whereis grep
grep: /usr/bin/grep /usr/share/man/man1/grep.1.gz
[root@wc vpnserver]#

Any one got any ideas I can try please?

[40hz]

Odd.  Grep is usually in /bin/grep rather than /usr/bin/grep from my experience.

[4wd]

Odd.  Grep is usually in /bin/grep rather than /usr/bin/grep from my experience.

I added /bin to $PATH but it made no difference, (even though there is a /bin/grep).

Forgot to mention it's x64 but I don't think that'll make a difference.

[Ath]

Could it be that the make script messes up your $PATH setting ?
Or does it switch to another user-context for executing stuff (sudo <otheruser>) ?

[ewemoa]

Link to source code / tarball under consideration?

[40hz]

Oops. *never mind.

[4wd]

Could it be that the make script messes up your $PATH setting ?

I don't think so, $PATH is the same after running make as it was before running, of course that doesn't preclude it being changed while it's running and reverting afterwards.

The same source compiled successfully on both CentOS 5 & 6, x86 & x64, without a problem - the only difference, (other than OS), being that those VPSs weren't minimal installs.

Or does it switch to another user-context for executing stuff (sudo <otheruser>) ?

Again, I don't think so, this is a fresh install of CentOS 7 so there's only whatever users are created at that point and I only log in as root, (I really should get out of that habit).

Link to source code / tarball under consideration?

http://www.softether-download.com/files/softether/v4.12-9514-beta-2014.11.17-tree/Linux/SoftEther_VPN_Server/64bit_-_Intel_x64_or_AMD64/softether-vpnserver-v4.12-9514-beta-2014.11.17-linux-x64-64bit.tar.gz

Using these instructions: Installing SoftEther VPN 4 on CentOS 6.5 Minimal x86_64

Doing a search just now I've found someone hosting an rpm for it, I may try that, (which isn't ideal), if I can't get it to build.

[ewemoa]

A quick glance suggests that .install.sh is checking for grep -- it's just a shell script and grepping for 'grep' in the source tree doesn't turn up much so it might be worth just commenting out the checking for grep in .install.sh and trying again.


BTW, if you don't mind sharing, if you execute 'which grep' on the command line, what is the result you see?

[4wd]

BTW, if you don't mind sharing, if you execute 'which grep' on the command line, what is the result you see?

Well, it was a minimal install, I had to install which before I could 'which grep' 

Answer was the same as the 'whereis grep' in the OP: /usr/bin/grep

Which leads us to:

A quick glance suggests that .install.sh is checking for grep ...

Stupid, stupid, STUPID - I didn't think to do ls -A in the directory 

Now I can see why it failed, not so much that it couldn't find grep but that which wasn't installed ... aaarrgghhhh!

As soon as which was installed, it worked.

Thanks guys and especially you ewemoa 

[ewemoa]

Congratulations!

Odd that 'which' wasn't there already....quite "minimal" as you said.