Skip to content

failed compile with atomic-1.1.14.gem #32

Open

Description

@waldy45

HI I'm getting a fail on compile with atomic-1.1.14.gem when installing rails with the following output. Im using Windows 7 32bit client & ruby 2.0.0-p247

versions:
atomic-1.1.14.gem
ruby 2.0.0-p247
devkit DevKit-mingw64-32-4.7.2-20130224-1151-sfx.exe

Q:\Ruby200\bin>gem install rails
Fetching: i18n-0.6.5.gem (100%)
Successfully installed i18n-0.6.5
Fetching: multi_json-1.8.0.gem (100%)
Successfully installed multi_json-1.8.0
Fetching: tzinfo-0.3.37.gem (100%)
Successfully installed tzinfo-0.3.37
Fetching: atomic-1.1.14.gem (100%)
Temporarily enhancing PATH to include DevKit...
Building native extensions. This could take a while...
ERROR: Error installing rails:
ERROR: Failed to build gem native extension.

Q:/Ruby200/bin/ruby.exe extconf.rb
creating Makefile

make "DESTDIR="
generating atomic_reference-i386-mingw32.def
compiling atomic_reference.c
atomic_reference.c: In function 'ir_compare_and_set':
atomic_reference.c:75:2: error: #error No CAS operation available for this platf
orm
make: *** [atomic_reference.o] Error 1

Gem files will remain installed in Q:/Ruby200/lib/ruby/gems/2.0.0/gems/atomic-1.
1.14 for inspection.
Results logged to Q:/Ruby200/lib/ruby/gems/2.0.0/gems/atomic-1.1.14/ext/gem_make
.out

Q:\Ruby200\bin>

Activity

  1. sunaku commented on Oct 15, 2013

    @sunaku

    👍 I'm hitting the same problem on CentOS 5.6 running 64-bit Linux 2.6.18-348.2.1.el5. 😓

    $ gem install atomic -v '1.1.14'
    Building native extensions.  This could take a while...
    ERROR:  Error installing atomic:
            ERROR: Failed to build gem native extension.
    
        /ruby-2.0.0-p247/bin/ruby extconf.rb
    creating Makefile
    
    make "DESTDIR="
    compiling atomic_reference.c
    atomic_reference.c: In function ‘ir_compare_and_set’:
    atomic_reference.c:75:2: error: #error No CAS operation available for this platform
    Makefile:223: recipe for target 'atomic_reference.o' failed
    make: *** [atomic_reference.o] Error 1
    
    
    Gem files will remain installed in /rubygems/gems/atomic-1.1.14 for inspection.
    Results logged to /rubygems/gems/atomic-1.1.14/ext/gem_make.out
    exit 1
  2. sunaku commented on Oct 16, 2013

    @sunaku

    Good news! ✨ This gem installs correctly under GCC 4.8.1: 🍰

    $ env PATH="/gcc-4.8.1/bin:$PATH" gem install atomic -v '1.1.14'
    Building native extensions.  This could take a while...
    Successfully installed atomic-1.1.14
    1 gem installed

    Previously, I was using GCC 4.7.2 and faced the problem described in this issue.

  3. headius commented on Oct 28, 2013

    @headius
    Owner

    I'd be willing to accept additional patches to aid building on older GCC, but for now since this is working I'm going to close it.

  4. Professionalusername commented on Nov 23, 2013

    @Professionalusername

    Have you found any solutions to the problem in Windows 7, 32 bit? My issue is identical to the OP, except that I'm using ruby 1.9.3.

  5. waldy45 commented on Nov 25, 2013

    @waldy45
    Author

    Hi, my client dropped his requirement for this, so I didn't follow up. hedius managed to install atomic using a later gcc v 4.8.1

  6. sixty4bit commented on Dec 26, 2013

    @sixty4bit

    atomic-1.1.10.gem
    ruby 2.0.0-p353
    devkit DevKit-mingw64-32-4.7.2-20130224-1151-sfx.exe

    The fix I found was to add the DevKit\mingw\bin directory to my PATH. This does not normally get added.

  7. added this to the atomic-1.1.15 milestone on Feb 26, 2014
  8. reopened this on Mar 1, 2018
  9. headius commented on Mar 1, 2018

    @headius
    Owner

    Old bugs never die!

    @cesar-valdez Perhaps there's something we can do to our Makefile to fix this? Your fix confuses me a bit! 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions