Author [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] [EN] [ZH] [ES] [PT] [IT] [DE] [FR] [NL] [TR] [SR] [AR] [RU] Topic: BitsharesX Mac (old mac) compile error  (Read 772 times)

0 Members and 1 Guest are viewing this topic.

Offline cryptfun

  • Newbie
  • *
  • Posts: 18
    • View Profile
BitsharesX Mac (old mac) compile error
« on: November 03, 2014, 05:14:10 AM »

My mac mini is an old one, it has Core 2 Duo CPU. (bought in 2010)

Following this doc,
wiki.bitshares.org/index.php/BuildInstructionsBitSharesX#Linux_and_OSX

around here,
# OSX users only!
export CMAKE_PREFIX_PATH=~/Qt/5.3/

cmake -DCMAKE_BUILD_TYPE=Release .
make


during the "make" process, it results in error message as below.
Undefined symbols for architecture x86_64:
  "_fchmodat", referenced from:
      boost::filesystem::detail::permissions(boost::filesystem::path const&, boost::filesystem::perms, boost::system::error_code*) in libboost_filesystem.a(operations.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
make[2]: *** [libraries/fc/lzma_test] Error 1
make[1]: *** [libraries/fc/CMakeFiles/lzma_test.dir/all] Error 2
make: *** [all] Error 2



I decided to build by myself because the dmg file also didn't work. I could only see the splash screen and it crashes.

I guess my machine and CPU type has been neglected by the devs.

Offline arubi

  • Sr. Member
  • ****
  • Posts: 209
    • View Profile
Re: BitsharesX Mac (old mac) compile error
« Reply #1 on: November 03, 2014, 10:15:12 AM »
Knowing your cpu model is not enough to help you.
You should list all appropriate versions of software your are using.

What's the OS version?
Compiler version?
What's the version of boost?
(etc.)

Anyway, I'm compiling just fine on an Intel T2060:
http://ark.intel.com/products/28021/Intel-Pentium-Processor-T2060-1M-Cache-1_60-GHz-533-MHz-FSB

For me it seems like you just have very old versions of software (libraries, compiler).
You should try compiling just the command-line wallet, so instead of:
cmake -DCMAKE_BUILD_TYPE=Release .
Use:
Code: [Select]
cmake .Then:
Code: [Select]
make bitshares_clientAnd see if that makes a difference.

Offline cryptfun

  • Newbie
  • *
  • Posts: 18
    • View Profile
Re: BitsharesX Mac (old mac) compile error
« Reply #2 on: November 04, 2014, 01:13:02 AM »
Thanks for reply, but your suggestion also results in the same error.
Below is the related version information.

Processor 2.4 GHz Intel Core 2 Duo
OSX 10.9.5 (13F34)

Boost version: 1.54.0
cmake version 3.0.2
ReadLine: readline-6.3
Berkeley DB: libdb_cxx-6.0

$ make -v
GNU Make 3.81
Copyright (C) 2006  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.

This program built for i386-apple-darwin11.3.0


$ gcc -v
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.10.sdk/usr/include/c++/4.2.1
Apple LLVM version 6.0 (clang-600.0.54) (based on LLVM 3.5svn)
Target: x86_64-apple-darwin13.4.0
Thread model: posix

Offline clayop

Re: BitsharesX Mac (old mac) compile error
« Reply #3 on: November 06, 2014, 03:58:56 AM »
Is this solved? Noone left behind!
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline arubi

  • Sr. Member
  • ****
  • Posts: 209
    • View Profile
Re: BitsharesX Mac (old mac) compile error
« Reply #4 on: November 06, 2014, 07:03:28 PM »
Is this solved? Noone left behind!

You're right, I just didn't have a chance to reply yet (all work, and university, makes arubi... etc).

cryptfun, aside from referring you to this post : https://github.com/bitcoin/bitcoin/issues/3228
I can't really do much more. I have no access to an OSX machine so I can't actively troubleshoot.
It seems that g++ is aliased to clang. Read up on that thread and see if any solution works for you.
I'd start with building with gcc insead of clang and see how that works out.

Let us know how it goes. Good luck.

 

Google+