Ticket #328 (closed defect: invalid)

Opened 13 months ago

Last modified 11 months ago

While installing on Windows XP got the error

Reported by: pravin Owned by: somebody
Priority: major Milestone:
Component: component1 Version:
Keywords: Cc: experiments.with.fb@…

Description

Building native extensions. This could take a while... ERROR: Error installing ferret:

ERROR: Failed to build gem native extension.

C:/ruby/bin/ruby.exe extconf.rb install ferret creating Makefile

nmake 'nmake' is not recognized as an internal or external command, operable program or batch file.

Gem files will remain installed in C:/ruby/lib/ruby/gems/1.8/gems/ferret-0.11.6 for inspection. Results logged to C:/ruby/lib/ruby/gems/1.8/gems/ferret-0.11.6/ext/gem_make.out

Attachments

Change History

  Changed 13 months ago by dbalmain

  • status changed from new to closed
  • resolution set to invalid

You need to install the win32 gem when installing on windows unless you have Visual C 6.0 installed.

follow-up: ↓ 4   Changed 12 months ago by anonymous

  • cc experiments.with.fb@… added
  • status changed from closed to reopened
  • resolution invalid deleted

I still get the same error when i do gem install ferret.

ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError?)

Bad file descriptor - connect(2)(Errno::EBADF)

I have downloaded the win32 gem from http://rubyforge.org/frs/?group_id=1028&release_id=3198

In what default locations does gem check when installing?

  Changed 12 months ago by anonymous

  • status changed from reopened to closed
  • resolution set to fixed

Its ok now.

in reply to: ↑ 2 ; follow-up: ↓ 5   Changed 12 months ago by dbalmain

Replying to anonymous:

I still get the same error when i do gem install ferret. ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError?) Bad file descriptor - connect(2)(Errno::EBADF)

Just for the sake of completeness, I just thought I had better add here that I did nothing to fix this. This error just occurs sometimes when something funny is going on with the gem servers and has nothing to do with Ferret.

Anyway, I'm happy to hear you managed to get it to install.

in reply to: ↑ 4 ; follow-up: ↓ 6   Changed 11 months ago by anonymous

  • status changed from closed to reopened
  • resolution fixed deleted

Replying to dbalmain:

Replying to anonymous:

I still get the same error when i do gem install ferret. ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError?) Bad file descriptor - connect(2)(Errno::EBADF)

Just for the sake of completeness, I just thought I had better add here that I did nothing to fix this. This error just occurs sometimes when something funny is going on with the gem servers and has nothing to do with Ferret. Anyway, I'm happy to hear you managed to get it to install.

i still can't..even though i downloaded and tried to install from local..same error

in reply to: ↑ 5   Changed 11 months ago by dbalmain

Replying to anonymous:

Replying to dbalmain:

Replying to anonymous:

I still get the same error when i do gem install ferret. ERROR: While executing gem ... (Gem::RemoteFetcher::FetchError?) Bad file descriptor - connect(2)(Errno::EBADF)

Just for the sake of completeness, I just thought I had better add here that I did nothing to fix this. This error just occurs sometimes when something funny is going on with the gem servers and has nothing to do with Ferret. Anyway, I'm happy to hear you managed to get it to install.

i still can't..even though i downloaded and tried to install from local..same error

Hmmm. It seems a little odd that you are getting a remote fetch error when you are installing locally. And, like I already mentioned, this is an gems error and most likely has nothing to do with Ferret. I'll try and help you out though in case I'm wrong. Could you paste the full output you get from the command including the command you are trying to run?

  Changed 11 months ago by dbalmain

  • status changed from reopened to closed
  • resolution set to invalid

No reply and I'm convinced this has nothing to do with Ferret. If you are still having this problem, please contact me off-line and I'll try and help you out. My email is dbalmain@….

Add/Change #328 (While installing on Windows XP got the error)

Author



Change Properties
<Author field>
Action
as closed
Next status will be 'reopened'
 
Note: See TracTickets for help on using tickets.