Testing Env: Host: Ubuntu 10.04 LTS Kernel: 2.6.32-21-generic-pae Image location: http://autobuilder.pokylinux.org/milestone/20100911-1/ 1. download sato image from milesone build. 2. boot up qemuarm with sato image 3. run command 'avahi-daemon', error will arise. ################### root@qemuarm:~# avahi-daemon avahi-daemon: error while loading shared libraries: libcap.so.2: cannot open shared object file: No such file or directory ####################
Xianchao, I think you mean the bug is for qemuarm, right? I modify the bug title to make it clear. BTW, the issue is same as bug 288, which is reported against qemux86. So I think maybe it OK to use the same bug to track the same issue. How about your opinion, Saul/Kevin?
cc He Qing.
I'll look into this bug. I think it's better to investigate a little before marking it as duplicated. Although the phenomena of two bugs look the same, theoretically, host contamination cannot happen for qemuarm images (because host and target are different). And, Xianchao, can you see if the patch addressing bug 288 also solves this issue? I've sent to the list, and it should be in master soon.
(In reply to comment #3) > I'll look into this bug. > > I think it's better to investigate a little before marking it as duplicated. > Although the phenomena of two bugs look the same, theoretically, host > contamination cannot happen for qemuarm images (because host and target are > different). > > And, Xianchao, can you see if the patch addressing bug 288 also solves this > issue? I've sent to the list, and it should be in master soon. Where can I get the patch? I only download the milestone build to run test cases, I have not build one image on my host for testing before.
This has been fixed in master not in M3, so this bug should remain open until next weekly testing occurs.
Xianchao, the patch addressing bug 288 is now in poky master as commit 7c99ba847084ca3ccfb3fe206b7b01aa50d50070. (In reply to comment #4) > (In reply to comment #3) > > I'll look into this bug. > > > > I think it's better to investigate a little before marking it as duplicated. > > Although the phenomena of two bugs look the same, theoretically, host > > contamination cannot happen for qemuarm images (because host and target are > > different). > > > > And, Xianchao, can you see if the patch addressing bug 288 also solves this > > issue? I've sent to the list, and it should be in master soon. > Where can I get the patch? I only download the milestone build to run test > cases, I have not build one image on my host for testing before.
Xianchao, Pls. also verify the bug as fixed if you have checked it in your testing.
Verified with milestone build (10/24)