Broken symbolic links in /usr/lib after compiling and installing -CURRENT

[Ilya Bakulin]

On Mon, May 21, 2012 12:36 pm, Jeremie Le Hen wrote:
> Can you provide the exact commands you have used to create your chroot?
>
Sure!

1. The build host is FreeBSD 8.2-RELEASE-p3 amd64
2. Directory where project resides ($PROJROOT):
/home/kibab/repos/freebsd-cap-git
2. FreeBSD-CURRENT sources are in $PROJROOT/freebsd
3. Object directory is $PROJROOT/obj
4. Installation directory is $PROJROOT/inst

5. Building world: while in $PROJROOT/freebsd, I type:
  make __MAKE_CONF=$PROJROOT/make.conf SRCCONF=$PROJROOT/src.conf -j16
buildworld
...After a while, build ends...
6. while in $PROJROOT/freebsd, type `sudo make buildenv`, after entering
build environment I set nessesary env variables:
PROJROOT=/home/kibab/repos/freebsd-cap-git
MAKEOBJDIRPREFIX=/home/kibab/repos/freebsd-cap-git/obj
DISTDIR=/home/kibab/repos/freebsd-cap-git/inst
DESTDIR=/home/kibab/repos/freebsd-cap-git/inst

7. After that, type:
make __MAKE_CONF=$PROJROOT/make.conf SRCCONF=$PROJROOT/src.conf -j16
installworld

Now I can chroot to newly installed system. FreeBSD 8.2 still allows
running 10-CURRENT binaries, so that's not a problem:
kibab at ssh%pwd
/home/kibab/repos/freebsd-cap-git/inst

kibab at ssh%sudo chroot `pwd` /bin/csh

# ls -l /usr/lib | grep libgcc_s
lrwxr-xr-x  1 0  0       71 May 20 17:31 libgcc_s.so ->
/usr/obj/home/kibab/repos/freebsd-cap-git/freebsd/tmp/lib/libgcc_s.so.1

So the path to shared library is invalid!

This setup was functional for about a year, and it was broken by recent
update. I tried with clean object directory as well, this doesn't change
anything.

-- 
Regards,
Ilya Bakulin
http://kibab.com
xmpp://kibab612@jabber.ru