James McCoy wrote:
> On Thu, Dec 08, 2011 at 03:17:52PM +0100, Bram Moolenaar wrote:
> >
> > Patch 7.3.368
> > Problem: Gcc complains about redefining _FORTIFY_SOURCE.
> > Solution: Undefine it before redefining it.
> > Files: src/Makefile, src/configure.in, src/auto/configure
> >
> >
> > *** ../vim-7.3.367/src/Makefile 2011-10-20 16:35:25.000000000 +0200
> > --- src/Makefile 2011-12-08 15:16:13.000000000 +0100
> > ***************
> > *** 561,568 ****
> > #CFLAGS = -g -O2 '-DSTARTUPTIME="vimstartup"' -fno-strength-reduce -Wall
> > -Wmissing-prototypes
> >
> > # Use this with GCC to check for mistakes, unused arguments, etc.
> > ! #CFLAGS = -g -Wall -Wextra -Wmissing-prototypes -Wunreachable-code
> > -D_FORTIFY_SOURCE=1
> > ! #CFLAGS = -g -O2 -Wall -Wextra -Wmissing-prototypes -D_FORTIFY_SOURCE=1
> > -DU_DEBUG
>
> _FORTIFY_SOURCE is actually supposed to be in CPPFLAGS, so anything
> building Vim with it specified in the proper environment variable won't
> be caught by configure's checks.
What makes you think that _FORTIFY_SOURCE should be in CPPFLAGS? Do you
have a reference?
--
hundred-and-one symptoms of being an internet addict:
260. Co-workers have to E-mail you about the fire alarm to get
you out of the building.
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
