Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Misc Size-Medium Type-Bug

New issue 22208 by [email protected]: Compilation broken with  
use_system_sqlite=1
http://code.google.com/p/chromium/issues/detail?id=22208

Chrome Version       : 4.0.212 svn r26343
OS + version : Gentoo
CPU architecture (32-bit / 64-bit): both

What steps will reproduce the problem?
Run gyp_chromium -f make build/all.gyp with -Duse_system_sqlite=1

What is the expected result?
Compilation completes successfully

What happens instead?
On final linking:
out/Release/obj/app/libapp_base.a(connection.o): In function
`sql::Connection::Preload()':
connection.cc:(.text._ZN3sql10Connection7PreloadEv+0xcb): undefined
reference to `sqlite3Preload'
out/Release/obj/webkit/libwebcore.a(SQLiteFileSystemChromiumPosix.o): In
function `(anonymous namespace)::chromiumOpen(sqlite3_vfs*, char const*,
sqlite3_file*, int, int*)':
SQLiteFileSystemChromiumPosix.cpp:(.text._ZN12_GLOBAL__N_112chromiumOpenEP11sqlite3_vfsPKcP12sqlite3_fileiPi+0x3a):
undefined reference to `initUnixFile'
SQLiteFileSystemChromiumPosix.cpp:(.text._ZN12_GLOBAL__N_112chromiumOpenEP11sqlite3_vfsPKcP12sqlite3_fileiPi+0xfd):
undefined reference to `fillInUnixFile'

 From README.chromium these 3 functions are indeed new or modified from
upstream sqlite, but as they are mangled in the upstream code, compilation
fails when enabling use_system_sqlite (which disables compilation of
modified files, like os_unix.c)

I'd like to provide a patch splitting/renaming these functions somewhere
eles in chromium code (should be easy, for example initUnixFile() is just a
one-liner call to memset()), but I don't know the coding guidelines that
apply in this case

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---

Reply via email to