chromium-browser: Outdated in raspbian

Bug #1008327 reported by mpthompson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Raspbian
Fix Released
High
mpthompson

Bug Description

Using advice from Hexxeh, I modified the builds rules to utilize armv6 code, vfp and hard float ABI. However, the package still fails several hours into the build with a syntax error.

Attempting a rebuild of chromium-browser_18.0.1025.151~r130497-1+rpi1 on 6/3/12 and will update the bug base with additional information if the build fails once again.

mpthompson (mpthompson)
Changed in raspbian:
assignee: nobody → mpthompson (mpthompson)
Revision history for this message
mpthompson (mpthompson) wrote :
Download full text (3.7 KiB)

Specific information concerning the compilation problem:

http://archive.raspbian.org/raspbian/logs/main/c/chromium-browser.log

Package: chromium-browser
Version: 18.0.1025.151~r130497-1+rpi1
Source Version: 18.0.1025.151~r130497-1+rpi1
Distribution: testing
Architecture: armhf

...

  CXX(target) out/Release/obj.target/content_renderer/content/renderer/p2p/socket_client.o
  CXX(target) out/Release/obj.target/content_renderer/content/renderer/p2p/socket_dispatcher.o
  CXX(target) out/Release/obj.target/content_renderer/content/renderer/gpu/command_buffer_proxy.o
  CXX(target) out/Release/obj.target/content_renderer/content/renderer/media/media_stream_dependency_factory_stub.o
content/renderer/media/media_stream_dependency_factory_stub.cc:11:1: error: 'WebRtcMediaEngine' in namespace 'cricket' does not name a type
content/renderer/media/media_stream_dependency_factory_stub.cc:17:14: error: 'bool MediaStreamDependencyFactory::CreatePeerConnectionFactory' is not a static member of 'class MediaStreamDependencyFactory'
content/renderer/media/media_stream_dependency_factory_stub.cc:17:5: error: 'MediaEngineInterface' is not a member of 'cricket'
content/renderer/media/media_stream_dependency_factory_stub.cc:17:36: error: 'media_engine' was not declared in this scope
content/renderer/media/media_stream_dependency_factory_stub.cc:18:22: error: expected primary-expression before '*' token
content/renderer/media/media_stream_dependency_factory_stub.cc:18:24: error: 'worker_thread' was not declared in this scope
content/renderer/media/media_stream_dependency_factory_stub.cc:18:37: error: expression list treated as compound expression in initializer [-fpermissive]
content/renderer/media/media_stream_dependency_factory_stub.cc:18:39: error: expected ',' or ';' before '{' token
content/renderer/media/media_stream_dependency_factory_stub.cc:22:64: error: no 'void MediaStreamDependencyFactory::DeletePeerConnectionFactory()' member function declared in class 'MediaStreamDependencyFactory'
content/renderer/media/media_stream_dependency_factory_stub.cc:33:52: error: no 'cricket::PortAllocator* MediaStreamDependencyFactory::CreatePortAllocator(content::P2PSocketDispatcher*, talk_base::NetworkManager*, talk_base::PacketSocketFactory*, const webkit_glue::P2PTransport::Config&)' member function declared in class 'MediaStreamDependencyFactory'
content/renderer/media/media_stream_dependency_factory_stub.cc:37:25: error: prototype for 'webrtc::PeerConnection* MediaStreamDependencyFactory::CreatePeerConnection(cricket::PortAllocator*, talk_base::Thread*)' does not match any in class 'MediaStreamDependencyFactory'
./content/renderer/media/media_stream_dependency_factory.h:57:7: error: candidate is: virtual talk_base::scoped_refptr<webrtc::PeerConnectionInterface> MediaStreamDependencyFactory::CreatePeerConnection(const string&, webrtc::PeerConnectionObserver*)
make[1]: *** [out/Release/obj.target/content_renderer/content/renderer/media/media_stream_dependency_factory_stub.o] Error 1
make[1]: Leaving directory `/«PKGBUILDDIR»/src'
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2
──────────────────...

Read more...

Revision history for this message
peter green (plugwash) wrote :

We now have a chromium package in raspbian but it is a couple of versions out of date. Trying to upgrade but running into problems with linker bugs (with gold) and address space exhaustion (with bfd)

summary: - chromium-browser: FTBFS in Raspbian
+ chromium-browser: Outdated in raspbian
Revision history for this message
peter green (plugwash) wrote :

We are now in sync with debian on chromium version.

Changed in raspbian:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.