I downloaded the sane cvs and compiled the front-ends and they compiled
fine. What changes were necessary between RH6.2 Gnome and the latest
from Helix? Can I expect other progs to have runtime/compiling
difficulties because they were geared towards an older Gnome? How can I
avoid/fix these problems?
Mike
Michael Vanecek wrote:
>
> I compiled sane under the old stock RH6.2 Gnome with no problems, but
> last night I upgraded to the latest Helix-Gnome and installed everything
> they had to download. Now when I go to recompile sane, when it gets to
> xscanimage, it spits out a ton of warnings and then craters.
> Here is a list of the warnings I get when xscanimage starts to compile:
>
> gcc -c -DHAVE_CONFIG_H -I. -I. -I../include -I../include
> -I/usr/local/include
> -I/usr/lib/glib/include -I/usr/X11R6/include -D_GNU_SOURCE
> -DPATH_SANE_CONFIG_DIR=/etc/sane.d
> -DPATH_SANE_DATA_DIR=/usr/share -DV_MAJOR=1 -DV_MINOR=0 -O2
> -m486 -fno-strength-reduce -W
> -Wall -DSCSIBUFFERSIZE=131072 xscanimage.c
> xscanimage.c:63: parse error before `GParam'
> xscanimage.c:66: parse error before `PLUG_IN_INFO'
~snipped~
> xscanimage.c:239: warning: `nargs' defined but not used
> make[1]: *** [xscanimage.o] Error 1
> make[1]: Leaving directory `/usr/src/redhat/BUILD/sane-1.0.3/frontend'
> make: *** [all-recursive] Error 1
> Bad exit status from /var/tmp/rpm-tmp.30359 (%build)
> [root@Linux SPECS]#
>
> Any ideas? I've run ldconfig a few times. I had to get Xsane 0.64
> because 0.61 also cratered. 0.64 compiled fine.
>
> Mike
>
> _______________________________________________
> gnome-list mailing list
> gnome-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/gnome-list
-- Source code, list archive, and docs: http://www.mostang.com/sane/ To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
This archive was generated by hypermail 2b29 : Sat Nov 18 2000 - 20:59:27 PST