Date: Mon, 29 May 2017 17:28:16 -0700 From: Kevin Casey <kcaseysw@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: side-effects from mesa-libs and ino64 updates ...? Message-ID: <e67478b8-b6a2-3860-652c-04e8d5d4667f@gmail.com> In-Reply-To: <CAPyFy2BwEVj10ttS3L4h8JX7EKV8B77vOja1CM2bEXGJBWwPJg@mail.gmail.com> References: <CAPyFy2BwEVj10ttS3L4h8JX7EKV8B77vOja1CM2bEXGJBWwPJg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I would appreciate observations about two difficulties that have surfaced for me since the mesa-libs and ino64 updates. Likely these are pilot errors but I've not been able to identify the causes. Here's the environment ... FreeBSD silver 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r318232: Fri May 12 00:21:37 PDT 2017 root@silver:/usr/src/sys/amd64/compile/silver amd64 /usr/src revision: 319159 /etc/src-env.conf WITH_META_MODE=yes NO_SILENT=yes rm -r /usr/obj 1. buildworld runs now fail: Building /usr/obj/usr/src/share/colldef/es_MX.UTF-8.LC_COLLATE --- all_subdir_lib --- /usr/obj/usr/src/tmp/usr/lib/libgcc_s.so: undefined reference to `__gxx_personality_v0' cc: error: linker command failed with exit code 1 (use -v to see invocation) 2. with ports as of: Fetching snapshot metadata... done. Updating from Sat May 27 09:42:54 PDT 2017 to Sun May 28 16:37:47 PDT 2017. echo $QT_SELECT qt5 attempting to re-install devel/py-qt5-core with portmaster -d py27-qt5-core yields Error: Failed to determine the detail of your Qt installation. Thanks for your thoughts. Kevin Casey
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e67478b8-b6a2-3860-652c-04e8d5d4667f>