Bug 269094 – sqlite-3.6.14: emerge fails due to configure script being out of date

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description DaggyStyle 2009-05-09 07:37:19 UTC]

here is the output:
>>> Emerging (1 of 1) dev-db/sqlite-3.6.14
 * sqlite-3.6.14.tar.gz RMD160 SHA1 SHA256 size ;-) ...                [ ok ]
 * checking ebuild checksums ;-) ...                                   [ ok ]
 * checking auxfile checksums ;-) ...                                  [ ok ]
 * checking miscfile checksums ;-) ...                                 [ ok ]
>>> Unpacking source...                                                      
>>> Unpacking sqlite-3.6.14.tar.gz to /var/tmp/portage/dev-db/sqlite-3.6.14/work                                                                            
 * Applying sandbox-fix2.patch ...                                      [ ok ]
 * Removing useless C++ checks ...                                      [ ok ]
>>> Source unpacked in /var/tmp/portage/dev-db/sqlite-3.6.14/work             
>>> Compiling source in /var/tmp/portage/dev-db/sqlite-3.6.14/work/sqlite-3.6.14 ...                                                                        
 * econf: updating sqlite-3.6.14/config.guess with /usr/share/gnuconfig/config.guess                                                                        
 * econf: updating sqlite-3.6.14/config.sub with /usr/share/gnuconfig/config.sub                                                                            
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --disable-debug --enable-threadsafe --enable-cross-thread-connections --disable-tcl              
configure: error: configure script is out of date:                            
 configure $PACKAGE_VERSION = 3.6.13                                          
 top level VERSION file     = 3.6.14                                          
please regen with autoconf                                                    

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/dev-db/sqlite-3.6.14/work/sqlite-3.6.14/config.log
 *                                                                     
 * ERROR: dev-db/sqlite-3.6.14 failed.                                 
 * Call stack:                                                         
 *               ebuild.sh, line   48:  Called src_compile             
 *             environment, line 2838:  Called econf '--disable-debug' '--enable-threadsafe' '--enable-cross-thread-connections' '--disable-tcl'            
 *               ebuild.sh, line  525:  Called die                            
 * The specific snippet of code:                                              
 *                      die "econf failed"                                    
 *  The die message:                                                          
 *   econf failed                                                             
 *                                                                            
 * If you need support, post the topmost build error, and the call stack if relevant.                                                                       
 * A complete build log is located at '/var/tmp/portage/dev-db/sqlite-3.6.14/temp/build.log'.                                                               
 * The ebuild environment file is located at '/var/tmp/portage/dev-db/sqlite-3.6.14/temp/environment'.                                                      
 *                                                                            

>>> Failed to emerge dev-db/sqlite-3.6.14, Log file:

>>>  '/var/tmp/portage/dev-db/sqlite-3.6.14/temp/build.log'

/var/tmp/portage/dev-db/sqlite-3.6.14/work/sqlite-3.6.14/config.log is attached.


Reproducible: Always

[Comment 1 DaggyStyle 2009-05-09 07:39:03 UTC]

Created attachment 190730 [details]
file's error log

[Comment 2 Lars Wendler (Polynomial-C) (RETIRED) 2009-05-09 07:43:37 UTC]

*** This bug has been marked as a duplicate of bug 269075 ***