[Nagiosplug-help] Re: check_mysql cleanup in configure

[Ton Voon]

On 20 Mar 2006, at 12:18, sean finney wrote:

>> I'm going to have to admit ignorance here: why not -rpath? Is it
>> better to use -L?
>
> i can't claim to be an expert on this one either, but yes, i think -L
> would be better in such case (or perhaps nothing at all for debian's
> uses).  it seems the problem with using -rpath in debian is not  
> that it
> necessarily breaks anything but that it causes the program to behave
> differently than others, and bypasses the well defined library search
> path defined by policy/local-adminsitrators.
>
> if you like, i can bounce this issue to some more knowledgable folks
> on debian-devel to get some further insight...

I've committed the change for use of mysql_config. I've also removed  
the one other place I was using -rpath and replaced with -L. It  
appears that libtool replaces -L with -rpath in the gcc linking stage  
- I don't know if this will give you problems, but when I disabled  
the use of libtool, plugins/tests/test_utils would not run correctly  
(could not find the libtap.a library in /usr/local/lib). So I'm  
guessing that we should use -L to find libraries and libtool will  
work out if a run path needs to be added.

>
>> After investigating mysql_config, I think it may be better to switch
>> to that method instead. http://sourceforge.net/tracker/index.php?
>> func=detail&aid=1359414&group_id=29880&atid=397597. But would give
>> similar problems for Debian packages?
>
> yes, i think that would be a better change, and i don't think it would
> give a problem for debian... perhaps we should give that a try?

It is a lot cleaner doing it via mysql_config. One casualty is that -- 
with-mysql is now deprecated.

Any comments on doing the mysql discovery this way?

Ton

http://www.altinity.com
T: +44 (0)870 787 9243
F: +44 (0)845 280 1725
Skype: tonvoon