Hi,
On Mon, Feb 11, 2002 at 10:55:18PM +, Tim Waugh wrote:
> On Mon, Feb 11, 2002 at 08:47:56PM +0100, Henning Meier-Geinitz wrote:
>
> > What is the problem with explicitely mentioning "/usr/include"? Does
> > it break anything or makes it much slower?
>
> The specific problem is that newer
On Mon, Feb 11, 2002 at 20:47:56 +0100, Henning Meier-Geinitz wrote:
> On Mon, Feb 11, 2002 at 09:44:36AM +, Tim Waugh wrote:
> > sane-config --cflags shouldn't say '-I/usr/include', since that's the
> > default include path anyway; similarly, sane-config --libs shouldn't
> > say '-lc' (and it
--v541l457l4DThMFo
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Mon, Feb 11, 2002 at 08:47:56PM +0100, Henning Meier-Geinitz wrote:
> What is the problem with explicitely mentioning "/usr/include"? Does
> it break anything or makes it much slower?
The specific proble
Hi,
On Mon, Feb 11, 2002 at 09:44:36AM +, Tim Waugh wrote:
> sane-config --cflags shouldn't say '-I/usr/include', since that's the
> default include path anyway; similarly, sane-config --libs shouldn't
> say '-lc' (and it doesn't).
Can we really assume that /usr/include is included on each an
sane-config --cflags shouldn't say '-I/usr/include', since that's the
default include path anyway; similarly, sane-config --libs shouldn't
say '-lc' (and it doesn't).
Here is a patch to fix the output of sane-config --cflags.
Tim.
*/
--- sane-backends-1.0.7/tools/sane-config.in.defaultincl
