I'm asking that because I was using Bigsur 2 days ago and no available version is currently working with Bigsur, so I downgraded my os to El capitan and I tested all options but no one is working. Today I am using Mojave 10.14.6 and still no version available.. Do you know a mac os version is working fine with valgrind please ? Thank's !
MacOS 10.13 is the last supported in the official git repo.
You should be able to get 10.14 to work with an unofficial clone (look for Louis Brunner on GitHub, there should be a brew recipe as well).
The poor state of affairs is all down to lack of resources. The Valgrind dev team has a fairly high bar to become a submitter. No-one is actively working on macOS. If people want Valgrind on macOS then we (the Valgrind dev team) need someone to step up and make a long term commitment to working on it.
Finally, there is also a significant possibility that macOS will be removed entirely from the official Valgrind repo. This was discussed as a possibility for 3.19. The subject hasn’t been raised for the next release (3.20 due out next month, October 2022).
Related
Can ios apps be compiled on the new M1 chipset?
Is there any schedule for official support?
The short answer is yes.
The latest version of XCode (version 12) is compiled as a universal app. This means that it runs on both Intel-based and Mac Sillicon machines natively. From Apple's website:
Xcode 12 is built as a Universal app that runs 100% natively on Intel-based CPUs and Apple Silicon for great performance and a snappy interface.* It also includes a unified macOS SDK that includes all the frameworks, compilers, debuggers, and other tools you need to build apps that run natively on Apple Silicon and the Intel x86_64 CPU.
This means that you should be able to compile iOS with the latest version of XCode without a problem. It would be kind of crazy for Apple to release professional hardware (MacBook Pro) without this capability.
Keep in mind that a number of third party applications may not work well on the ARM machines yet. VSCode is not currently supported on M1 devices (although Microsoft have said that it's coming). VSCode is an Electron based app which currently can't be emulated with Apple's Rosetta II platform. You might not use VSCode, but keep in mind that any Electron based apps that you use may not work straight away.
If you exclusively use XCode and don't critically rely on any third-party apps you should be ok.
EDIT: I just noticed that you tagged your post for react-native. Information is pretty slim for compatibility at the moment, so I would be cautious. If you need a Macbook Pro to do commercial work or school projects right now then you run the risk of things not working as intended. The M1 MacBooks will undoubtedly support everything that you need as a developer in the future and they're particularly great candidates for iOS development because of the parallels made possible by the shared ARM architecture.
If you're relying on a new machine to get work done right now, going with an Intel-based machine is probably the best option. For reference, I recently got an Intel-based 16" MacBook Pro with work because I need to get things done right now without any issues. The commercial value far outweighs the potential benefits that an M1 machine might bring in a year or two. If you're ok with running into some issues over the next few months, I'm sure that the M1 machines will provide plenty of value for years ahead.
While there are problems that do not allow compiling the application.
brew and cocoapods are installed in the console with rosetta enabled.
pod install / update fails because flipper and some parts of RN are not supported by the platform
if you use expo - without cli then everything is ok
updates: now cli working (after update all - homebrew, cocoapods and other to last version)
from what I know, iOS app only compiles on Mac os, so it should work with whatever macOS uses.
I have an old mac OS application developed in Mojave with the deployment target 10.12. Now how to update mac OS application to support Catalina? Or is the application automatically supports all future mac OS versions?
When developing for macOS (or any other Apple platform, for that matter), there are two key concepts to take into account when thinking about compatibility:
The SDK version: this is the SDK you're compiling against and it is usually determined by the Xcode version you're using to build your project.
The Deployment Target: this is the lowest OS version you want to support.
Normally, if you have followed the best practice in implementing your code and all of your dependencies have done the same, updating an app for a new macOS version requires only to download the latest Xcode on the latest macOS, build it and run your smoke tests (manually or through automated tests).
There may be things that have been deprecated in the meantime and Xcode will report them as warnings while building. You may read more about deprecated APIs in the macOS 10.15 release notes.
Keep in mind that you don't actually have to rebuild your app every time a new macOS version comes out. Even though it is better to test it at least once and dedicate time to explore and make use of new APIs, apps built on the previous version of macOS will, most of the times, run flawlessly on the next version (and maybe even further). This obviously depends on the app complexity, so your mileage may vary.
Every time I open GitHub for Mac it asks me to "add a new helper tool" and prompts me for my password. Every time I enter my password (I am an admin on this computer) but I see no noticeable changes afterwards and the prompt comes back every time I reopen GitHub. (See attached photo for the prompt window.)
I am running OSX Yosemite Version 10.10 on a Late 2012 Mac Mini (2.5 GHz Intel Core i5).
Unsure if this is related but I am running GitHub version "Reactive Barbecue (186)". According to the GitHub for Mac release notes this is NOT the newest version, but when I select "Check for updates" it says I have the latest version. Would a fresh install of GitHub solve this? This is more of a nuisance and doesn't noticeably impede my work.
I use GitHub daily for XCode pushes with my coworkers. They all use MacBook Airs and OSX Yosemite but do not have the same issue as me.
I was also having this problem.
Cause? Maybe GitHub.app was confused by multiple git installations: XCode's Command Line Tools and Homebrew's copy (a newer version and includes bash completion).
Running the shell command git credential-osxkeychain returned a "usage" line, so a helper was installed despite that message.
Fix: Downloading and running GitHub Desktop successfully installed its helper. I think GitHub Desktop.app is the new name for GitHub.app, so apparently they fixed the bug by now.
BTW: They wrote "If you're using GitHub for Mac or Windows, the upgrade is automatic.", but their automatic upgrade didn't fix this problem nor switch to "GitHub Desktop.app".
The only solution I found so far was to delete the GitHub for Mac application. Then I re-downloaded the app (the most recent version 193 "Big Feels").
It then gave me a popup saying I needed to uninstall the old version since OSX now comes with Git commands by default (or something like that?). Clicking "Uninstall now" made the app crash so I had to select "Uninstall later". This is sort of only a fix for the symptom since GitHub could keep telling me to uninstall every time I open it, but at least it says I have the most recent version now.
Use AppCleaner and nuke it. Reinstall.
Just installed Yosemite and when I run brew doctor I get:
Warning: Your Xcode (6.0.1) is outdated
Please update to Xcode 6.1.
Xcode can be updated from the App Store.
But in the AppStore it looks like XCode 6.0.1 is the latest version. What's the best way to correct this?
Tis that slight lag between 10.10 being Avail and xcode getting updated. If you read the top of brew doctor output it says
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!
So if everything is working, then you should do what it suggests and ignore it. The command line tools / compilers where updated for 10.10 (software update should have picked them up for you). Are you running into any issues with compiling? or just that warning.
pulling up from the comments. Your ruby and postgresql issues are from the upgrade, but it isn't really brews fault, or that compiler error warning.
with rvm just reinstall your ruby. My main dev is done with ruby-2.1.3 so
rvm reinstall ruby-2.1.3
rebuilt ruby and all my gems. The problem is that the ssl libs (maybe others) that ruby was linked to were removed / replaced in the upgrade to 10.10. The reinstall will rebuild and relink to the newer correct libs.
postgresql is slightly different. Apparently during the upgrade a couple of empty directories in /usr/local/var/postgres get removed. No idea why.
see this SO answer for how to fix that.
`pg_tblspc` missing after installation of latest version of OS X (Yosemite or El Capitan)
also if you are use pow (http://pow.cx) you will need to upgrade it to the latest version as 10.10 removed ipfw completely and only leaves pf as the firewall. so you will need to the new version which uses pf anchors.
The above steps where all I needed to do it in order to get my dev back to working.
Looks like developer.apple.com does show an XCode 6.1 as "Available Shortly" as of Fri, Oct 17, at 10pm central time. Not yet available from the AppStore. I guess I'm just too eager for an update.
First my specs are an Intel i7 toshiba laptop with 8gigs of RAM running windows 8.1 with all the latest updates. When I first launch any of Jetbrains IDEs after install, it would ask me for my workspace location and then it would proceed to do nothing after than, but it stays in memory and slows down my entire system for about a minute, after that, the computer stops being slow and returns to normal but the program still does nothing (no GUI) but still remains in memory, what is going on??? Thanks in advance.
It's hard giving a definite answer to your question. But it sounds to me like you have a problem with your Java. Make sure you have it installed and at the latest version.
Also, try looking for matching bugs in the JetBrains bug tracker.
Replacing the jre folder within the IDE folder (pycharm,intelliJ,etc.) with one from an updated JDK install not JRE install.
ex:
JDK/jre7 copy over Jetbrains/IDE/jre
fixes the issue