ruby -d
? Do you get the same error for other gems too? Maybe an exception is being raised and caught internally when Rubygems loads something.
-d
for similar reasons - third-party is often written without -d
in mind and there's no way to disable all the warnings that result from it.
Powered by mwForum 2.29.7 © 1999-2015 Markus Wichitill