I recently updated my Mac to MacOS Ventura Beta, causing terminal commands like gcc, pyhton3 and pip3 to not work. Until last week I was able to use them normally, but after the update terminal asks me to download XCode Commandline Developer Tools.
The problem that came with this, is that VSCode is unable to find include files for C/C++.
I tried reinstalling VSCode, VSCode extensions related to C/C++, and even changing the #include_path for C files in VSCode, but nothing seems to work.
Any help would be very much appreciated :).
I wanted to put my solution here.
The new macOS Ventura is officially released now. I encountered the same issue you described. The solution was pretty simple, just to install XCode.
Run this command in Terminal.app:
xcode-select --install
Let it install the XCode.
Restart your VSCode.
You should be working correctly now.
One of our engineers facing an error with PhpStorm. Whenever he edits anything in PhpStorm, it gives the error related to PHP_Codesniffer:
phpcs: env: php: No such file or directory...
If open PHPCodeSniffer Inspection Settings, the below attached settings can be seen.
One more point, it was working fine until he upgrades his MacOS from Big Sur to Monterey 12.0.1. Not sure this OS upgrade affect the application settings. Presently he cannot work with PhpStorm.
Could you please have a look and let me know?
One more point, it was working fine until he upgrades his MacOS from Big Sur to Monterey 12.0.1. Not sure this OS upgrade affect the application settings. Presently he cannot work with PhpStorm.
I had the same issue. Monterey removes the installed PHP version, as Mac OS no longer ships with php installed.
Install php and it should work again.
In my case, using homebrew
brew install php#7.4
brew link php#7.4
After I had to reinstall my Windows 10 I faced the problem of Cypress installation which I can't resolve. Before this moment it worked fine. But since the OS has been reinstalled I am not able to install Cypress in local folder any more. Whatever folder I try to use, Cypress is installed globally to c:\users\admin... folder. I tried to reinstall nodejs, clear npm cache, but nothing helped. Other packages can be installed properly, but not the Cypress. Did anybody face this problem and how it can be fixed?
After installing 2019.3 on Windows as an upgrade from 2019.2, I am greeted with this message:
I reinstalled PyCharm from scratch, and am still hitting the same error. Any idea what could have gone wrong and how to fix it?
(As a work-around, uninstalling 2019.3 and reinstalling 2019.2.5 works.)
The problem is caused by the disabled YAML plugin. See the relevant ticket in the PyCharm's bug tracker https://youtrack.jetbrains.com/issue/PY-38866. Basically you need to re-enable the plugin.
Remove org.jetbrains.plugins.yaml from
macOS: ~/Library/Preferences/PyCharm2019.3/disabled_plugins.txt
Ubuntu: ~/.PyCharm2019.3/config/disabled_plugins.txt
Windows: C:\Users\<USER>\.PyCharm2019.3\config\disabled_plugins.txt
I have been running MAMP Pro 3.05 successfully in Yosemite up to DP4 on a partition that was a clean install of Yosemite.
I now have run the installer for DP5 over my Mavericks install, and now that MAMP Pro install will not start Apache. It says to check the logs, but I don't see anything pertinent.
I'm assuming that since this is a pre-existing install, something in its config is wrong for Yosemite's Apache.
Any ideas?
MAMP Folks just posted the workaround
Workaround for the 10.10 Preview 5 bug: Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars”
Test Update: It works!
Works for Yosemite release too!
Just found workaround from MAMP on Twitter
Workaround for the 10.10 Preview 5 bug:
Rename the file “envvars” located in into “_envvars”
This works also for Mamp Pro 2.1.1 on Yosemite.
MAMP Folks just posted the workaround
Workaround for the 10.10 Preview 5 bug: Rename the file “envvars”
located in /Applications/MAMP/Library/bin into “_envvars”
Test Update: It works!
Apparently the MAMP folks are working on a work-around:
https://twitter.com/mamp_en/status/496655943506350081
Follow their account for updates.
MAMP Pro 3.0.7.3 should run fine on Yosemite, but after installing it on a brand new machine, I experienced the same problem.
In my case, the problem occurred because I had defined Additional Parameters for my virtual host that contained quotes. By default, Yosemite keyboard settings are set to convert straight quotes to smart quotes ("no-cache" became “no-cache”. Depending on font and font size, this may not be immediately obvious). This made Apache crash, even when the host was disabled.
To change this settings, go to System Preferences -> Keyboard. In the Text tab, uncheck Use smarts quotes and dashes.
Today, I upgraded to MAMP Pro 3.0.7.3 after I upgraded to OSX Yosemite 10.10 (official release) and I experienced this same problem. Apache could not start and it has an empty log file.
I tried this fix, but I noticed that the file is named "envvars_" not "envvars". I renamed it to envvars, restarted MAMP Pro and apache could not start and it had an empty log file. I also noticed that the envvars file had been renamed to envvars_ after I had renamed it.
I was running MAMP 3.0.5 on Mavericks. After upgrading Mavericks to El Capitan, I ran into the same issue. Mysql did start normally but Apache did not.
After renaming envvars to _envvars in the folder /Applications/MAMP/Library/bin such as suggested for Yosemite, I was able to start Apache as before.
So, this fix works for El Capitan as well!
I didn't get it working by changing envvar to _envvar but was able to resolve by changing the apache port from 8888 to 80 then noticed I was missing the mod_example.so. See how I resolved below:
Why won't Apache Server start in MAMP?
I tried that solution and others over and over and did not work until I realised I should be restarting completely MAMP, after doing so, this simple change from envvars to _envvars worked like a charm.
You can completely restart MAMP checking if there's any process going on, open the terminal:
ps -cvx | grep "mysql"
That will output a list of the processes that involves mysql at the time, with a PDI associated, so you only have to take that number and:
kill PDI
Where PDI is the number associated to the process, after that, if you write again the command ps -cvx | grep "mysql" the pointer should be empty.
Once done, only execute MAMP.
The approved answer didn't work for me because the _envvars file was already there. I had to download the latest version of MAMP and install it and it worked.
Sometimes, it's not always the envars files that's the culprit. If you've been editing the vhost file at /Applications/MAMP/conf/apache/extra/httpd-vhosts.conf, a syntax error could cause MAMP's apache to not start without a warning.
In that case, you can run the following command and see if any errors are encountered.
sudo apachectl stop
Try this::
Rename the file “envvars” located in /Applications/MAMP/Library/bin into “_envvars” only for OS X Yosemite.
I got MAMP v3.4 working.
I renamed "envars_" to "_envars" ... but that didn't work.
I had to also go into preferences, and hit the "Set Web & MySql ports to 80 & 3306" button!
Works!