Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #4281

Closed
Open
Created 12 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Unable to install eventmachine 1.0.3 dependency - gitlab installation fails

Closed

Unable to install eventmachine 1.0.3 dependency - gitlab installation fails

Created by: dmsimard

When attempting to install the current master branch, I am getting the following error:

Installing eventmachine (1.0.3) sh: 1: Syntax error: Unterminated quoted string

Gem::Installer::ExtensionBuildError: ERROR: Failed to build gem native extension.

    /usr/bin/ruby1.9.1 extconf.rb --with-cflags="-O2 -pipe -march=native -w


Gem files will remain installed in /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3 for inspection.
Results logged to /home/git/gitlab/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/ext/gem_make.out
An error occurred while installing eventmachine (1.0.3), and Bundler cannot continue.

Indeed, in .bundle/config, I can see the following:


---
BUNDLE_BUILD__EVENTMACHINE: --with-cflags="-O2 -pipe -march=native -w
BUNDLE_BUILD__THIN: --with-cflags="-O2 -pipe -march=native -w
BUNDLE_FROZEN: '1'
BUNDLE_PATH: vendor/bundle
BUNDLE_WITHOUT: development:test:postgres
BUNDLE_DISABLE_SHARED_GEMS: '1'

There are no matching double quotes end the string to the BUNDLE_BUILD lines.

I was not able to reproduce this error in 5.2 - eventmachine is not a dependancy to 5.2. This error is obtained both from upgrading 5.2 to master as well as a fresh install of master.

Using Ubuntu 12.04. Note: The package ruby 1.9.3 is used (apt-get install ruby1.9.3), even though the ruby binary file name is ruby1.9.1:

# /usr/bin/ruby1.9.1 -v
ruby 1.9.3p0 (2011-10-30 revision 33570) [x86_64-linux]

I have found this bug in bundler which may be related: https://github.com/bundler/bundler/issues/2469

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: dzaporozhets

      Its not a gitlab bug. Please use Support forum for such issues. P.S. We recommend to you install ruby via installation docs with all mentioned librarires to prevent such issues.

      By Administrator on 2013-06-26T05:52:28 (imported from GitLab project)

    • Administrator
      Administrator @root · 11 years ago
      Owner

      Created by: proudcommerce

      we had the same problem by updating gitlab to 5.3.

      fix in .bundle/config:

      BUNDLE_BUILD__EVENTMACHINE: --with-cflags='-O2' -pipe -march='native' -w BUNDLE_BUILD__THIN: --with-cflags='-O2' -pipe -march='native' -w

      By Administrator on 2013-07-05T07:13:23 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    2
    Labels
    Awaiting developer action/feedback Configuration/Check
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference: