Ok, thanks. Could you redirect your entire build output from 4.6 to a file and send it along (or upload it somewhere if you don't want to send to the whole list). Maybe that will provide a clue. On Wed, Oct 20, 2010 at 10:23 PM, Jim Ursetto <address@hidden> wrote:
Hi there.
Did you happen to install over an older version of chicken, one which
may have left a libchicken.so remnant there? From your mail, it
sounds like libchicken.so already existed and it was a real file
instead of a symlink, is that correct?
yes and NO. I did install 4.6 over 4.5 for the first time and got the complaint. Then I suspected as you do it was caused by the left libchicken.so from 4.5. Then I tried to reinstall 4.5 from the repos (btw, I am on Arch, in whose repos still lies the older 4.5) and removed it to see if `pacman' (the package manager of Arch) did a bad job. But the answer is NO, it removed everything, no such libchicken.so left in /usr/lib/. Then I built 4.6 and installed it. After the installation, the complaint appeared. An `ls -l /usr/lib/libchicken.*' showed that libchicken.so was **indeed** not a symbolic link to libchicken.so.5 but a real file.
Jim
2010/10/18 Yi DAI <address@hidden>:
> Hi,
>
> After installing 4.6.0 to /usr. It seems that /usr/lib/libchicken.so is not
> a symbolic link to /usr/lib/libchicken.so.5 which causes ldconfig to
> complain on my system. I change it to a symbolic link solving the problem.
> Just report it here. Thanks
>
> Best,
>
> --
> DAY
> Chicken-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/chicken-users
>
>
-- DAI Yi (代 毅)
|