[sane-devel] SANE source compilation problems
Hello, On Apr 26 12:28 Julien BLACHE wrote (shortened): Speaking of resmgr, I think we can safely remove any code using it. I doubt it's still in use in SuSE... I'd be very surprised if it was. We (i.e. openSUSE/Novell) do no longer use resmgr inside SANE since a longer time. If no one else uses resmgr inside SANE, all resmgr related code could be completely removed from SANE. FYI: Our sane-backends RPM changelog contains: * Mon Sep 11 2006 jsmeix at suse.de - disable-resmgr-support.patch disables the resmgr support in SANE which is no longer needed in SANE because resmgr works now outside of SANE via ACLs for the scanner device nodes. And our disable-resmgr-support.patch is (too long lines are shown wrapped here): --- configure.in.orig +++ configure.in @@ -155,15 +155,21 @@ AC_CHECK_HEADERS([asm/io.h],,,[#include SANE_CHECK_MISSING_HEADERS -AC_CHECK_HEADER(resmgr.h,[ - AC_CHECK_LIB( - resmgr, - rsm_open_device,[ - AC_DEFINE(HAVE_RESMGR,1,[define if you have the resmgr library]) - LIBS=$LIBS -lresmgr - ] - ) -]) +# Since Suse Linux 10.0 resmgr installs ACLs on device nodes. +# Therefore there is no need to patch applications with special resmgr +# support anymore. +# As the rsm_open_device calls in sanei_scsi.c and sanei_usb.c +# are optionally via ifdef HAVE_RESMGR with fallback open calls, +# the special resmgr support is not removed but only disabled here: +#AC_CHECK_HEADER(resmgr.h,[ +# AC_CHECK_LIB( +# resmgr, +# rsm_open_device,[ +# AC_DEFINE(HAVE_RESMGR,1,[define if you have the resmgr library]) +# LIBS=$LIBS -lresmgr +# ] +# ) +#]) Mad world: I added a patch to get rid of those stuff which was initially introduced by us. By the way: Some time ago resmgr was completely replaced by a HAL-based stuff but now HAL will be dropped (because HAL is declared deprecated) so that the HAL-based stuff was already in advance replaced by a udev-based stuff (of course until this will be replaced by whatever future completely-new-and-better-than-anything-else-stuff ;-) Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex
[sane-devel] SANE source compilation problems
On Tue, Apr 27, 2010 at 4:40 AM, Johannes Meixner jsmeix at suse.de wrote: Mad world: I added a patch to get rid of those stuff which was initially introduced by us. How do you think we feel? :) And no, I don't want to contemplate what comes after udev allan -- The truth is an offense, but not a sin
[sane-devel] SANE source compilation problems
Ok Chris- kill resmgr at your earliest convenience. allan -- The truth is an offense, but not a sin
[sane-devel] SANE source compilation problems
m. allan noah kitno455 at gmail.com wrote: How do you think we feel? :) And no, I don't want to contemplate what comes after udev You should, really. Never miss a good laugh, there aren't so many in this world... JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] SANE source compilation problems
Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1 -lm -ltiff -ljpeg -lgphoto2 -lgphoto2_port -lexif -lm -lusb -lusb @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS at unreplaced with some text after sane-backends make install? Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? Best regards, Ilmars Poikans -- next part -- An HTML attachment was scrubbed... URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100425/702503ff/attachment.htm
[sane-devel] SANE source compilation problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ilm?rs Poik?ns : Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1 -lm -ltiff -ljpeg -lgphoto2 -lgphoto2_port -lexif -lm -lusb -lusb @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS at unreplaced with some text after sane-backends make install? No, something like @REGMGR_LIBS@ is normally replaced after ./configure. Without looking at any of the code, I suspect a typo. My guess is that it should be @RESMGR_LIBS at . Just checked, it's been fixed already. ;-) Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? SANE_STATUS_WARMING_UP is one of the statusses that has been considered for addition to the API. IIRC, sane-backends-1.0.21 would ship without any API changes (and the #if 0 indicates that it will), so it appears you have found a bug in scanadf.c. Hope this helps, - -- Olaf Meeuwissen, LPIC-2 FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkvU1hcACgkQt5qrxaZLMnKo/gCeOP7Bbkd/KWKUptcDTOVvnjIe fiwAn1KgvMMvpK+k3hpBVbXG83tWFPzQ =Ah98 -END PGP SIGNATURE-
[sane-devel] SANE source compilation problems
On Mon, Apr 26, 2010 at 2:53 AM, Olaf Meeuwissen olaf.meeuwissen at avasys.jp wrote: SANE_STATUS_WARMING_UP is one of the statusses that has been considered for addition to the API. ?IIRC, sane-backends-1.0.21 would ship without any API changes (and the #if 0 indicates that it will), so it appears you have found a bug in scanadf.c. Isn't it better to have one switch like SANE_API_2 in sane.h instead of two #if 0 (See patch to current git master in attachment)? Then there is flexibility to switch on new features with one #define in code or by passing argument to gcc. WIth those changes old sane-frontends compiles successfully (except you need to either add #define SANE_API_2 1 to scanadf.c or pass additional argument when compiling during make). Best regards, Ilmars Poikans -- next part -- A non-text attachment was scrubbed... Name: patch-header.patch Type: text/x-patch Size: 2834 bytes Desc: not available URL: http://lists.alioth.debian.org/pipermail/sane-devel/attachments/20100426/6c5c0a18/attachment.bin
[sane-devel] SANE source compilation problems
Chris Bagwell chris at cnpbagwell.com wrote: Hi, Others have replied about the remaining issues once @RESMGR@ typo is Speaking of resmgr, I think we can safely remove any code using it. I doubt it's still in use in SuSE... I'd be very surprised if it was. JB. -- Julien BLACHE http://www.jblache.org jb at jblache.org GPG KeyID 0xF5D65169
[sane-devel] SANE source compilation problems
On Mon, Apr 26, 2010 at 5:28 AM, Julien BLACHE jb at jblache.org wrote: Chris Bagwell chris at cnpbagwell.com wrote: Hi, Others have replied about the remaining issues once @RESMGR@ typo is Speaking of resmgr, I think we can safely remove any code using it. I doubt it's still in use in SuSE... I'd be very surprised if it was. If no one else objects, I'll happily remove it from Makefiles and source code. That is unless someone else prefers doing it. Chris
[sane-devel] SANE source compilation problems
When was the last version of suse that used it replaced? If more than two years, kill it. allan On Mon, Apr 26, 2010 at 3:52 PM, Chris Bagwell chris at cnpbagwell.com wrote: On Mon, Apr 26, 2010 at 5:28 AM, Julien BLACHE jb at jblache.org wrote: Chris Bagwell chris at cnpbagwell.com wrote: Hi, Others have replied about the remaining issues once @RESMGR@ typo is Speaking of resmgr, I think we can safely remove any code using it. I doubt it's still in use in SuSE... I'd be very surprised if it was. If no one else objects, I'll happily remove it from Makefiles and source code. ?That is unless someone else prefers doing it. Chris -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] SANE source compilation problems
http://gitorious.org/opensuse/resmgr says resmgr was removed in 11.0. distrowatch.com says openSUSE 11.0 was released 2008-06-19. We are couple months shy of 2 years. By time next sane release it will be well over 2 years. :) Opinions? I'll put it on my slw track for now. Chris On Mon, Apr 26, 2010 at 3:04 PM, m. allan noah kitno455 at gmail.com wrote: When was the last version of suse that used it replaced? If more than two years, kill it. allan On Mon, Apr 26, 2010 at 3:52 PM, Chris Bagwell chris at cnpbagwell.com wrote: On Mon, Apr 26, 2010 at 5:28 AM, Julien BLACHE jb at jblache.org wrote: Chris Bagwell chris at cnpbagwell.com wrote: Hi, Others have replied about the remaining issues once @RESMGR@ typo is Speaking of resmgr, I think we can safely remove any code using it. I doubt it's still in use in SuSE... I'd be very surprised if it was. If no one else objects, I'll happily remove it from Makefiles and source code. ?That is unless someone else prefers doing it. Chris -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] SANE source compilation problems
you dont need to compile sane-frontends from devel source. use the last release, or skip it entirely. scanimage can do most things scanadf can, and the other programs in sane-frontends are not actively developed. allan On Sun, Apr 25, 2010 at 4:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS@ unreplaced with some text after sane-backends make install? Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? Best regards, Ilmars Poikans -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org -- The truth is an offense, but not a sin
[sane-devel] SANE source compilation problems
It should compile fine in Ubuntu/Debian Make sure you have these pkgs before you configure: build-essential libusb-dev Cheers, Alejandro Imass On Sun, Apr 25, 2010 at 4:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. So, my first question - Is it normal to have something like @REGMGR_LIBS@ unreplaced with some text after sane-backends make install? Then I got to second problem while making sane-frontends - compiling scanadf.c failed, make reported error: scanadf.c:995: error: ?SANE_STATUS_WARMING_UP? undeclared (first use in this function) Source for SANE_STATUS_WARNING_UP undeclared problem was in /usr/local/include/sane/sane.h (installed by make install in sane-backends) on line 74. Missing define is deactivated with #if 0 line above. When I changed #if 0 to #if 1 and enabled following two #define declarations, sane-frontends make was successful finally. Is it supposed to be so, that user needs to manually change something in installed files to make sane successfully? Or I found a feature or bug? Best regards, Ilmars Poikans -- sane-devel mailing list: sane-devel at lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject unsubscribe your_password ? ? ? ? ? ? to sane-devel-request at lists.alioth.debian.org
[sane-devel] SANE source compilation problems
On Sun, Apr 25, 2010 at 3:25 PM, Ilm?rs Poik?ns ilmars at delibero.lv wrote: Hi, I downloaded source from git repositories (sane-backends and sane-frontends) and tired to compile them. I have Ubuntu 9.10, needed dev library packages were there. sane-backends configure, make, make install was fine. sane-frontends configure failed. I traced problem down to /user/local/bin/sane-config having line: LIBS= -ldl -lv4l1?? -lm -ltiff -ljpeg? -lgphoto2 -lgphoto2_port -lexif -lm -lusb?? -lusb? @REGMGR_LIBS@ When I deleted @REGMGR_LIBS@ from that line, then sane-frontends configure run successfully. I didn't care about graphical frontends, so configure disabled GUI. Previously gcc tried to find that file and failed to compile some tests. This part was my fault. I recently fixed oen sane-config bug and introduced another. I've just submitted a fix so if you re-pulled sane-backends from git and reinstall, this part of the problem should go away. Others have replied about the remaining issues once @RESMGR@ typo is fixed. sane-frontend in current git contains some next generation API's that sane-backends has disabled. The released sane-frontends package is the one to use with released and git versions of sane-backends. Chris
