Date: Sun, 08 Jan 2017 05:24:36 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ppc@FreeBSD.org Subject: [Bug 200020] [patch] editors/libreoffice: enable build on powerpc64 Message-ID: <bug-200020-21-95QAhBVCdj@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-200020-21@https.bugs.freebsd.org/bugzilla/> References: <bug-200020-21@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D200020 --- Comment #14 from Curtis Hamilton <hamiltcl@verizon.net> --- I see. Using a jail is a good idea, as long as the jail environment is comparable to the live environment. However, different versions of runtime libraries can cause undesired behaviors. I have the luxury of having two separate systems for building and testing. >From what you've stated, I do believe what you are seeing is the difference= in the stdc++ libs used by GCC49 and /usr/bin/gcc. Especially, if 'usr/bin/gcc= ' is the stock GCC distribution. That is why I asked about '/etc/libmap.conf.' Y= ou can perform a quick check by checking for the presence, or absence, of 'GLIBCXX_3.4.18' by doing the following: strings /usr/lib/libstdc++*|grep GLIBCXX I've had this happen to me when building a port on one system and installin= g on another, after upgrading GCC on the build system.=20 BTW, what version of FreeBSD are you using? --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-200020-21-95QAhBVCdj>