-
-
Notifications
You must be signed in to change notification settings - Fork 487
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hg_sage.commit() Error on OS X 10.5.5. Conflict in libPng.dylib? #4678
Comments
comment:1
Can you supply some more info, i.e. how did you build Sage, i.e. is this a FrameWork build for example. What is EDITOR set to in your environment. In general do not open tickets unless it is clear what the bug is. This case is clearly such a case since we will need some discussion what is wrong and trac is the wrong place to do that. For that you should use sage-support instead. Cheers, Michael |
comment:2
This is just a regular build of Sage on OS X 10.5.5 (using make) after moving /opt out of the way. EDITOR is set to:
which calls TextMate, but it is crashing before then. If I use a Macports build of mercurial, I can run hg commit just fine (which is what I did after this crashed). I'll keep your statements about tickets in mind for the future. Sorry. |
comment:3
Yep, mate crahes since when mercurial executes EDITOR for some stupid reason when applying patches it picks up the libpng.dylib provided by Sage. There are two solutions here:
This should be discussed on sage-devel if we want to patch hg to use sage-native-execute for its EDITOR command, but this ticket is closed as wontfix. Cheers, Michael |
comment:4
Sorry I forgot: In case we decide to patch hg this would be a new ticket. Cheers, Michael |
When trying hg_sage.commit() on OS X 10.5.5. I get the following error
So, for some reason, there is a conflict with the system frameworks. Unfortunately, this can't be commented out like Macports or Fink.
Component: misc
Keywords: hg, libpng
Issue created by migration from https://trac.sagemath.org/ticket/4678
The text was updated successfully, but these errors were encountered: