Databases
StackOverflow2013
Postsdbo
POCan't install ruby-ldap under Windows/Cygwin
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't install ruby-ldap under Windows/Cygwin
    text
    copied!<p><code>gem install ruby-ldap</code></p> <pre><code>Building native extensions. This could take a while... ERROR: Error installing ruby-ldap: ERROR: Failed to build gem native extension. /usr/bin/ruby.exe extconf.rb --with-ldap-dir=/usr --with-openldap2 checking for ldap.h... yes [...] creating Makefile make gcc -I. -I. -I/usr/lib/ruby/1.8/i386-cygwin -I. ... [...] gcc -shared -s -o ldap.so ... </code></pre> <p>The configuration and the compilation works just fine. But the installation throws this error:</p> <pre><code>make install /usr/bin/install -c -m 0755 ldap.so /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib /usr/bin/install -c -m 644 ./lib/ldap/control.rb /usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap /usr/bin/install: `./lib/ldap/control.rb' and `/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb' are the same file Makefile:130: recipe for target `/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb' failed make: *** [/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb] Error 1 </code></pre> <p><code>./lib/ldap/control.rb</code> and <code>/usr/lib/ruby/gems/1.8/gems/ruby-ldap-0.9.12/lib/ldap/control.rb</code> are indeed the same file, but why? Other gems with nativ bindings like <code>mysql</code> worked just fine. I reported this as a bug, but some other guy does not have the problem, so the package itself is intact.</p> <p>If I download the gem and run:</p> <pre><code>ruby extconf.rb make install </code></pre> <p>The Makefile runs just fine. It must be my system/configuration. Whats going wrong here?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload