Thanks for reply. I have discussed this issue on IRC and my issue is solved.
What I was doing wrong ---------------------------------- I compiled the code just before the installation of gperf. Installing of gperf does not solve the issue. What Solved the problem ------------------------------------ After installing gperf, I delete Debug directories and resync with --force option and compile whole code again. On Mon, Jun 22, 2009 at 8:40 AM, Lei Zhang <[email protected]> wrote: > You need to give more info. What revision of the source code are you > at? Did you make any local changes? > > FWIW, we have a Jaunty build bot on the experimental waterfall and it built > ok. > > http://build.chromium.org/buildbot/waterfall.fyi/builders/Chromium%20Linux%20(Jaunty)/builds/1981<http://build.chromium.org/buildbot/waterfall.fyi/builders/Chromium%20Linux%20%28Jaunty%29/builds/1981> > > On Mon, Jun 22, 2009 at 5:00 AM, Ibrar Ahmed<[email protected]> wrote: > > Hi, > > > > I am getting error while compiling on ubuntu 9.04 (64bit) > > > > > /home/ibrar/Google/chromium/src/third_party/WebKit/WebCore/css/CSSParser.cpp: > > In function 'int WebCore::cssValueKeywordID(const > > WebCore::CSSParserString&)': > > > /home/ibrar/Google/chromium/src/third_party/WebKit/WebCore/css/CSSParser.cpp:4947: > > error: expected initializer before '*' token > > > /home/ibrar/Google/chromium/src/third_party/WebKit/WebCore/css/CSSParser.cpp:4948: > > error: 'hashTableEntry' was not declared in this scope > > Compiling > > > /home/ibrar/Google/chromium/src/sconsbuild/Debug/obj/third_party/WebKit/WebCore/css/CSSPropertyLonghand.o > > scons: *** > > > [/home/ibrar/Google/chromium/src/sconsbuild/Debug/obj/third_party/WebKit/WebCore/css/CSSParser.o] > > Error 1 > > scons: building terminated because of errors. > > > > > > > > > > > > > > > > On Sat, Jun 20, 2009 at 4:45 AM, Hunnter2k3 <[email protected]> wrote: > >> > >> Ever since V2 has been pushed, the CPU usage for Chrome has sky- > >> rocketed every time i am loading pages. > >> Every time a page is loading, both cores are hitting 100%. > >> Worse is when sites are lagging or slow, the CPU is still at 100% > >> until it is finished, no ifs or buts. > >> > >> I even done a fresh install, I even installed SRWare's Iron, it still > >> hits 100% when a page loads. > >> > >> If this is what V2 is going to be like, i am going straight back to > >> V1, i don't want a browser eating 100% and interrupting other > >> processes, especially if it is because of a feature i couldn't care > >> less about. > >> > >> Is this what has happened to Full Page Zoom now, instead of generating > >> it each time a person wants to zoom? > >> If so, for the love of everything decent, please go back to the old > >> system, i don't care for FPZ and never will, or at least start using > >> that wonderful thing called Options and add it in there, please. > >> > >> > > > > > > > > -- > > Ibrar Ahmed > > > > > > > > > > > > > -- Ibrar Ahmed --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
