[Rubygems-developers] can not install RubyGems (uninitialized constant YAML::Syck::DefaultLoader (NameError))

Greg Hauptmann greg.hauptmann.ruby at gmail.com
Fri Feb 6 18:46:58 EST 2009


PS. Luis - I did do (probably silly for not understanding what I was
doing) an "apt-get install ruby-libs".  I'm not sure if this is
significant.  I guess I didn't really remember how Ruby was installed
on my box and tried to do an update....

2009/2/7 Greg Hauptmann <greg.hauptmann.ruby at gmail.com>:
> thanks,
>
> gcc version is as follows - could this be the issue?:
> [root at home ruby-1.8.7-p72]# gcc -v
> Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.6 20060404 (Red Hat 3.4.6-9)
> [root at home ruby-1.8.7-p72]#
>
>
>
> The irb test seems good:
> [root at home local]# irb
> irb(main):001:0> require 'yaml'
> => true
> irb(main):002:0> a = [1,2,3]
> => [1, 2, 3]
> irb(main):003:0> puts a.to_yaml
> ---
> - 1
> - 2
> - 3
> => nil
> irb(main):004:0>
>
>
> It seemed to compile syck ok:
> compiling syck
> make[1]: Entering directory `/root/temp/ruby-1.8.7-p72/ext/syck'
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c gram.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c syck.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c token.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c emitter.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c bytecode.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c handler.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c node.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c yaml2byte.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c rubyext.c
> gcc -I. -I../.. -I../../. -I../.././ext/syck -DHAVE_ST_H
> -D_FILE_OFFSET_BITS=64  -fPIC -g -O2   -c implicit.c
> gcc -shared -o ../../.ext/i686-linux/syck.so gram.o syck.o token.o
> emitter.o bytecode.o handler.o node.o yaml2byte.o rubyext.o implicit.o
> -L. -L../.. -L.  -rdynamic -Wl,-export-dynamic    -ldl -lcrypt -lm
> -lc
> make[1]: Leaving directory `/root/temp/ruby-1.8.7-p72/ext/syck'
> compiling syslog
>
>
> Thanks again
>
>
>
>
> 2009/2/7 Luis Lavena <luislavena at gmail.com>:
>> On Fri, Feb 6, 2009 at 7:40 PM, Greg Hauptmann
>> <greg.hauptmann.ruby at gmail.com> wrote:
>>> I did see these warnings in the Ruby make - could this be the issue?
>>>
>>
>> No, those are part of miniruby, later in the make process you should
>> see "compiling syck".
>>
>> That's the one that maybe didn't complete properly.
>>
>> Can you indicate which version of GCC you have? maybe this is
>> something that can be related to Ruby itself and not RubyGems.
>>
>> Please try in the console (irb)
>>
>> require 'yaml'
>> a = [1,2,3]
>> puts a.to_yaml
>>
>> The output should be:
>> ---
>> - 1
>> - 2
>> - 3
>>
>> --
>> Luis Lavena
>> AREA 17
>> -
>> Perfection in design is achieved not when there is nothing more to add,
>> but rather when there is nothing more to take away.
>> Antoine de Saint-Exupéry
>> _______________________________________________
>> Rubygems-developers mailing list
>> Rubygems-developers at rubyforge.org
>> http://rubyforge.org/mailman/listinfo/rubygems-developers
>>
>
>
>
> --
> Greg
> http://blog.gregnet.org/
>



-- 
Greg
http://blog.gregnet.org/


More information about the Rubygems-developers mailing list