You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2013/05/03 06:12:16 UTC

[jira] [Resolved] (TS-1842) traffic_(logstats|logcat|sac) doesn't compile on the latest Ubuntu

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

James Peach resolved TS-1842.
-----------------------------

       Resolution: Duplicate
    Fix Version/s: 3.3.3
         Assignee: James Peach

This should be fixed by TS-1843.
                
> traffic_(logstats|logcat|sac) doesn't compile on the latest Ubuntu
> ------------------------------------------------------------------
>
>                 Key: TS-1842
>                 URL: https://issues.apache.org/jira/browse/TS-1842
>             Project: Traffic Server
>          Issue Type: Bug
>         Environment: Ubuntu 13.04, g++ 4.7.3
>            Reporter: Igor Galić
>            Assignee: James Peach
>             Fix For: 3.3.3
>
>
> {noformat}
> make[1]: Entering directory `/home/igalic/src/asf/trafficserver/proxy'
>   CXXLD  traffic_logcat
> /usr/bin/ld.bfd.real: ../iocore/eventsystem/libinkevent.a(UnixEventProcessor.o): undefined reference to symbol 'hwloc_get_type_depth'
> /usr/bin/ld.bfd.real: note: 'hwloc_get_type_depth' is defined in DSO /usr/lib/x86_64-linux-gnu/libhwloc.so.5 so try adding it to the linker command line
> /usr/lib/x86_64-linux-gnu/libhwloc.so.5: could not read symbols: Invalid operation
> collect2: error: ld returned 1 exit status
> make[1]: *** [traffic_logcat] Error 1
> {noformat}
> if we run {{make V=1}}, we see: {noformat}make[1]: Entering directory `/home/igalic/src/asf/trafficserver/proxy'
> /bin/bash ../libtool  --tag=CXX   --mode=link g++  -std=c++11 -g -pipe -Wall -Werror -Wno-error=unused-parameter -Wunused-parameter -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic   -o traffic_logcat logcat.o signals.o InkXml.o DiagsConfig.o UglyLogStubs.o logging/liblogging.a ../mgmt/utils/libutils_p.a ../mgmt/libmgmt_p.a ../lib/records/librecprocess.a ../iocore/eventsystem/libinkevent.a ../lib/ts/libtsutil.la -lpthread  -lnsl -lresolv -lrt -lpcre -lssl -lcrypto -L/usr/lib/x86_64-linux-gnu -ltcl8.5 -ldl -lexpat    -lm  
> libtool: link: g++ -std=c++11 -g -pipe -Wall -Werror -Wno-error=unused-parameter -Wunused-parameter -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic -o .libs/traffic_logcat logcat.o signals.o InkXml.o DiagsConfig.o UglyLogStubs.o  logging/liblogging.a ../mgmt/utils/libutils_p.a ../mgmt/libmgmt_p.a ../lib/records/librecprocess.a ../iocore/eventsystem/libinkevent.a ../lib/ts/.libs/libtsutil.so -lpthread -lnsl -lresolv -lrt -lpcre -lssl -lcrypto -L/usr/lib/x86_64-linux-gnu -ltcl8.5 -ldl /usr/lib/x86_64-linux-gnu/libexpat.so -lm -Wl,-rpath -Wl,/opt/ats-trunk/lib
> /usr/bin/ld.bfd.real: ../iocore/eventsystem/libinkevent.a(UnixEventProcessor.o): undefined reference to symbol 'hwloc_get_type_depth'
> /usr/bin/ld.bfd.real: note: 'hwloc_get_type_depth' is defined in DSO /usr/lib/x86_64-linux-gnu/libhwloc.so.5 so try adding it to the linker command line
> /usr/lib/x86_64-linux-gnu/libhwloc.so.5: could not read symbols: Invalid operation
> collect2: error: ld returned 1 exit status{noformat}
> if we manually add {{-lhwloc}} it compiles:
> {noformat}
> /bin/bash ../libtool  --tag=CXX   --mode=link g++  -std=c++11 -g -pipe -Wall -Werror -Wno-error=unused-parameter -Wunused-parameter -O3 -feliminate-unused-debug-symbols -fno-strict-aliasing -Wno-invalid-offsetof -mcx16 -rdynamic   -o traffic_logcat logcat.o signals.o InkXml.o DiagsConfig.o UglyLogStubs.o logging/liblogging.a ../mgmt/utils/libutils_p.a ../mgmt/libmgmt_p.a ../lib/records/librecprocess.a ../iocore/eventsystem/libinkevent.a ../lib/ts/libtsutil.la -lpthread  -lnsl -lresolv -lrt -lpcre -lssl -lcrypto -L/usr/lib/x86_64-linux-gnu -ltcl8.5 -ldl -lexpat    -lm -lhwloc {noformat}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira