[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ANNOUNCE: usfda-ndc-drug-info v0.4



Andreas writes:

> checking for libxml - version >= 2.0.0... yes (version 2.5.6)
> checking for gawk... gawk
> checking for tr... tr
> checking for cat... cat
> checking how to link against the Berkeley DB C++ library... undefined
> configure: error: could not link against db3

I am unable to duplicate this error even with the 3.2.17 version of
db3. Specifically, I rebuilt from source the files available on:

http://packages.debian.org/testing/libs/libdb3++.html

and this compiles cleanly:

/* x.cpp */
#include <db_cxx.h>
int
main ()
{
  int major, minor, patch_level; 
  DbEnv::version(&major, &minor, &patch_level);
  return 0;
}

with:

    g++ -o conftest -g -O2   x.cpp -ldb3_cxx

which is the test that is failing in your config.log with:

configure:2993: g++ -o conftest -g -O2   conftest.cc -ldb3_cxx >&5
In file included from /usr/include/c++/3.2/backward/iostream.h:31,
                 from /usr/include/db_cxx.h:52,
                 from configure:2975:
/usr/include/c++/3.2/backward/backward_warning.h:32:2: warning: #warning This file includes at least one deprecated or antiquated header. Please consider using one of the 32 headers found in section 17.4.1.2 of the C++ standard. Examples include substituting the <X> header for the <X.h> header for C++ includes, or <sstream> instead of the deprecated header <strstream.h>. To disable this warning use -Wno-deprecated.
/tmp/ccdiGKCY.o(.text+0x17): In function `main':
/home/tillea/debian-maintain/sponsor/lizzy/usfa-ndc-drug-info/usfda-ndc-drug-info-0.4b/configure:2985: undefined reference to `DbEnv::version(int*, int*, int*)'collect2: ld returned 1 exit status
configure:2996: $? = 1

Which doesn't make a whole lot of sense to me as

    DbEnv::version(int*, int*, int*)

is a standard and benign function, unless there is a compatibility
issue between libraries compiled with 2.95 and 3.2.

> This is normally the reason if the orig.tar.gz is missnamed.  A usual
> error is to use '-' instead of '_' before the upstream version number.

That's it!

Thanks for all your help,

Elizabeth



Reply to: