1

I'have some problem with build-essentials on Debian Stretch. Since an npm command fail, and the symptom is build-essentials not installed, I reinstalled it from scratch. When checking version, all seems ok except make:

make -v

reports /usr/bin/make syntax error near unexpected token....

What can be wrong? it seems to run make as if it was a shell script ( just my guess ) how this can be?

UPDATE By reinstalling just make, it worked:

apt-get install make --reinstall

sooo reliable system...

enter image description here

closed as off-topic by Jeff Schaller, Kusalananda, G-Man, LinuxSecurityFreak, Rui F Ribeiro May 20 '18 at 9:01

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions describing a problem that can't be reproduced and seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jeff Schaller, Kusalananda, G-Man, LinuxSecurityFreak, Rui F Ribeiro
If this question can be reworded to fit the rules in the help center, please edit the question.

  • Not reproducible... so not a valid question. – Felice Pollano May 21 '18 at 8:04
1

Looks like your /usr/bin/make was at least partially overwritten with something else. This might mean you have some filesystem corruption. Which filesystem type(s) are you using?

You might want to run a full filesystem check to see if you have more filesystem corruption than just one overwritten /usr/bin/make. If you are using XFS, you should be aware that the generic fsck or fsck.xfs commands do nothing at all for XFS filesystems, as this filesystem type is supposed to do all "routine" checks internally. To just check for errors on a XFS filesystem, you should use xfs_repair -n. As always, filesystem checks should be run with the filesystem in question unmounted, or mounted as read-only if it's your root filesystem.

Not the answer you're looking for? Browse other questions tagged or ask your own question.