Date: Fri, 10 Apr 2015 09:09:51 +0100 From: Matt Smith <fbsd@xtaz.co.uk> To: Dewayne Geraghty <dewayne.geraghty@heuristicsystems.com.au> Cc: freebsd-ports@freebsd.org Subject: Re: openssl and bash libcrypto Message-ID: <20150410080951.GD1280@xtaz.uk> In-Reply-To: <5527769D.3060505@heuristicsystems.com.au> References: <552657AC.1020802@ish.com.au> <55271AB5.8020907@ish.com.au> <CABgom6fORDqZUg8HvHLCMuRFVtSxvEF0U0jFvBRKJUm%2BKmJ6Sw@mail.gmail.com> <55272BC5.8090805@ish.com.au> <5527769D.3060505@heuristicsystems.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Apr 10 17:07, Dewayne Geraghty wrote: >part of the base system. If your system is crashing due to /usr/bin/vi >which is part of the base system, then something is very wrong with the >system. I'm guessing but is it possible that you've installed 32 libs >onto a 64 base system, or the other way around? > >I can't see how vi needs anything under /usr/local, as its from the >"base" system - so I guess others may need to step up to assist. See the comments in the PR at https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198788 It appears that on certain hardware compiling openssl 1.0.2 with the ASM optimisations turned on, which is the default, can cause all sorts of strange issues. I had the same issues with vi, bash, and all sorts of things both in the base system and the ports system. I have no idea why or how. But disabling ASM and recompiling it works around the issue. It seems to completely corrupt the environment. Matt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150410080951.GD1280>