© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Just ran into this on 32-bit Fedora 8 (eg. an Amazon Web Services "small instance", one of the starter Amazon Machine Images provided by Amazon).
Is there any way the config script could be modified to autodetect the platform bitsize instead of defaulting to 64-bit?
The reason why it would be handy is that the user doesn't always have control over how "./configure" is invoked. For example, installing the "memcache" RubyGem with "gem install memcache", the gem has a bundled version of libmemcached (0.38) and it prebuilds it with a hardcoded "./configure" line.
Normally with RubyGems you can pass in build options like "gem install foo -- --some-option", but that won't work here because that only applies to building the gem itself, not its dependencies. So in this case the only way to install is to run "gem install", let it fail, and then go in and hand-edit the "ext/extconf.rb" file inside the unpacked gem and finish the install manually.
I'm going to see if I can get the memcache gem patched to avoid this issue, but it would be nice for other users of libmemcached could be spared the trouble too. What do you think?