Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Horacio Sanson <hsanson@gmail.com>
To: Sup developer discussion <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] Tokyo Cabinet fails with invalid record header
Date: Sun, 19 Jun 2011 22:25:34 +0900	[thread overview]
Message-ID: <201106192225.34516.hsanson@gmail.com> (raw)
In-Reply-To: <1308373312-sup-3728@masanjin.net>

On Saturday 18 June 2011 14:02:59 William Morgan wrote:
> I have pushed a branch called 'leveldb' that uses leveldb instead of
> TokyoCabinet. Can you try this please? You will need to install the
> 'leveldb-ruby' gem.

Sorry but I am unable to install the leveldb-gem. It complains about a missing 
header and I have already installed all the packages that contain that file and 
still no luck:

###########################################
sudo gem1.9.1 install leveldb-ruby
Building native extensions.  This could take a while...
ERROR:  Error installing leveldb-ruby:
        ERROR: Failed to build gem native extension.

/usr/bin/ruby1.9.1 extconf.rb
g++ -c -I. -I./include -DLEVELDB_PLATFORM_POSIX -std=c++0x -O2 -DNDEBUG        
-DUSE_SNAPPY=1 db/builder.cc -o db/builder.o
In file included from ./port/port.h:14:0,
                 from ./db/filename.h:14,
                 from db/builder.cc:7:
./port/port_posix.h:14:22: fatal error: cstdatomic: そのようなファイルやディレクトリはありません
compilation terminated.
make: *** [db/builder.o] エラー 1
##############################################

The error message says that the cstdatomic file does not exists. I installed 
the  libstdc++6-4.4-dev package that has the file in 
(/usr/include/c++/4.4/cstdatomic) but the build system fails to find it.

-- 
regards,                                                                                                                                                                                                       
Horacio Sanson
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel

  reply	other threads:[~2011-06-19 13:30 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14  8:36 Horacio Sanson
2011-06-14 17:30 ` William Morgan
2011-06-14 22:36   ` Horacio Sanson
2011-06-15 15:11     ` William Morgan
2011-06-18  5:02       ` William Morgan
2011-06-19 13:25         ` Horacio Sanson [this message]
2011-06-19 18:30           ` William Morgan
2011-06-19 21:59             ` William Morgan
2011-06-19 22:48               ` Horacio Sanson
2011-06-20  3:54                 ` William Morgan
2011-06-20  5:23                   ` Horacio Sanson
2011-06-20 16:42                     ` William Morgan
2011-06-20 22:26                       ` Horacio Sanson
2011-06-20 22:52                         ` William Morgan
2011-06-22  3:25                           ` William Morgan
2011-06-22 12:38                             ` Horacio Sanson
2011-06-22 18:06                               ` William Morgan
2011-06-28 17:42                                 ` Alvaro Herrera
2011-06-29  5:18                                   ` William Morgan
2011-06-22 22:41                             ` Horacio Sanson
2011-06-22 23:36                               ` William Morgan
2011-06-23 13:29                                 ` Horacio Sanson
2011-06-23 15:44                                   ` William Morgan
2011-06-15 15:16     ` William Morgan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201106192225.34516.hsanson@gmail.com \
    --to=hsanson@gmail.com \
    --cc=sup-devel@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox