On Monday, 12 March 2018 08:27:31 GMT Alexander Kapshuk wrote: > On Mon, Mar 12, 2018 at 10:17 AM, Mick <michaelkintz...@gmail.com> wrote: > > I can see a few warnings pilling up on different systems when trying to > > emerge chromium-65.0.3325.146: > > > > warning: unknown warning option '-Wno-enum-compare-switch'; did you mean > > '- > > Wno-enum-compare'? [-Wunknown-warning-option] > > warning: unknown warning option '-Wno-tautological-unsigned-zero-compare' > > [- Wunknown-warning-option] > > warning: unknown warning option '-Wno-null-pointer-arithmetic'; did you > > mean '-Wno-null-arithmetic'? [-Wunknown-warning-option] > > warning: unknown warning option '-Wno-tautological-constant-compare'; did > > you mean '-Wno-tautological-pointer-compare'? [-Wunknown-warning-option] > > 4 warnings generated. > > > > Does this mean I should be using a different gcc or CFLAGS? > > > > They mostly are: > > > > CFLAGS="-march=native -O2 -pipe" > > > > -- > > Regards, > > Mick > > On my x86 system, I've been seeing similar warnings being generated by > clang when compiling the ffmpeg that comes with chromium. > I've also hit another bug related to that, where clang compilation > terminates with an error message along the lines of there being not > enough registers available. > There's a bug registered for that in chromium bugzilla, which I can't > reference at the moment. So far, no solution has been implemented, as > far as I could tell.
Right, clang's the culprit ... thanks for letting me know. An amd64 system completed the emerge without problems, two others are still chugging along. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
