Hi Sam,
> On Aug 5, 2021, at 9:42 AM, Sam Ruby <ru...@intertwingly.net> wrote:
>
> Perhaps at some point we should have a zoom call and you can share
> your screen and we can explore it together. Ping me on slack if this
> interests you.
That sounds like a great idea. I've sent you a DM on Slack.
>
> Meanwhile, did setupmymac complete successfully?
No. It runs for an hour and then fails.
>
> Can you try the following command from the
> /srv/whimsy/www/secretary/workbench directory?
>
> $ bundle update
No luck there either.
>
> If that doesn't work, you won't have the gems installed you need to
> run the workbench.
Seems to be a theme:
vi
/private/var/whimsy/whimsy/www/secretary/workbench/vendor/bundle/ruby/2.6.0/extensions/universal-darwin-19/2.6.0/ffi-1.15.3/mkmf.log
"pkg-config --exists libffi"
| pkg-config --libs libffi
=> "-L/opt/local/lib -lffi \n"
"xcrun clang -o conftest
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/universal-darwin19
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/backward
-I/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0
-I. -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT
-g -Os -pipe -DHAVE_GCC_ATOMIC_BUILTINS conftest.c -L.
-L/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib -L.
-L/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.Internal.sdk/usr/local/lib
-arch x86_64 -lruby.2.6 "
In file included from conftest.c:1:
In file included from
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby.h:33:
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
fatal error: 'ruby/config.h' file not found
#include "ruby/config.h"
^~~~~~~~~~~~~~~
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/include/ruby-2.6.0/ruby/ruby.h:24:10:
note: did not find header 'config.h' in framework 'ruby' (loaded from
'/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk/System/Library/Frameworks')
1 error generated.
checked program was:
/* begin */
1: #include "ruby.h"
2:
3: int main(int argc, char **argv)
4: {
5: return 0;
6: }
/* end */
>
> ---
>
> Some background on the "auto update issue".
>
> Bundle update will update you to nokogiri 1.12.2 (which was recently
> updated to include nokogumbo) and no separate nokogumbo.
> Unfortunately, wunderbar version 1.4.5 still looks for nokogumbo and
> will fail if it isn't present. Solutions are to either pin nokogiri
> to 1.11 (NOT RECOMMENDED) or to update wunderbar to 1.5.0
> (RECOMMENDED).
>
> This is the danger of doing bundle update to get the latest of most
> things, but selectively pinning other things. Eventually, you will
> get out of sync.
>
> There are two sane approaches to this problem: (1) have the server run
> bundle update, try to stay up to date, report and regressions promptly
> and see to it that the regressions are added to the test suite, or (2)
> have the server run bundle install, check in Gemfile.lock and don't
> allow any updates (including security updates!) until a whimsy
> developer runs bundle update on their machine and checks in the
> updated Gemfile.lock file.
>
> I prefer the first option as getting a bug report that "version n
> released yesterday introduced a regression" is much easier to debug
> than "some version released in the past n months introduced a
> regression". But honestly, either approach is preferable to the
> broken approach that whimsy had been using since late last year.
>
> - Sam Ruby
>
> On Wed, Aug 4, 2021 at 11:14 PM Craig Russell <apache....@gmail.com
> <mailto:apache....@gmail.com>> wrote:
>>
>> Still looking for some help here. The error reported from the completion of
>> setupmymac points to ruby2js strange error. Is this perhaps related to the
>> auto-update issue being discussed else-thread?
>>
>> Is there some reason that ruby2js must be === 3.6.0?
>> Raw Bundler exception
>>
>> Exception message:
>>
>> Could not find gem 'ruby2js (= 3.6.0)' in rubygems repository
>> https://rubygems.org/ or installed locally.
>> The source contains the following versions of 'ruby2js': 3.2.0, 4.1.4
>> (Bundler::GemNotFound)
>> Any help will be rewarded in kind(ness).
>> Craig
>>
>>> On Aug 3, 2021, at 7:57 PM, Craig Russell <apache....@gmail.com> wrote:
>>>
>>> I think Apple has indicated their intent to discontinue ruby as a
>>> system-provided tool.
>>>
>>> macOS Catalina 10.15 Release Notes
>>> Scripting Language Runtimes
>>> Deprecations
>>> Scripting language runtimes such as Python, Ruby, and Perl are included in
>>> macOS for compatibility with legacy software. Future versions of macOS
>>> won’t include scripting language runtimes by default, and might require you
>>> to install additional packages. If your software depends on scripting
>>> languages, it’s recommended that you bundle the runtime within the app.
>>> (49764202)
>>>
>>>
>>>
>>>> On Aug 3, 2021, at 3:25 PM, Sam Ruby <ru...@intertwingly.net
>>>> <mailto:ru...@intertwingly.net> <mailto:ru...@intertwingly.net
>>>> <mailto:ru...@intertwingly.net>>> wrote:
>>>>
>>>> On Tue, Aug 3, 2021 at 3:32 PM Craig Russell <apache....@gmail.com
>>>> <mailto:apache....@gmail.com> <mailto:apache....@gmail.com
>>>> <mailto:apache....@gmail.com>>> wrote:
>>>>>
>>>>> [MacBook-Pro-10:~] clr% head -1 `which bundle`
>>>>> #!/usr/local/opt/ruby/bin/ruby
>>>>> [MacBook-Pro-10:~] clr% head -1 `which gem`
>>>>> #!/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
>>>>
>>>> Unless you have a reason to want two versions of Ruby, I would
>>>> recommend that you stick with the system installed version. You
>>>> should be able to remove the non-system installed Ruby using:
>>>>
>>>> $ brew uninstall ruby
>>>>
>>>> Whether or not you want to do that (and whether or not removing it
>>>> works) Try to install/overwrite bundler:
>>>>
>>>> $ sudo gem install bundler
>>>>
>>>> If this works (i.e., the two commands at the top of this email
>>>> starting with "head -1" now return the same results), try rerunning
>>>> setupmymac.
>>>
>>> I'll try that. I guess if Apple ever does get rid of ruby I can easily
>>> reinstall it.
>>>
>>> Craig
>>>>
>>>> - Sam Ruby
>>>
>>> Craig L Russell
>>> c...@apache.org <mailto:c...@apache.org> <mailto:c...@apache.org
>>> <mailto:c...@apache.org>>
>> Craig L Russell
>> c...@apache.org <mailto:c...@apache.org>
Craig L Russell
c...@apache.org
