Hmm, I didn't realize that it was a high priority to get this fixed in
1.0.9 (as Henning pointed out, it's been in since 1.0.5)
However, if it needs to be fixed and the choices are
1) Disable the backend in configure.in for non-gcc platforms
2) Submit the portable code
Option 2) sounds the lower risk to me. Shall I go ahead and do that?
It seems that CVS is still down. How far is the code freeze going
to move?
--
Peter Fales Lucent Technologies, Room 1C-436
N9IYJ 2000 N Naperville Rd PO Box 3033
internet: psfa...@lucent.com Naperville, IL 60566-7033
work: (630) 979-8031
On Mon, Oct 14, 2002 at 03:53:18PM +0200, Petter Reinholdtsen wrote:
> [Peter Fales]
> > The new code seems to work OK, but I don't think it's a good idea to
> > submit it just before the 1.0.9 code freeze. I'll commit the CVS
> > changes to the next release.
>
> Then you will need to fix configure.in to skip this backend on all
> non-gcc, non-little endian platforms to avoid compile errors on all
> these platforms.
> _______________________________________________
> Sane-devel mailing list
> sane-de...@www.mostang.com
> http://www.mostang.com/mailman/listinfo/sane-devel
