[fdo-users] Compilation on 64-bit linux

Robin Newton robin.newton at 1spatial.com
Mon Apr 11 10:59:14 EDT 2011


I'm trying to build fdo-3.6.0_5104 on 64-bit Linux (openSUSE 10.2
x86-64, gcc 4.1.2, ld I've run into a number of problems,
some of which I've been able to resolve with minor tweaks to source code
or build scripts. (The biggest change was I made was to use gdal-1.8.0
rather than gdal-1.7.1, as I couldn't get the latter to compile.)

The thing that currently has me stumped is this:

relocation R_X86_64_32 against `boost::detail::(anonymous
namespace)::create_current_thread_tls_key()' can not be used when making
a shared object; recompile with -fPIC
could not read symbols: Bad value

I see that this has been encountered before:


but it doesn't look like this was ever resolved.

Does anyone know if it is possible to build this (or any other) version 
of FDO on 64-bit Linux and, if so, how?

Any help appreciated,

1Spatial: Steering you towards efficient and reliable location-based data with the 1Spatial Data Improvement Process


1Spatial Group Limited; Registered in England No. 4785688 VAT Reg. No. 816329821; Registered Office: Tennyson House; Cambridge Business Park; Cambridge; CB4 0WZ; United Kingdom

This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the sender immediately and delete this e-mail from your system. Please note that any views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of 1Spatial Group Limited, its subsidiaries or associated companies, except where the author specifically states them to be the views of 1Spatial Group Limited, its subsidiaries or associated companies. 
1Spatial Group Limited, its subsidiaries and associated companies will not be held liable for any legally binding obligations that are not the subject of an official 1Spatial purchase order or as part of a contract signed by a director of one of the aforementioned companies.
Although the company has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. You should understand and accept that, when communicating with us by e-mail, it is not a totally secure communications medium.

More information about the fdo-users mailing list