1

Topic: Unresolved R_X86_64_NONE

Hi all, once again faced a problem, to bypass which "simple update to newer binutils" it is impossible. The problem is described on StackOverflow: https://stackoverflow.com/questions/487 … relocation if someone can answer something intelligible,  from me (including and here %) very much I want to understand WTF at last.

2

Re: Unresolved R_X86_64_NONE

How much I remember it happens when try for example  collected for one architecture, to pick up in  on other architecture for example  is collected for x64 and we cling it to application which gathers for x32

3

Re: Unresolved R_X86_64_NONE

Hello, reversecode, you wrote: R> how much I remember it happens when try for example  collected for one architecture, to pick up in  on other architecture R> for example R>  is collected for x64 R> and we cling it to application which gathers for x32... And then another gets out unresolved: ` R_X86_64_32 `, but it is not my case (and them there how many). All is assembled by one compiler under 64.

4

Re: Unresolved R_X86_64_NONE

It is not enough information on a problem from source codes gathers both  and ? In one stopping? Or  that is pulled already ready collected whence?  ? Can try on other OS with another ? Other version ? To throw  in  and to look at the character on which swears  in such thin errors can understand only itself compiling at whom there is an access to the environment

5

Re: Unresolved R_X86_64_NONE

Hello, reversecode, you wrote: R> there is not enough information on a problem ok, in addition to that that is already told on SO R> from source codes gathers both  and ? boost it is collected in RPM the same toolchain' (DTS-7). R> in one stopping? Not an essence important. The main thing that the same compiler is used for boost'a and my application (a unit tests in this case) R> or  that is pulled already ready collected whence? Collected boost has been delivered from RPM in docker an image (where already is available DTS-7) R>  ? 7.2.1 (from DTS-7) R> can try on other OS with another ? Other version ? It is possible. But it is necessary  this combination (DTS-7). In DTS-4 (GCC 5.3.1) with  collected DTS the compiler from the same RPM spec' the similar problem is not present % (R> to throw  in  and to look at the character on which swears ` nm-D ` and ` readelf ` on libstdc ++. so.6.0.19 Show that ` _ZNSt8ios_base4InitD1Ev @GLIBCXX_3.4 ` character is and is exported (` T `) R>  R> in such thin errors can understand only itself compiling who has an access to the environment therefore and ask the help for I do not understand WTF (while only a guess, to check up which sometimes in any way)

6

Re: Unresolved R_X86_64_NONE

Hello, zaufi, you wrote: Z> very much I want to understand WTF at last. Here such code : https://github.com/cloudera/Impala/comm … 92a53c7291 began from here: http://community.cloudera.com/t5/Intera … /m-p/56741 came here: https://github.com/cloudera/Impala/comm … 87af0beed2 try to pick open, as they  ps. At you tests are an executed file or.so?

7

Re: Unresolved R_X86_64_NONE

Hello, uzhas, you wrote: U> try to pick open, as they  thanks,  ... U> ps. At you tests are an executed file or.so? An executed file