Tony Mechelynck wrote:

> Is there a reason why the newly introduced compiler flags
> (_POSIX_C_SOURCE, _X_OPEN_SOURCE, and, on the non-GTK non-ruby Tiny
> build, -ansi) are repeated near the end of the gcc command-line? (I
> use incremental build, i.e. I don't run configure myself, I set the
> environment variables for it once and for all, and then I let make
> (called with no arguments for the compile phase) call configure when
> it thinks that it's needed. Otherwise I recompile only the modules
> whose source and/or prerequisites have changed, except that I may run
> "make reconfig" once in a long while if I see an update to some system
> libraries used by gvim.)
> Here is my latest "Huge" command-line:
> gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK  -pthread
> -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include -I/usr/include/freetype2  -D_REENTRANT
> -DORBIT2=1 -pthread -I/usr/include/libgnomeui-2.0
> -I/usr/include/gnome-keyring-1 -I/usr/include/libbonoboui-2.0
> -I/usr/include/libxml2 -I/usr/include/libgnome-2.0
> -I/usr/include/libbonobo-2.0 -I/usr/include/bonobo-activation-2.0
> -I/usr/include/orbit-2.0 -I/usr/include/libgnomecanvas-2.0
> -I/usr/include/gail-1.0 -I/usr/include/libart-2.0
> -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include
> -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16
> -I/usr/include/pango-1.0 -I/usr/include/harfbuzz
> -I/usr/include/pango-1.0 -I/usr/include/freetype2
> -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> -I/usr/include/gnome-vfs-2.0 -I/usr/lib64/gnome-vfs-2.0/include
> -I/usr/include/gconf/2 -I/usr/include/dbus-1.0
> -I/usr/lib64/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib64/glib-2.0/include  -D_POSIX_C_SOURCE=200809L
> -fno-strength-reduce -Wall -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
>  version.c -o objects/version.o
> and here is the corresponding "Tiny" one:
> gcc -c -I. -Iproto -DHAVE_CONFIG_H   -D_POSIX_C_SOURCE=200809L
> -fno-strength-reduce -Wall -ansi -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1
> -ansi        version.c -o objects/version.o
> Looking back at my accumulated logs shows that the "duplicated flags"
> were introduced the last time configure was run by make, yesterday
> (Sat 14-Apr-2018) at about 16:00. The preceding configure (before
> testing for ruby, which for me makes no difference since my Huge build
> has both GTK and ruby and my Tiny build has neither) had added one
> instance each of those same flags.

When running configure, it may pick up existing CFLAGS and other things.
To avoid that, run "make clean" first.  Or even "make distclean", since
you are going to run configure anyway.

In most cases the duplicate arguments are harmless.  And the specific
CPP flags have just been removed.

hundred-and-one symptoms of being an internet addict:
189. You put your e-mail address in the upper left-hand corner of envelopes.

 /// Bram Moolenaar -- --   \\\
///        sponsor Vim, vote for features -- \\\
\\\  an exciting new programming language --        ///
 \\\            help me help AIDS victims --    ///

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

You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Raspunde prin e-mail lui