Summary: | www-client/chromium-22.0.1207.1 fails in libc_urandom_override.cc w/gcc-4.7 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | crabbed halo ablution <crabbedhaloablution> |
Component: | Current packages | Assignee: | Chromium Project <chromium> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | matrix47 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://code.google.com/p/chromium/issues/detail?id=137437 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 412615 | ||
Attachments: |
fix missing unistd.h file
XPathGrammar.h header |
Description
crabbed halo ablution
2012-07-19 18:56:38 UTC
Could someone post a patch for this? Or should I wait for next dev release? Thanks Created attachment 318680 [details] fix missing unistd.h file please use attached patch, and test you can leverage user patches # mkdir -p /etc/portage/patches//www-client/chromium-22.0.1207.1 # cp chromium-header-fix.patch /etc/portage/patches//www-client/chromium-22.0.1207.1 # emerge =chromium-22.0.1207.1 (In reply to comment #1) > Could someone post a patch for this? Or should I wait for next dev release? > > Thanks While the patch provided above does allow the build to progress it later fails with the following error: third_party/WebKit/Source/WebCore/xml/XPathParser.cpp: In member function 'WebCore::XPath::Expression* WebCore::XPath::Parser::parseStatement(const WTF::String&, WTF::PassRefPtr<WebCore::XPathNSResolver>, WebCore::ExceptionCode&)': third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:478:39: error: too many arguments to function 'int WebCore::XPath::xpathyyparse()' In file included from third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:49:0: /var/tmp/portage/www-client/chromium-22.0.1207.1/work/chromium-22.0.1207.1/out/Release/obj/gen/webkit/XPathGrammar.hpp:108:5: note: declared here make: *** [out/Release/obj.target/webcore_remaining/third_party/WebKit/Source/WebCore/xml/XPathParser.o] Error 1 make: *** Waiting for unfinished jobs.... I'm using gcc 4.7.1 this is no problem with 4.7.1, works here (In reply to comment #3) > While the patch provided above does allow the build to progress it later > fails with the following error: > > third_party/WebKit/Source/WebCore/xml/XPathParser.cpp: In member function > 'WebCore::XPath::Expression* WebCore::XPath::Parser::parseStatement(const > WTF::String&, WTF::PassRefPtr<WebCore::XPathNSResolver>, > WebCore::ExceptionCode&)': > third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:478:39: error: too > many arguments to function 'int WebCore::XPath::xpathyyparse()' this function defined in the code, should have no problem > In file included from > third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:49:0: > /var/tmp/portage/www-client/chromium-22.0.1207.1/work/chromium-22.0.1207.1/ > out/Release/obj/gen/webkit/XPathGrammar.hpp:108:5: note: declared here could you attach this file? > make: *** > [out/Release/obj.target/webcore_remaining/third_party/WebKit/Source/WebCore/ > xml/XPathParser.o] Error 1 > make: *** Waiting for unfinished jobs.... > > I'm using gcc 4.7.1 (In reply to comment #4) > > In file included from > > third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:49:0: > > /var/tmp/portage/www-client/chromium-22.0.1207.1/work/chromium-22.0.1207.1/ > > out/Release/obj/gen/webkit/XPathGrammar.hpp:108:5: note: declared here > > could you attach this file? I'm afraid I can't, there's no such file left after the build fails: ls: cannot access /var/tmp/portage/www-client/chromium-22.0.1207.1/work/chromium-22.0.1207.1/out/Release/obj/gen/webkit/XPathGrammar.hpp: No such file or directory Created attachment 318780 [details]
XPathGrammar.h header
Yes, XPathGrammar.hpp will be deleted,
its aim is to generate XPathGrammar.h
work/chromium-22.0.1207.1/out/Release/obj/gen/webkit/XPathGrammar.h
could you try to compare with mine? see attached file
btw, My yacc compile : sys-devel/bison-2.5.1
I have just tried the patch "chromium-header-fix.patch" but I get this error: In file included from third_party/WebKit/Source/WTF/wtf/OwnPtr.h:25:0, from third_party/WebKit/Source/WTF/wtf/RefCounted.h:27, from third_party/WebKit/Source/WebCore/dom/EventListener.h:24, from third_party/WebKit/Source/WebCore/dom/RegisteredEventListener.h:27, from third_party/WebKit/Source/WebCore/dom/EventListenerMap.h:36, from third_party/WebKit/Source/WebCore/dom/EventTarget.h:35, from third_party/WebKit/Source/WebCore/dom/Node.h:29, from third_party/WebKit/Source/WebCore/xml/XPathStep.h:30, from third_party/WebKit/Source/WebCore/xml/XPathParser.h:30, from third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:29: third_party/WebKit/Source/WTF/wtf/NullPtr.h:52:1: warning: identifier ‘nullptr’ is a keyword in C++11 [-Wc++0x-compat] third_party/WebKit/Source/WebCore/xml/XPathParser.cpp: In member function ‘WebCore::XPath::Expression* WebCore::XPath::Parser::parseStatement(const WTF::String&, WTF::PassRefPtr<WebCore::XPathNSResolver>, WebCore::ExceptionCode&)’: third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:478:39: error: too many arguments to function ‘int WebCore::XPath::xpathyyparse()’ In file included from third_party/WebKit/Source/WebCore/xml/XPathParser.cpp:49:0: /media/Test/portagehd/portage/www-client/chromium-22.0.1207.1-r1/work/chromium-22.0.1207.1/out/Release/obj/gen/webkit/XPathGrammar.hpp:108:5: note: declared here make: *** [out/Release/obj.target/webcore_remaining/third_party/WebKit/Source/WebCore/xml/XPathParser.o] Errore 1 make: *** Attesa dei processi non terminati.... (In reply to comment #7) That is bug 427438. (In reply to comment #8) > (In reply to comment #7) > > That is bug 427438. I can confirm that by downgrading to sys-devel/bison-2.5.1 Chromium 22.0.1207.1 was merge successfully with the patch provided in an earlier comment. (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > > That is bug 427438. > > I can confirm that by downgrading to sys-devel/bison-2.5.1 Chromium > 22.0.1207.1 was merge successfully with the patch provided in an earlier > comment. So do I confirm this Is this in an overlay - I'm feeling very lazy tonight this bug (comment #1) still exist on chromium-22.0.1215.0.ebuild , also see my comments to bug 427438 , I think it's should more convenient to comment here Fixed in chromium-22.0.1221.1. |