From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: [ANNOUNCE] First release candidates for Xen 4.0.4 and 4.1.3 Date: Tue, 08 May 2012 08:50:51 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: M A Young Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 07/05/2012 21:52, "M A Young" wrote: > On Mon, 7 May 2012, Keir Fraser wrote: > >> Folks, >> >> I have just tagged first release candidates for 4.0.4 and 4.1.3: >> >> http://xenbits.xen.org/staging/xen-4.0-testing.hg (tag 4.0.4-rc1) >> http://xenbits.xen.org/staging/xen-4.1-testing.hg (tag 4.1.3-rc1) >> >> Please test! > > I am seeing problems building 4.1.3-rc1 on Fedora 17, though it might be > changes in Fedora 17 rather than xen changes that have triggered it. When > trying to compile objects such as scheduler.c in tools/blktap2/drivers I > get the error > /usr/include/features.h:329:3: error: #warning _FORTIFY_SOURCE requested but > disabled [-Werror=cpp] > > On checking that file I see that this is because -Wp,-D_FORTIFY_SOURCE=2 > is requested with -O0 . Fedora 17 decides to warn about this and it > becomes an error as -Werror is specified. > This conflict occurs because of the line > CFLAGS += -Werror -g -O0 > in tools/blktap2/drivers/Makefile > I can of course work around the problem in my build, but I was wondering > if optimization level 0 is still necessary for this code. I think the > only other place -O0 is used now is tools/security/Makefile which I > assume will also trigger the problem. Thanks. The same appears to be true in xen-unstable also. Is the solution to simply remove -O0 from the command line? We can test that out in xen-unstable if so, and backport if it causes no problems. -- Keir > Michael Young