Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libsairedis compile failed undefined ref sai_object_type_get_availability #578

Open
duhbbx opened this issue Mar 18, 2020 · 9 comments
Open

Comments

@duhbbx
Copy link

duhbbx commented Mar 18, 2020

I build sonic (branch 201911) with make all, when compile libsairedis:

[ 01 ] [ target/debs/stretch/libsairedis_1.0.0_amd64.deb ]

then error appeared with following message:

./syncd/syncd.cpp:2987: undefined reference to `sai_object_type_get_availability'
/sonic/src/sonic-sairedis/meta/.libs/libsaimetadata.so: undefined reference to `sai_switch_id_query'
collect2: error: ld returned 1 exit status
Makefile:466: recipe for target 'syncd' failed
make[4]: *** [syncd] Error 1
make[4]: Leaving directory '/sonic/src/sonic-sairedis/syncd'
Makefile:404: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/sonic/src/sonic-sairedis'
Makefile:336: recipe for target 'all' failed
make[2]: *** [all] Error 2
make[2]: Leaving directory '/sonic/src/sonic-sairedis'
dh_auto_build: make -j1 returned exit code 2
debian/rules:28: recipe for target 'binary-syncd' failed
make[1]: *** [binary-syncd] Error 2
make[1]: Leaving directory '/sonic/src/sonic-sairedis'
dpkg-buildpackage: error: fakeroot debian/rules binary-syncd gave error exit status 2
[  FAIL LOG END  ] [ target/debs/stretch/libsairedis_1.0.0_amd64.deb ]
slave.mk:347: recipe for target 'target/debs/stretch/libsairedis_1.0.0_amd64.deb' failed
make: *** [target/debs/stretch/libsairedis_1.0.0_amd64.deb] Error 1
make[1]: *** [Makefile.work:196: all] Error 2
make[1]: Leaving directory '/home/xu/sonic-buildimage'
make: *** [Makefile:7: all] Error 2

platform: cavium
system: debian

Could some one help me with this error? thanks.

@melsom
Copy link

melsom commented Apr 28, 2020

Hello, I am experiencing the same thing. Did you manage to resolve it?

@wendani
Copy link
Contributor

wendani commented Apr 28, 2020

Has cavium sai implementation defined/implemented this symbol?

#578 (comment)

@melsom
Copy link

melsom commented Apr 29, 2020

Has cavium sai implementation defined/implemented this symbol?

#578 (comment)

I am not sure how to proceed. Do you know how to resolve this?

@duhbbx
Copy link
Author

duhbbx commented May 12, 2020 via email

@melsom
Copy link

melsom commented May 12, 2020

Okay great. Did you get it to work? My next issue was that the XP80_Endpoint pre-compiled kernel module which interfaces with the ASIC only was compiled for a certain kernel, and did not work.

Do you have a working CAVIUM image newer than the 2017* posted on the Wiki which you can share? It would be much appreciated! Thank you!

@duhbbx
Copy link
Author

duhbbx commented May 14, 2020 via email

@melsom
Copy link

melsom commented May 14, 2020

Email me on: andreas at terrahost.no and I'll give you a place to upload it! Thank you for your help.

@bahirul
Copy link

bahirul commented Aug 26, 2020

I solve it by copying docker images from others in my company, not focus on this build problem. At 2020-04-29 03:41:47, "Andreas Melsom Haakonsen" [email protected] wrote: Hello, I am experiencing the same thing. Did you manage to resolve it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi, could you explain "copying docker images from others" ? I still can't get it, i have cavium hardware switch and built and same error.

Thanks

@melsom
Copy link

melsom commented Aug 26, 2020

I solve it by copying docker images from others in my company, not focus on this build problem. At 2020-04-29 03:41:47, "Andreas Melsom Haakonsen" [email protected] wrote: Hello, I am experiencing the same thing. Did you manage to resolve it? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Hi, could you explain "copying docker images from others" ? I still can't get it, i have cavium hardware switch and built and same error.

Thanks

Sorry but if you have Cavium hardware there is absolutely nothing out there that supports it or remotely works as it should. It may as well be used as a door stopper. :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants