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: Mon, 20 Jun 2011 07:48:38 +0900 [thread overview]
Message-ID: <201106200748.38303.hsanson@gmail.com> (raw)
In-Reply-To: <1308520727-sup-5380@masanjin.net>
This morning I tried with g++-4.4 and got a different error. When I return from
work I will look into it. In the meantime this is the error:
rm -f libleveldb.a
ar -rs libleveldb.a ./db/builder.o ./db/db_impl.o ./db/db_iter.o
./db/filename.o ./db/dbformat.o ./db/log_reader.o ./db/log_writer.o
./db/memtable.o ./db/repair.o ./db/table_cache.o ./db/version_edit.o
./db/version_set.o ./db/write_batch.o ./port/port_posix.o ./table/block.o
./table/block_builder.o ./table/format.o ./table/iterator.o ./table/merger.o
./table/table.o ./table/table_builder.o ./table/two_level_iterator.o
./util/arena.o ./util/cache.o ./util/coding.o ./util/comparator.o
./util/crc32c.o ./util/env.o ./util/env_posix.o ./util/hash.o
./util/histogram.o ./util/logging.o ./util/options.o ./util/status.o
ar: creating libleveldb.a
creating Makefile
make
g++ -I. -I/usr/lib/ruby/1.8/x86_64-linux -I/usr/lib/ruby/1.8/x86_64-linux -I.
-fPIC -fno-strict-aliasing -g -g -O2 -fPIC -I../../leveldb/include -c
leveldb.cc
gcc -shared -o leveldb.so leveldb.o -L. -L/usr/lib -L. -Wl,-Bsymbolic-
functions -rdynamic -Wl,-export-dynamic -lruby1.8 -lpthread -lrt -ldl -
lcrypt -lm -lc -L../../leveldb -lleveldb
/usr/bin/ld: ../../leveldb/libleveldb.a(db_impl.o): relocation R_X86_64_32S
against `vtable for leveldb::DBImpl::RecoverLogFile(unsigned long,
leveldb::VersionEdit*, unsigned long*)::LogReporter' can not be used when
making a shared object; recompile with -fPIC
../../leveldb/libleveldb.a: could not read symbols: Bad value
collect2: ld returned 1 exit status
make: *** [leveldb.so] エラー 1
This is my g++:
g++ --version
g++ (Ubuntu/Linaro 4.4.5-15ubuntu1) 4.4.5
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
On Monday 20 June 2011 06:59:02 William Morgan wrote:
> Reformatted excerpts from William Morgan's message of 2011-06-19:
> > Reformatted excerpts from Horacio Sanson's message of 2011-06-19:
> > > ./port/port_posix.h:14:22: fatal error: cstdatomic:
> > > そのようなファイルやディレクトリはありません
> >
> > What is the output of g++ --version on your system, please?
>
> Try version 0.4. I believe it should work for oyu.
--
regards,
Horacio Sanson
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2011-06-19 22:49 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
2011-06-19 18:30 ` William Morgan
2011-06-19 21:59 ` William Morgan
2011-06-19 22:48 ` Horacio Sanson [this message]
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=201106200748.38303.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