Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 23 Jan 2015 23:33:19 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 196674] security/keepassx2 bus error on
Message-ID:  <bug-196674-13-Y39t8aYsOA@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-196674-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-196674-13@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=196674

--- Comment #16 from Ivan Brawley <ivan@brawley.id.au> ---
(In reply to Eric Camachat from comment #15)

I think I've reproduced what you are seeing. And after syncing up my 11-CURRENT
VM to the most recent.

You are setting CFLAGS somewhere else? (environment variable or
/etc/make.conf?)

I can see in your cc_is_clang log there are some extra options to cc. And in
your cc_is_clang-O1 log, I can't see it actually using that.

If I set $CFLAGS env variable with "-pipe -march=corei7 -g" (-m and -g are the
extra options), configure doesn't add any -O options and I get the crash. But
if I also add -O2 to the list, all is good.

In fact, setting $CFLAGS to just "-pipe" so that the cc commands are the same
as the defaults with the -O option removed, it still crashes. And the same
thing for -O0. Which is odd as I tested that before (perhaps that testing
produced incorrect results).

Doing some more debugging, there is a bug in the libgcrypt's cipher/Makefile
when turning down the optimisations for cipher/tiger.o (and with my patch, for
cipher/salsa20.c). It echos a libtool commandline through sed to change the
-Oblah to -O1, but the first s// sed command will only change the first
instance of -Oblah found, not all of them. So you could end up with multiple
different -Oblah options to cc, which will further complicate debugging, etc.

Eric, try having a look around your Makefile, env variables and /etc/make.conf,
etc to see if you are also trying to set CFLAGS and remove it so that it will
compile libgcrypt with a clean environment. You should see in the build log the
rest of the modules compiling with -O2 for instance.

ivan.

-- 
You are receiving this mail because:
You are the assignee for the bug.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-196674-13-Y39t8aYsOA>