[Libdbi-drivers-devel] libdbi-drivers not linked against libdbi themselves

2008-12-09 Thread Martin Sperl
Hi!

 

I have found this bug more than a year ago already, but forgot to
mention it on this list.

Now that rrdtool has gained libdbi-backend support in the latest trunk
version I believe that the need will be higher that this is fixed...

 

The problem is that when calling dbi_driver_open with a valid driver
(e.g: mysql) it works fine when using the rrdtool binary itself, but
when invoking the same command via the PERL binding for RRDTool it
fails.

 

The reason is that in this case some symbols cannot get resolved in this
case.

 

The example output message is:

[EMAIL PROTECTED] SOURCES]# perl rrdtool.test.pl

/usr/lib/dbd/libdbdmysql.so: undefined symbol: _dbd_parse_datetime

libdbi: Failed to load driver: /usr/lib/dbd/libdbdmysql.so

[EMAIL PROTECTED] SOURCES]#

 

The only solution that seems to help is recompiling the drivers with
export LDFLAGS=-ldbi before starting configure.

 

[EMAIL PROTECTED] SPECS]# ldd /usr/lib/dbd/libdbdmysql.so  | grep dbi

[EMAIL PROTECTED] SPECS]# rpm -Uhv
../RPMS/i386/libdbi-dbd-mysql-0.8.1a-1.2.2.i386.rpm  --force

Preparing...###
[100%]

   1:libdbi-dbd-mysql   ###
[100%]

[EMAIL PROTECTED] SPECS]# ldd /usr/lib/dbd/libdbdmysql.so  | grep dbi

libdbi.so.0 = /usr/lib/libdbi.so.0 (0x002d2000)

[EMAIL PROTECTED] SPECS]#

 

[EMAIL PROTECTED] SOURCES]# perl rrdtool.test.pl

[EMAIL PROTECTED] SOURCES]# 

 

So you may want to incorporate this patch that libdbi is linked out of
the box with any future releases of libdbi-drivers...

 

Cheers,

Martin

 

-- 

MARTIN SPERL
Manager, System Engineering
Amdocs Qpass Austria GmbH 

FN 185962 z, Commercial Court Vienna

Neutorgasse 12/1, 1010 Vienna, Austria

+43.1.5326464.708 (desk)
+43.676.6688634 (mobile)
+43.1.5326464.300 (fax)

AMDOCS  CUSTOMER EXPERIENCE SYSTEMS INNOVATION

 


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp
--
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/___
Libdbi-drivers-devel mailing list
Libdbi-drivers-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libdbi-drivers-devel


[Libdbi-drivers-devel] libdbi-drivers not linked against libdbi themselves

2008-12-09 Thread Markus Hoenicka
Hi,

first of all, my apologies for taking care of your message so late,
but it got stuck between tons of spam as you're not subscribed to the
list.

We have received reports aobut similar problems in the past. Our
solution was to link the drivers against libdbi by default. There is
still a switch to toggle this behaviour, but the default has simply
been reversed. This is implemented in the current CVS version, and it
will be widely available as soon as we dare to release 1.0.

regards,
Markus

Martin Sperl writes:
  Hi!
  
   
  
  I have found this bug more than a year ago already, but forgot to
  mention it on this list.
  
  Now that rrdtool has gained libdbi-backend support in the latest trunk
  version I believe that the need will be higher that this is fixed...
  
   
  
  The problem is that when calling dbi_driver_open with a valid driver
  (e.g: mysql) it works fine when using the rrdtool binary itself, but
  when invoking the same command via the PERL binding for RRDTool it
  fails.
  
   
  
  The reason is that in this case some symbols cannot get resolved in this
  case.
  
   
  
  The example output message is:
  
  [EMAIL PROTECTED] SOURCES]# perl rrdtool.test.pl
  
  /usr/lib/dbd/libdbdmysql.so: undefined symbol: _dbd_parse_datetime
  
  libdbi: Failed to load driver: /usr/lib/dbd/libdbdmysql.so
  
  [EMAIL PROTECTED] SOURCES]#
  
   
  
  The only solution that seems to help is recompiling the drivers with
  export LDFLAGS=-ldbi before starting configure.
  
   
  
  [EMAIL PROTECTED] SPECS]# ldd /usr/lib/dbd/libdbdmysql.so  | grep dbi
  
  [EMAIL PROTECTED] SPECS]# rpm -Uhv
  ../RPMS/i386/libdbi-dbd-mysql-0.8.1a-1.2.2.i386.rpm  --force
  
  Preparing...###
  [100%]
  
 1:libdbi-dbd-mysql   ###
  [100%]
  
  [EMAIL PROTECTED] SPECS]# ldd /usr/lib/dbd/libdbdmysql.so  | grep dbi
  
  libdbi.so.0 = /usr/lib/libdbi.so.0 (0x002d2000)
  
  [EMAIL PROTECTED] SPECS]#
  
   
  
  [EMAIL PROTECTED] SOURCES]# perl rrdtool.test.pl
  
  [EMAIL PROTECTED] SOURCES]# 
  
   
  
  So you may want to incorporate this patch that libdbi is linked out of
  the box with any future releases of libdbi-drivers...
  
   
  
  Cheers,
  
  Martin
  
   
  
  -- 
  
  MARTIN SPERL
  Manager, System Engineering
  Amdocs Qpass Austria GmbH 
  
  FN 185962 z, Commercial Court Vienna
  
  Neutorgasse 12/1, 1010 Vienna, Austria
  
  +43.1.5326464.708 (desk)
  +43.676.6688634 (mobile)
  +43.1.5326464.300 (fax)
  
  AMDOCS  CUSTOMER EXPERIENCE SYSTEMS INNOVATION
  
   
  
  
  This message and the information contained herein is proprietary and 
  confidential and subject to the Amdocs policy statement,
  you may review at http://www.amdocs.com/email_disclaimer.asp
  html xmlns:v=urn:schemas-microsoft-com:vml 
  xmlns:o=urn:schemas-microsoft-com:office:office 
  xmlns:w=urn:schemas-microsoft-com:office:word 
  xmlns:x=urn:schemas-microsoft-com:office:excel 
  xmlns:p=urn:schemas-microsoft-com:office:powerpoint 
  xmlns:a=urn:schemas-microsoft-com:office:access 
  xmlns:dt=uuid:C2F41010-65B3-11d1-A29F-00AA00C14882 
  xmlns:s=uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882 
  xmlns:rs=urn:schemas-microsoft-com:rowset xmlns:z=#RowsetSchema 
  xmlns:b=urn:schemas-microsoft-com:office:publisher 
  xmlns:ss=urn:schemas-microsoft-com:office:spreadsheet 
  xmlns:c=urn:schemas-microsoft-com:office:component:spreadsheet 
  xmlns:odc=urn:schemas-microsoft-com:office:odc 
  xmlns:oa=urn:schemas-microsoft-com:office:activation 
  xmlns:html=http://www.w3.org/TR/REC-html40; 
  xmlns:q=http://schemas.xmlsoap.org/soap/envelope/; xmlns:D=DAV: 
  xmlns:x2=http://schemas.microsoft.com/office/excel/2003/xml; 
  xmlns:ois=http://schemas.microsoft.com/sharepoint/soap/ois/; 
  xmlns:dir=http://schemas.microsoft.com/sharepoint/soap/directory/; 
  xmlns:ds=http://www.w3.org/2000/09/xmldsig#; 
  xmlns:dsp=http://schemas.microsoft.com/sharepoint/dsp; 
  xmlns:udc=http://schemas.microsoft.com/data/udc; 
  xmlns:xsd=http://www.w3.org/2001/XMLSchema; 
  xmlns:sub=http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/; 
  xmlns:ec=http://www.w3.org/2001/04/xmlenc#; 
  xmlns:sp=http://schemas.microsoft.com/sharepoint/; 
  xmlns:sps=http://schemas.microsoft.com/sharepoint/soap/; 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; 
  xmlns:udcxf=http://schemas.microsoft.com/data/udc/xmlfile; 
  xmlns:wf=http://schemas.microsoft.com/sharepoint/soap/workflow/; 
  xmlns:mver=http://schemas.openxmlformats.org/markup-compatibility/2006; 
  xmlns:m=http://schemas.microsoft.com/office/2004/12/omml; 
  xmlns:mrels=http://schemas.openxmlformats.org/package/2006/relationships; 
  xmlns:ex12t=http://schemas.microsoft.com/exchange/services/2006/types; 
  xmlns:ex12m=http://schemas.microsoft.com/exchange/services/2006/messages; 
  xmlns:Z=urn:schemas-microsoft-com: xmlns:st=#1; 
  xmlns=http://www.w3.org/TR/REC-html40;
  
  head
  meta