Date: Sat, 1 Feb 2014 21:55:07 +0100 From: Joel Dahl <joel@vnode.se> To: Thomas Hoffmann <trh411@gmail.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: libelf.so.1 missing after -CURRENT update Message-ID: <E3CA656B-D4B5-49F4-90AC-2F7FF5D80BA9@vnode.se> In-Reply-To: <CAB7-od=4GYGfkL26a%2BJEq2c0BeBcX3hXukO2-43_NxyrRMMhVg@mail.gmail.com> References: <CAB7-od=4GYGfkL26a%2BJEq2c0BeBcX3hXukO2-43_NxyrRMMhVg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
1 feb 2014 kl. 21:52 skrev Thomas Hoffmann <trh411@gmail.com>: > Did my weekly update of -CURRENT today to r261350 from r261236. After = the > upgrade when I tried to run 'pkg' I got the error: >=20 > libelf.so.1 required by libpkg.so.1 >=20 > So, I reinstalled 'pkg', which fixed the problem. Then I ran = pkg_libchk to > see if any other libs were missing and got: >=20 > glib -2.36.3_1: /usr/local/bin/gresource misses libelf.so.1 >=20 > So i re-installed glib and re-ran pkg_libchk against it. No more = missing > libelf.so.1. >=20 > Anyway, I'm wondering if I inadvertently deleted libelf.so.1 during = the > 'make delete-old' or 'make delete-old-libs' steps of the rebuild. > Unfortunately, these are the only two steps of the build process > (mergemaster excepted) that I do not 'script' the output, so I cannot = go > back to see if that is the case. Obviously I need to begin "script'ing > these two steps on future builds. >=20 > Anyone else seen this or that can confirm an inadvertent delete of > libelf.so.1 on my part? I=92m seeing the same thing. =97 Joel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E3CA656B-D4B5-49F4-90AC-2F7FF5D80BA9>