search for: dsomething_something

...;s important, and I've had my experience with never hearing back even after asking for confirmation of success. Same as drive-by patch drops. > > - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, LDFLAGS > > in favor of passing these exclusively as cmake's > > -Dsomething_something=<FLAGS>? Linux distros usually have an > > environment with CFLAGS etc. and use that building packages and > > this didn't interfere in the past in my builds, but I'm open to > > avoid this by unsetting any such variables first. > > > The problem I'...

...ith the new build because the ninja scripts hard-code paths to CC and CXX which then ends in an error. I tried twice, and before I try another build, ​ ​ I wonder about this: - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, LDFLAGS in favor of passing these exclusively as cmake's -Dsomething_something=<FLAGS>? Linux distros usually have an environment with CFLAGS etc. and use that building packages and this didn't interfere in the past in my builds, but I'm open to avoid this by unsetting any such variables first. - Is there a configuration in the CI matrix that builds all...

...hard-code paths to CC and CXX which then > ends in an error. > > I tried twice, and before I try another build, > ​ ​ > I wonder about this: > > - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, > LDFLAGS in favor of passing these exclusively as > cmake's -Dsomething_something=<FLAGS>? Linux distros > usually have an environment with CFLAGS etc. and use > that building packages and this didn't interfere in the > past in my builds, but I'm open to avoid this by unsetting > any such variables first. > The problem I've had in the pa...

...d my experience with never > hearing back even after asking for confirmation of success. Same as > drive-by patch drops. > > > > - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, LDFLAGS > > > in favor of passing these exclusively as cmake's > > > -Dsomething_something=<FLAGS>? Linux distros usually have an > > > environment with CFLAGS etc. and use that building packages and > > > this didn't interfere in the past in my builds, but I'm open to > > > avoid this by unsetting any such variables first. > > > &g...

...; scripts hard-code paths to CC and CXX which then > ends in an error. > > I tried twice, and before I try another build, > I wonder about this: > > - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, > LDFLAGS in favor of passing these exclusively as > cmake's -Dsomething_something=<FLAGS>? Linux distros > usually have an environment with CFLAGS etc. and use > that building packages and this didn't interfere in the > past in my builds, but I'm open to avoid this by unsetting > any such variables first. > > - Is there a configuration in...

On Tue, Oct 4, 2016 at 10:15 AM, Carsten Mattner <carstenmattner at gmail.com> wrote: > On Tue, Oct 4, 2016 at 2:22 AM, Xinliang David Li <xinliangli at gmail.com> > wrote: > > For clang build, cmake flags: > > > > -DCMAKE_EXE_LINKER_FLAGS=-fuse-ld=gold \ > > -DCMAKE_MODULE_LINKER_FLAGS=-fuse-ld=gold \ > >

...t; scripts hard-code paths to CC and CXX which then > ends in an error. > > I tried twice, and before I try another build,​ ​I wonder about this: > > - Should I avoid any and all CFLAGS, CXXFLAGS, CPPFLAGS, > LDFLAGS in favor of passing these exclusively as > cmake's -Dsomething_something=<FLAGS>? Linux distros > usually have an environment with CFLAGS etc. and use > that building packages and this didn't interfere in the > past in my builds, but I'm open to avoid this by unsetting > any such variables first. > > - Is there a configuration in...