gcc - When ./configure is given conflicting options, which wins? -


i'm building cross-compiling gcc using buildroot, , can supply additional configuration options ./configure step without patching buildroot sources. however, want override option buildroot sources have explicitly set. specifically, buildroot sources have:

$(gcc_src_dir)/configure $(quiet) \ --prefix=/usr \ ... --disable-__cxa_atexit \ ... $(extra_gcc_config_options) 

and i'm hoping put --enable-__cxa_atexit $extra_gcc_config_options , have what's honored.

i'm guessing if buildroot's makefile well-designed enough, in fact happen. i'm trying verify (in documentation, not trial , error) , having trouble finding specification of happens when conflicting options passed ./configure script.

will autotools-based configure scripts handle same way? or might gcc handle 1 way, , (for example) binutils handle different way?

i expect else on has had track down before me. google-fu , so-fu aren't turning up.

the relevant documentation how configuration should work gnu coding standards , running configure scripts / optional features autoconf manual.

they don't mention conflicting options, we're left inspecting shell code in generated configure script. script made autoconf 2.69 processes --enable-foo , --disable-foo options in order , assigns enable_foo, therefore latter option wins.


Comments

Popular posts from this blog

SPSS keyboard combination alters encoding -

Add new record to the table by click on the button in Microsoft Access -

javascript - jQuery .height() return 0 when visible but non-0 when hidden -