gearmand 0.22 no longer recognises --libdrizzle-mysql or --libdrizzle_user arguments

Bug #800734 reported by Dave Webb
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Gearman
Invalid
Undecided
Unassigned
gearmand (Ubuntu)
Won't Fix
Undecided
Unassigned

Bug Description

I was trying out the gearmand 0.22, but it failed to start when I used the following commandline (which works on our current version - 0.16):

/opt/gearman/sbin/gearmand \
        --daemon \
        --port=14730 \
        --user=gearmand \
        --log-file=/tmp/new_gearmand_log \
        --queue-type=libdrizzle \
        --libdrizzle-mysql \
        --libdrizzle_user=gearman \
        --libdrizzle-db=gearman_db \
        --libdrizzle-table=gearman_queue -vvvvvv

This failed with the error: "unknown option libdrizzle-mysql".
I removed that argument, and got the error: "unknown option libdrizzle_user".
The same thing happened for --libdrizzle-db and --libdrizzle-table

Has this method of specifying the persistance DB type and location changed? The docs at http://gearman.org/index.php?id=manual:job_server#persistent_queues still mention the previous method (though 0.22 is pretty new).

I think gearmand was built in the standard ./configure && make && make test && make install fashion.

Revision history for this message
Dave Webb (x-launchpad-net-dcw-co-nz) wrote :

After further investigation, I found that ./configure isn't picking up the libdrizzle install now.

Running it like the following worked:

libdrizzle_CFLAGS="-I/usr/local/include" libdrizzle_LIBS="-L/usr/local/lib -ldrizzle" ./configure

This isn't a bug, just me not realising that this new version of gearmand needed different compile flags.

Changed in gearmand:
status: New → Invalid
Revision history for this message
Brian Aker (brianaker) wrote : Re: [Bug 800734] Re: gearmand 0.22 no longer recognises --libdrizzle-mysql or --libdrizzle_user arguments

Sorry about that, let me put a note in the docs about it.

For the most part I am trying to use pkgconfig where available.

On Jun 22, 2011, at 8:21 AM, Dave Webb wrote:

> After further investigation, I found that ./configure isn't picking up
> the libdrizzle install now.
>
> Running it like the following worked:
>
> libdrizzle_CFLAGS="-I/usr/local/include"
> libdrizzle_LIBS="-L/usr/local/lib -ldrizzle" ./configure
>
> This isn't a bug, just me not realising that this new version of
> gearmand needed different compile flags.
>
>
> ** Changed in: gearmand
> Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to
> Gearman.
> https://bugs.launchpad.net/bugs/800734
>
> Title:
> gearmand 0.22 no longer recognises --libdrizzle-mysql or
> --libdrizzle_user arguments
>
> Status in Gearman Server and Client Libraries:
> Invalid
>
> Bug description:
> I was trying out the gearmand 0.22, but it failed to start when I used
> the following commandline (which works on our current version - 0.16):
>
> /opt/gearman/sbin/gearmand \
> --daemon \
> --port=14730 \
> --user=gearmand \
> --log-file=/tmp/new_gearmand_log \
> --queue-type=libdrizzle \
> --libdrizzle-mysql \
> --libdrizzle_user=gearman \
> --libdrizzle-db=gearman_db \
> --libdrizzle-table=gearman_queue -vvvvvv
>
> This failed with the error: "unknown option libdrizzle-mysql".
> I removed that argument, and got the error: "unknown option libdrizzle_user".
> The same thing happened for --libdrizzle-db and --libdrizzle-table
>
> Has this method of specifying the persistance DB type and location
> changed? The docs at
> http://gearman.org/index.php?id=manual:job_server#persistent_queues
> still mention the previous method (though 0.22 is pretty new).
>
> I think gearmand was built in the standard ./configure && make && make
> test && make install fashion.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gearmand/+bug/800734/+subscriptions

Revision history for this message
Dave Webb (x-launchpad-net-dcw-co-nz) wrote :

I got the correct values when running pkg-config directly, so perhaps that process isn't running correctly within ./configure

# pkg-config libdrizzle --libs
-L/usr/local/lib -ldrizzle

# pkg-config libdrizzle --cflags
-I/usr/local/include

Revision history for this message
Dave Webb (x-launchpad-net-dcw-co-nz) wrote :

OK, looking at the configure logs when I'm not passing _CFLAGS or _LIBS, I can see why it's failing. This host has libdrizzle 0.8 installed, and the check is for 1.0.

configure:20150: checking for libdrizzle
configure:20158: $PKG_CONFIG --exists --print-errors " libdrizzle-1.0 >= 2011.03.13 "
Package libdrizzle-1.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libdrizzle-1.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'libdrizzle-1.0' found

As far as I can tell, gearmand is working fine with libdrizzle 0.8, though I'll update to 1.0 and recompile. Thanks for your patience.

Revision history for this message
Razvan Puscasu (razvantim) wrote :

Did anyone manage to install LIBDRIZZLE 1.0 ? I cannot seem to find the sources to compile it. Thanks

Revision history for this message
Dave Webb (x-launchpad-net-dcw-co-nz) wrote :

I managed to get this all going, and wrote down the steps on the question at https://answers.launchpad.net/gearmand/+question/162914

This involved installing drizzle7-devel and libdrizzle7-devel from RPM, then passing flags to ./configure.

Revision history for this message
Guo Chow (guo) wrote :

This problem occurs on ubuntu server 12.04 amd64, where gearmand was installed using apt-get. It seems that the dependency on package libdrizzle-dev is not took into account as well.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

In current versions, libdrizzle is not included, but libmysqlclient functionality is. As such, I think this might be irrelevant.

Changed in gearmand (Ubuntu):
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.