[ 
https://issues.apache.org/jira/browse/TS-2346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Igor Galić closed TS-2346.
--------------------------

    Resolution: Invalid
      Assignee: Igor Galić

Well, that was silly. The build is picking up the previous installation under 
$prefix, that's why it's trying to link against an ink_atoi64 with a different 
contract.

> tstop link error:  undefined reference to `ink_atoi64(char const*)'
> -------------------------------------------------------------------
>
>                 Key: TS-2346
>                 URL: https://issues.apache.org/jira/browse/TS-2346
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>            Reporter: Igor Galić
>            Assignee: Igor Galić
>
> I consistently get this failure on Linux with 4.1.x as soon as I change 
> {{--prefix}}. No other {{configure}} option makes a difference.
> {code}
> make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/plugins'
> Making all in tools
> make[1]: Entering directory `/home/igalic/src/asf/trafficserver/tools'
>   CXXLD    tstop/tstop
> ../mgmt/api/remote/.libs/libtsmgmt.so: undefined reference to 
> `ink_atoi64(char const*)'
> clang: error: linker command failed with exit code 1 (use -v to see 
> invocation)
> make[1]: *** [tstop/tstop] Error 1
> make[1]: Leaving directory `/home/igalic/src/asf/trafficserver/tools'
> make: *** [all-recursive] Error 1
> 2 igalic@levix ~/src/asf/trafficserver (git)-[4.1.2] % cd - 
> ~/src/asf/trafficserver/tools
> igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] % readelf -a 
> ../mgmt/api/remote/.libs/libtsmgmt.so | c++filt | grep ink_atoi64
> 00000022cb00  004900000007 R_X86_64_JUMP_SLO 0000000000000000 ink_atoi64(char 
> const*) + 0
>     73: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND ink_atoi64(char 
> const*)
>    601: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND ink_atoi64(char 
> const*)
> igalic@levix ~/src/asf/trafficserver/tools (git)-[4.1.2] % 
> {code}



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to