[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20111104021450.GA8649@openwall.com>
Date: Fri, 4 Nov 2011 06:14:50 +0400
From: Solar Designer <solar@...nwall.com>
To: owl-dev@...ts.openwall.com
Subject: Re: %optflags for new gcc
On Fri, Nov 04, 2011 at 06:05:13AM +0400, Solar Designer wrote:
> For gcc, we make an attempt to use %optflags_lib for its libraries:
...
> However, apparently this did not work at least for libgomp - notice how
> the address I got is not even 8-byte aligned, which it would be if our
> current %optflags_lib had worked.
Confirmed per gcc build log:
/bin/sh ./libtool --tag=CC --mode=compile /usr/src/world/rpm-work-2/BUILD/gcc-4.6.2/obj-i686-openwall-linux/./gcc/xgcc -B/usr/src/world/rpm-work-2/BUILD/gcc-4.6.2/obj-i686-openwall-linux/./gcc/ -B/usr/i686-openwall-linux/bin/ -B/usr/i686-openwall-linux/lib/ -isystem /usr/i686-openwall-linux/include -isystem /usr/i686-openwall-linux/sys-include -DHAVE_CONFIG_H -I. -I../../../libgomp -I../../../libgomp/config/linux/x86 -I../../../libgomp/config/linux -I../../../libgomp/config/posix -I../../../libgomp -Wall -Werror -ftls-model=initial-exec -march=i486 -mtune=i686 -Wc,-pthread -pipe -march=i686 -O2 -fomit-frame-pointer -mpreferred-stack-boundary=2 -MT alloc.lo -MD -MP -MF .deps/alloc.Tpo -c -o alloc.lo ../../../libgomp/alloc.c
Notice how it appends our non-lib %optflags (starting with -pipe) to
some flags that gcc itself wanted to use. The appending is fine, but we
should have %optflags_lib appended here.
Alexander
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
