bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: configure bug?


From: Geoffrey Lassner
Subject: Re: configure bug?
Date: Thu, 18 Jul 2002 13:37:04 -0600

> Geoffrey Lassner <address@hidden> writes:
> 
> Hi Geoffrey,
> 
> >     I am not a compiling guru by any means but I do not believe
> > that /usr/local is preferred:
> >
> > % cd /tmp
> > % echo '#include <foo>' > foo.c
> > % cc -v -c foo.c
> > #include "..." search starts here:
> > #include <...> search starts here:
> >  /usr/include
> >  /usr/include
> 
> Indeed, it isn't.  Probably, you should file a bug report to your gcc
> package maintainer.  Here's what I get (Debian GNU/Linux unstable):
> 
>     GNU CPP version 2.95.4 20011002 (Debian prerelease) (i386 Linux/ELF)
>     #include "..." search starts here:
>     #include <...> search starts here:
>      /usr/local/include
>      /usr/lib/gcc-lib/i386-linux/2.95.4/include
>      /usr/include
>     End of search list.
> 
> > The solution below fixes everything except for python (although I do not
> > remember having to fix that one before): 
> >
> > % sh
> > $ CFLAGS='-I/usr/local/include' LDFLAGS='-L/usr/local/lib' ./configure
> 
> Good.
> 
> > checking for python2.2/Python.h... no
> > checking for python2.1/Python.h... no
> > checking for python2.0/Python.h... no
> > checking for python2/Python.h... no
> > checking for python/Python.h... no
> > checking for python1.5/Python.h... no
> > checking for Python.h... no
> 
> Ok, so where *is* your Python.h?  You should try to locate which
> package it provides, and where it lives.
> 
> Jan.

Jan,

Here it is:

% ls -l /usr/local/include/python2.1/Python.h 
-r--r--r--  1 root  wheel  2747 Jul  1 13:59 
/usr/local/include/python2.1/Python.h

I am not sure why it is not picking it up now that the CFLAGS is set.

Geoffrey




reply via email to

[Prev in Thread] Current Thread [Next in Thread]