You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See eventmachine/eventmachine#345 -- this won't build using bundle install, I'm getting the same error as people in mentioned issue.
compiling rubymain.cpp
rubymain.cpp: In function ‘VALUE t_connect_server(VALUE, VALUE, VALUE)’:
rubymain.cpp:468:42: error: format not a string literal and no format arguments [-Werror=format-security]
rubymain.cpp: In function ‘VALUE t_bind_connect_server(VALUE, VALUE, VALUE, VALUE, VALUE)’:
rubymain.cpp:488:42: error: format not a string literal and no format arguments [-Werror=format-security]
cc1plus: some warnings being treated as errors
make: *** [rubymain.o] Error 1
Further research:
on i386 it compiles all native extensions without problems, just checked. Debian stable @ amd64 is a problematic combination,
thin and nokogiri fail, too,
changing eventmachine, thin and nokogiri versions in Gemfile.lock to fixed ones makes bundle install complete successfully on amd64, but then barkeep doesn't quite work and uses 100% CPU.
The text was updated successfully, but these errors were encountered:
Been able to reproduce this as well.
This is the sole reason stopping me using barkeep in my production development teams.
64-bit is a necessity in this day and age (especially with enterprise servers).
See eventmachine/eventmachine#345 -- this won't build using
bundle install
, I'm getting the same error as people in mentioned issue.Further research:
i386
it compiles all native extensions without problems, just checked. Debian stable @amd64
is a problematic combination,thin
andnokogiri
fail, too,eventmachine
,thin
andnokogiri
versions inGemfile.lock
to fixed ones makesbundle install
complete successfully onamd64
, but thenbarkeep
doesn't quite work and uses 100% CPU.The text was updated successfully, but these errors were encountered: