When trying to build sane-backends in Mac OS X on an Intel iMac, I ran
into a problem (see below). It appears that the configure script does
not cope with spaces in the name of a directory in the path to the
directory in which it resides.
The opinion on the sane-devel mailing list was that the problem is
inherent in autoconf. Being a noob, I bow to their greater experience.
Of course, I could just make sure not to use spaces in any directory
related to things GNUish, and now that I know, I won’t; but it would
be nice if noobs like me didn’t have to spend days learning about this
idiosyncrasy the hard way.
Peter
On 09-Mar-24, at 11:28, Chris Bagwell wrote:
Yes, I've seen similar issues in all autotools projects. I've seen
it most on Mac's as well (don't know if its limited to just that
platform though)... The configure scripts don't seem to cope well
with spaces in directory names.
Not much can be done about this short of fixing the autotools.
Chris
On Tue, Mar 24, 2009 at 10:58 AM, Peter Schoenrank
<pe...@schoenrank.ca> wrote:
I am using Mac OS X 10.5.6 on an Intel iMac. When I do
$ mkdir ~/Desktop/scanning\ from\ the\ command\ line
$ cd ~/Desktop/scanning\ from\ the\ command\ line
$ curl 'http://alioth.debian.org/snapshots.php?group_id=30186' >
sane-scm-latest.tar.gz
$ open sane-scm-latest.tar.gz
$ cd sane-scm-2009-03-24/sane-backends
$ export BACKENDS="pixma canon"
$ ./configure --build=x86-apple-osx
I get
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/bin/sh: /Users/cps/Desktop/scanning: No such file or directory
configure: WARNING: `missing' script is too old or missing
It would seem that some part of configure is not coping with
~/Desktop/scanning\ from\ the\ command\ line
having spaces in its name.
Peter
-----
Peter Schoenrank
mailto: pe...@schoenrank.ca
phone: 250-655-6753
