Problem with gio-fam-backend, portupgrade failing...
mark at msen.com
Mon Apr 7 20:35:13 UTC 2008
On Monday 07 April 2008 03:54:12 pm peter harrison wrote:
> I'm having a problem running portupgrade -a. The original run was
> interrupted by a system crash. Now when I try to repeat it fails asking for
> pkgdb -fF to be run.
> When I run this, I get stale dependencies on policykit, but when I say
> "yes" to install, the install of policykit fails on gio-fam-backend (not a
> port I had installed before the attempted upgrade).
> Here's an extract from the build:
> -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/include -pthread
> -DG_LOG_DOMAIN=\"GLib-GIO\" -I../.. -I../../glib -I../../gmodule
> -I../../gio -DG_DISABLE_CAST_CHECKS
> -DGIO_MODULE_DIR=\"/usr/local/lib/gio/modules\" -DGIO_COMPILATION
> -DG_DISABLE_DEPRECATED -O2 -fno-strict-aliasing -pipe -Wall -MT
> libgiofam_la-gfamfilemonitor.lo -MD -MP -MF
> .deps/libgiofam_la-gfamfilemonitor.Tpo -c gfamfilemonitor.c -o
> libgiofam_la-gfamfilemonitor.o >/dev/null 2>&1 mv -f
> .deps/libgiofam_la-gfamfilemonitor.Plo gmake: *** No rule to make target
> `../../gio/libgio-2.0.la', needed by `libgiofam.la'. Stop. *** Error code
> Stop in /usr/ports/devel/gio-fam-backend.
> ** Command failed [exit code 1]: /usr/bin/script -qa
> /tmp/portinstall.72819.0 env make ** Fix the problem and try again.
> ---> Skipping 'sysutils/policykit' because a requisite port
> 'devel/gio-fam-backend' failed (specify -k to force) ** Listing the failed
> packages (-:ignored / *:skipped / !:failed)
> ! devel/gio-fam-backend (unknown build error)
> * sysutils/policykit
> Command failed [exit code 1]: /usr/local/sbin/portinstall
> So now I'm stuck halfway through a portupgrade.
> This is on
> FreeBSD desktop.piggybox 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #5: Wed Apr
> 2 03:41:26 BST 2008 peter at server.piggybox:/usr/obj/usr/src/sys/GENERIC
> Can anyone offer a suggestion for how I fix this?
> Thanks in advance.
> Peter Harrison
I have seen this before, if ( /devel/ ) gio-fam-backend needs a library that
is outdated, it gives this sort of error. I know when I had the issue, it
was that it needs glib 2.16 and I had 2.14. Thankfully it doesn't have too
many dependancies so it isn't hard to check them all.
More information about the freebsd-questions