Broken symbolic links in /usr/lib after compiling and installing
-CURRENT
Jeremie Le Hen
jlh at FreeBSD.org
Tue May 22 12:27:26 UTC 2012
Ilya,
On Mon, May 21, 2012 at 01:43:39PM +0200, Ilya Bakulin wrote:
> 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
This is expected I think, as "make buildenv" defines $_SHLIBDIRPREFIX
which is used to make the toolchain use libraries built during stage 4.2
of buildworld.
Just run "make installworld" with the correct DESTDIR and your chroot
will be fine.
--
Jeremie Le Hen
Men are born free and equal. Later on, they're on their own.
Jean Yanne
More information about the freebsd-toolchain
mailing list