Brian Kroth wrote:
I had also seen this in the bug. Do you know if there's a way to
specify per package CFLAG customizations in portage?
Also, does anyone know if this is being fixed on bind's end of things?
Thanks,
Brian
Akos Szalkai wrote:
I recently upgraded to bind-9.3.4 via portage, and it now keeps core
dumping on me. Anyone running chrooted
bind-9.3.4+hardended+grsecurity having this problem?
Yes, it also happens to non-chrooted bind. This is bug #158664.
Basically, using -O instead of -O2 (gcc optimization) solved it for me.
Akos
I've done this on my laptop a few times, and am not too familiar. But I
have the file:
/etc/portage/env/dev-libs/beecrypt-3.1.0-r2
and the contents are:
CFLAGS="-O2 -march=pentium3 -pipe -fomit-frame-pointer"
This is on a Pentium-M laptop, but it won't compiler unless I set
"march=pentium3". With this structure I've changed march= for just the
one version of the package. I've experimented with having an unversioned
package and it works, too. In this particular case, I now have
beecrypt-4.1.2-r1 and apparently it has compiled just fine with my
default "march=pentiumm". I believe it overrides the whole CFLAGS
environment variable, not piece by piece.
Dale Pontius
--
[email protected] mailing list
