osx-elcapitan

Error in mcrypt after upgrading into El Capitan OS

痞子三分冷 提交于 2019-12-02 06:32:56
I just upgraded my OS into El Capitan. I had to do some changes in my apache configurations to make everything works as it did before. Thanks for - http://coolestguidesontheplanet.com/get-apache-mysql-php-and-phpmyadmin-working-on-osx-10-11-el-capitan/ One thing that is not working for me is the Mcrypt extension. Anyone knows how to update it to make it work? Can be a problem related to the new System Integrity Protection or "SIP"? Maybe could be helpful to check permission on the /usr folder and change them as needed. After upgrading to El Capitan, mcrypt.so has been moved from /usr/lib/php

laravel composer install could not solve installable package for tymon/jwt-auth

不羁的心 提交于 2019-12-02 04:20:26
问题 I am trying to run composer install for a laravel project. The error is as below: Loading composer repositories with package information Installing dependencies (including require-dev) from lock file Warning: The lock file is not up to date with the latest changes in composer.json. You may be getting outdated dependencies. Run update to update them. Your requirements could not be resolved to an installable set of packages. Problem 1 - Installation request for namshi/jose 5.0.2 -> satisfiable

Xcode not showing product scheme after updating to EL Capitan?

有些话、适合烂在心里 提交于 2019-12-02 01:29:38
I’m using xcode 6.4. it was working fine but after updating to EL Capitan. Now the product scheme is not showing. image attached. I'm not able to select any device or simulator Confirm that you are not using any variant of xcode 6 . I also got the same issue with xcode 6.4 , but when I used xcode 7 , everything was working fine. So get xcode 7 . It will work Here is a snippet of bug with OS X El Capitan Developer Beta 7 Release Notes Refer this link for more. Vakas Just stretch the Xcode window in horizontal direction and make it bigger than your screen size, it will bring that back. I had the

Firefox isn't showing typescript (.ts) source maps in the debugger

好久不见. 提交于 2019-12-02 01:22:48
问题 I can only see the .js files, the .ts sources don't appear in Firefox. It works in Chrome, I can see and place line breaks in .ts files, and the debugger works great. But Firefox will not work, no version, not the stable or the nightly or the developer version. Could it be that the functionality is not implemented on Mac/OSX? If so, there should be something on the internet about that, but I've found nothing. Apparently, the problem has not been documented anywhere. Does anyone have any

Firefox isn't showing typescript (.ts) source maps in the debugger

廉价感情. 提交于 2019-12-01 21:50:30
I can only see the .js files, the .ts sources don't appear in Firefox. It works in Chrome, I can see and place line breaks in .ts files, and the debugger works great. But Firefox will not work, no version, not the stable or the nightly or the developer version. Could it be that the functionality is not implemented on Mac/OSX? If so, there should be something on the internet about that, but I've found nothing. Apparently, the problem has not been documented anywhere. Does anyone have any knowledge of this, and perhaps how to fix it? A little late but hopefully helpful. For Firefox make sure

rpy2 error after upgrading to OSX El Capitan

末鹿安然 提交于 2019-12-01 16:28:07
问题 I have an error occurring in a very similar way to this SO question. The solution of simply installing rpy2 using conda doesn't work. The key difference in my case is that rpy2 worked properly before I updated to Mac OSX 10.11 (El Capitan). My Python version is Python 2.7.10 , conda: 3.18.4 , R: R version 3.2.2 (2015-08-14) -- "Fire Safety and all were installed using the anaconda distribution. I get the following error: ImportError: dlopen(/Users/user/anaconda/lib/python2.7/site-packages

Why is node-gyp rebuild failing on Mac OSX El Capitan

烈酒焚心 提交于 2019-12-01 15:05:08
I recently bought a mac, which uses Mac OSX El Capitan v10.11.4. Installed node with homebrew, and am using node v6.2.2 and npm v3.9.5. I'm getting an error with bcrypt during npm install , which I believe derives from a node-gyp rebuild error. I also recently downloaded xcode-select(version 2343) and xcode(7.3.1) (in that order). Here is the full error output after i run npm install : https://gist.github.com/varunjayaraman/5734af617d616437cd5b3456b20bc503 Not sure what's going wrong. I come from linux land and do tend to be wary of not installing from source myself, so maybe that is the cause

Why is node-gyp rebuild failing on Mac OSX El Capitan

巧了我就是萌 提交于 2019-12-01 13:54:55
问题 I recently bought a mac, which uses Mac OSX El Capitan v10.11.4. Installed node with homebrew, and am using node v6.2.2 and npm v3.9.5. I'm getting an error with bcrypt during npm install , which I believe derives from a node-gyp rebuild error. I also recently downloaded xcode-select(version 2343) and xcode(7.3.1) (in that order). Here is the full error output after i run npm install : https://gist.github.com/varunjayaraman/5734af617d616437cd5b3456b20bc503 Not sure what's going wrong. I come

Rendering Glitch on Mac OSX El Capitan with OpenGL

不打扰是莪最后的温柔 提交于 2019-12-01 06:42:12
问题 I created a tennis game for OSX using SDL 1.2 + OpenGL 1.1 . Everything was ok till El Capitan. Now, a few textures aren't displayed correctly. The court white lines are now black ; the player textures are all bad ; the energy bars on the left are all black: The white lines on the icons aren't normal. The rainbow texture on the highlighted icon isn't either: How the game should normally looks: So the wrong textures are: the players : they are re-created in-game using different textures, using

Title bar missing in NSOpenPanel?

我们两清 提交于 2019-12-01 05:55:55
Since OS X 10.11 it seems the title bar no longer appears even when using setTitle: does anyone know what happened and how to get the old behavior back? mangerlahn From the AppKit Release Notes for OS X v10.11 : In 10.11, most NSOpenPanels have adopted a design that was formerly reserved only for applications which adopted iCloud Documents support and this panel design was only used if iCloud Drive was turned on in System Preferences. This note will refer to the design as the “iCloud Open Panel Design” although the design is no longer limited to applications with iCloud Documents support. The