For the record, the OSX binaries are broken because cliquer fails to install; the log contains:
error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: changing install names or rpaths can't be redone for: /Users/vbraun/Code/binary-pkg/source/SageMath/jc4b6yulaujayb9sr94ia88eourzeqip0oidmas391yaj24ng0bmdu/local/lib/libcliquer.dylib (for architecture x86_64) because larger updated load commands do not fit (the program must be relinked, and you may need to use -headerpad or -headerpad_max_install_names) Of course errors are not caught in cliquer's spkg-install so the compilation continues from there. The binary then doesn't work, of course. On Tuesday, January 26, 2016 at 1:36:45 PM UTC-5, Nathann Cohen wrote: > > > Nathann: > > William, > > I'm sorry to say that the situation is not as simple as "You suggest, > and you are happy to see people doing it for you". > > Sometimes, people do stuff because nobody would do it otherwise. They > feel responsible as members of the community, and so give it a try. I > swear: trust me. And by merely "suggesting stuff and waiting for > others to (happily) do it" the truth is that you sometimes *use* those > people. > > Once, on a trac ticket, I saw something like that: "Of course this > implementation is unnecessarily slow, but someday somebody will see it > and improve it". For somebody like me, it comes very close to forcing > me to improve it: because I do not accept to see a very obviously slow > algorithm in Sage when I see a clear way to improve it: we deserve > better (*). > > I can only pray that not too many people will grow this "much bigger > picture longterm strategic view of things" that you mentionned. > Because each time it happens (you cite Nicolas Thierry as an example) > we lose a developer and those they take with them. > > And there is work to be done. Work which will only be done by those > who remain. Some key people who, like you, are hardly repleacable: how > many persons do you think have what it takes to change Sage's build > system? > > I'd say three: Volker, Jeroen and you. Perhaps there are others: I > don't even know enough to give the full list. > > But you cannot expect this to be done by one person, it takes a *lot* > of time and skill, and we are not enough. > > So please, now that you have seen the "much bigger picture longterm > strategic view of things", come down here and get your hands dirty. We > can't do the job if those who know how to do it think that they are > above it. > > Nathann > > (*) On this ticket, they *knew* what was wrong. They just did not care > enough to spend the time. > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-support+unsubscr...@googlegroups.com. To post to this group, send email to sage-support@googlegroups.com. Visit this group at https://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
