Re: [concordance-devel] concordance failure on new ubuntu
Marc Williams wrote:
Stephen Warren wrote:
Marc Williams wrote:
Thanks, but neither the install_policykit nor the install udev worked (I
didn't try the 3rd one). What did work though was this:
echo 'SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=666'
|sudo tee /etc/udev/rules.d/custom-concordance.rules
That's essentially what make install_dev should do for you. I just
tested it on Jaunty 32-bit, and it worked fine for me.
Did you configure libconcord with a non-standard prefix? If so, the
makefile will install the udev policy in the wrong place. Perhaps you
can just run make install_udev again, and paste the output here?
Nope. Just ran it from the libconcord dir. (This is 64bit Jaunty).
However, I noticed that it installed the rule into
/usr/local/etc/udev/rules.d. I'm pretty sure that nothing is going to
find it there:
I've made reference to this in the bug you filed, but just for the record,
you can fix this with
./configure --sysconfigdir=/etc --rootdatadir=/usr/share
*or*
./configure --prefix=/usr
The later will install the binaries in /usr/bin and the libraries in
/usr/lib potentially conflicting with system-installed packages, FYI.
--
Phil Dibowitz p...@ipom.com
Open Source software and tech docsInsanity Palace of Metallica
http://www.phildev.net/ http://www.ipom.com/
Never write it in C if you can do it in 'awk';
Never do it in 'awk' if 'sed' can handle it;
Never use 'sed' when 'tr' can do the job;
Never invoke 'tr' when 'cat' is sufficient;
Avoid using 'cat' whenever possible -- Taylor's Laws of Programming
signature.asc
Description: OpenPGP digital signature
--
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] concordance failure on new ubuntu
Stephen Warren wrote:
Marc Williams wrote:
Thanks, but neither the install_policykit nor the install udev worked (I
didn't try the 3rd one). What did work though was this:
echo 'SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=666'
|sudo tee /etc/udev/rules.d/custom-concordance.rules
That's essentially what make install_dev should do for you. I just
tested it on Jaunty 32-bit, and it worked fine for me.
Did you configure libconcord with a non-standard prefix? If so, the
makefile will install the udev policy in the wrong place. Perhaps you
can just run make install_udev again, and paste the output here?
Nope. Just ran it from the libconcord dir. (This is 64bit Jaunty).
However, I noticed that it installed the rule into
/usr/local/etc/udev/rules.d. I'm pretty sure that nothing is going to
find it there:
ma...@marcw-desk:~/source/concordance-0.21/libconcord$ sudo make
install_udev
[sudo] password for marcw:
./gen_udev_support -u
Creating udev file: libconcord.rules ... done
/bin/mkdir -p /usr/local/etc/udev/rules.d
/bin/sh /home/marcw/source/concordance-0.21/libconcord/install-sh -c -m
644 libconcord.rules \
/usr/local/etc/udev/rules.d/99-libconcord.rules
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] concordance failure on new ubuntu
Thanks, but neither the install_policykit nor the install udev worked (I
didn't try the 3rd one). What did work though was this:
echo 'SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=666'
|sudo tee /etc/udev/rules.d/custom-concordance.rules
Phil Dibowitz wrote:
On Tue, May 05, 2009 at 11:54:13AM +0200, Jack van Hemmen wrote:
Thanks.
Sure. Let me know how that works for you. It's new code.
Hopefully the upcoming debian (and subsequently ubuntu) package should make
this a non-issue.
I need to follow up again with the guys packaging it...
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] concordance failure on new ubuntu
Marc Williams wrote:
Thanks, but neither the install_policykit nor the install udev worked (I
didn't try the 3rd one). What did work though was this:
echo 'SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=666'
|sudo tee /etc/udev/rules.d/custom-concordance.rules
That's essentially what make install_dev should do for you. I just
tested it on Jaunty 32-bit, and it worked fine for me.
Did you configure libconcord with a non-standard prefix? If so, the
makefile will install the udev policy in the wrong place. Perhaps you
can just run make install_udev again, and paste the output here?
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
Re: [concordance-devel] concordance failure on new ubuntu
Marc Williams wrote:
Thanks, but neither the install_policykit nor the install udev worked (I
didn't try the 3rd one). What did work though was this:
echo 'SYSFS{idVendor}==046d, SYSFS{idProduct}==c111, MODE=666'
|sudo tee /etc/udev/rules.d/custom-concordance.rules
That's essentially what make install_dev should do for you. I just
tested it on Jaunty 32-bit, and it worked fine for me.
Did you configure libconcord with a non-standard prefix? If so, the
makefile will install the udev policy in the wrong place. Perhaps you
can just run make install_udev again, and paste the output here?
--
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
___
concordance-devel mailing list
concordance-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/concordance-devel
