The database.cc function in the current release of bmpx is missing a declaration for "sqlite3_prepare_v2" (used on line 521). This error occurs in the .../work/bmpx-0.40.14/src directory. Reproducible: Always Steps to Reproduce: 1. Attempt to emerge 0.40.14 release of bmpx. Actual Results: Fails to build package. Expected Results: Package should build. USE flags are: USE="hal -debug -doc -modplug -networkmanager -sid -startup-notification"
Created attachment 150054 [details] Copy of error compiling database.cc
emerge --info, and sqlite version?
#bmp, Freenode 16:05 < QuiRK-> hmm, sqlite3_prepare_v2 has been introduced in sqlite 3.3.11 and later 16:06 < QuiRK-> but i think i have bumped sqlite requirements to 3.4 And ebuild deps also >=sqlite-3.4 Something doesn't match here..
Looks like a gcc-4.3 problem. Provide your emerge --info, please. And a more complete build log too, please.
Created attachment 150064 [details] emerge --info output Versions on sqlite indicates that: /dev-db/sqlite-2.8.16-r4 and /dev-db/sqlite-3.5.6 are installed. 3.4.1 and 3.5.3 seem to be available in the portage tree. It is worth noting that there are still a number of "current" packages (php, apr-util, sof, sqlite-ruby-2.2.3-r1, balsa and qt-4.3.2-r1) which appear to depend on the old sqlite-2.8.16-r4.
(In reply to comment #4) > Looks like a gcc-4.3 problem. > > Provide your emerge --info, please. And a more complete build log too, please. > Not sure, builds fine with gcc-4.3 here. 16:10 < milosz> yeah no idea other than what QuiRK said 16:13 < QuiRK-> and i have also checked sqlite3_prepare_v2 has not been removed from sqlite 3.5 Does it help if you remove sqlite 2 temporarily? It might be picking up the wrong version, i.e. bad slotting
Created attachment 150066 [details, diff] Fix attempt Try this
Created attachment 150068 [details] bmpx-0.40.14.ebuild Ebuild using the fix attempt..
Created attachment 150069 [details, diff] Fix attempt #2
Well let me know if any of above worked, might want to also try upgrading to sqlite-3.5.6 which works for me. Actually, it might be the first thing to try. :/
(In reply to comment #10) > Well let me know if any of above worked, might want to also try upgrading to > sqlite-3.5.6 which works for me. Actually, it might be the first thing to try. > :/ > Nevermind, you are using 3.5.6. Both 3.5.3 and 3.5.6 works here, odd. I should be really hitting the same error.
I did not attempt any of the provided fixes. I did unmerge sqlite-2.8.16-r4. After that bmpx would emerge properly. It is necessary to re-emerge sqlite-2.8.16-r4 for sqlite-ruby-2.2.3. It is not clear whether the previously mentioned packages, other than sqlite-ruby actually depend upon sqlite-2.8.16 as they did not show up as being broken when a revdep -r was run (sqlite-ruby did show up as broken). So there may be some kind of a slotting problem.
Petteri, Can you have a look at this? Thanks.
(In reply to comment #14) > I did not attempt any of the provided fixes. > I did unmerge sqlite-2.8.16-r4. After that bmpx would emerge properly. > It is necessary to re-emerge sqlite-2.8.16-r4 for sqlite-ruby-2.2.3. > > It is not clear whether the previously mentioned packages, other than > sqlite-ruby actually depend upon sqlite-2.8.16 as they did not show up as being > broken when a revdep -r was run (sqlite-ruby did show up as broken). > > So there may be some kind of a slotting problem. > I'm closing this as WORKSFORME. I tried just about everything to reproduce this, with both sqlite's installed (also with different versions in each slot). Since it works for you too, now.. Please reopen, if duplicate is received or you can provide more information on howto reproduce.
