do_sqlite3 does not generate proper pure ruby gem when created with "rake native gem"
Reported by ronin-11960 (at lighthouseapp) | January 8th, 2009 @ 02:20 PM
When issuing "rake native gem" for do_sqlite3, two gems are created: a pure ruby gem which should compile native extensions on installation, and a native gem which includes the .so. The problem is that the pure ruby gem does not compile native extensions when installed.
Comments and changes to this ticket
-
Luis Lavena January 8th, 2009 @ 08:31 PM
- Tag changed from “do_sqlite3” to “gem extensions, do_sqlite3”
- State changed from “unconfirmed” to “accepted”
I can confirm this, and also found the root of the problem.
It seems RubyGems doesn't allow clone (dup) of gem specifications.
Because of that, when invoking
nativemodifies theGem::Specificationthus break the normal (pure-ruby) gem.A patch and a release for rake-compiler is under way.
Please apologize the inconvenience.
-
Luis Lavena January 8th, 2009 @ 09:07 PM
- State changed from “accepted” to “resolved”
The fix for rake-compiler has been committed:
http://github.com/luislavena/rak...
A new gem has been released (0.3.1) to RubyForge.
Please reopen this ticket if the problem continues.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Luis Lavena