Re: please do a "make doc-clean; make clean"

[Carl Sorensen]

On 12/30/09 4:15 PM, "Graham Percival" <address@hidden> wrote:

> On Wed, Dec 30, 2009 at 04:06:12PM -0700, Carl Sorensen wrote:
>> 
>> On 12/30/09 3:14 PM, "Graham Percival" <address@hidden> wrote:
>> 
>>>> configure: WARNING: Python.h: accepted by the compiler, rejected by the
>>>> preprocessor!
>>> 
>>> That's not normal.
>> 
>> How can I find out about the tests used to check "usability" and "presence"?
>> I would like to know what exactly is failing.  That might give me a clue.
>> 
>> Every one of the strange warnings says that *.h is usable, but not present.
>> That seems strange.
> 
> IIRC, the exact command would be in config.log.

Thanks, that helped.

Here's the one for pango:

configure:9182: checking pango/pangoft2.h usability
configure:9182: gcc -c   -O2 -finline-functions -g -pipe
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -arch
ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk
-fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd
-fno-common -dynamic -DNDEBUG -g -O3  -I/opt/local/include/pango-1.0
-I/opt/local/include/freetype2 -I/opt/local/include
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include   conftest.c
>&5
conftest.c:9:1: warning: "PACKAGE_NAME" redefined
conftest.c:2:1: warning: this is the location of the previous definition
conftest.c:9:1: warning: "PACKAGE_NAME" redefined
conftest.c:2:1: warning: this is the location of the previous definition
configure:9182: $? = 0
configure:9182: result: yes
configure:9182: checking pango/pangoft2.h presence
configure:9182: gcc -E
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5
-I/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5 -arch
ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk
-fno-strict-aliasing -Wno-long-double -no-cpp-precomp -mno-fused-madd
-fno-common -dynamic -DNDEBUG -g -O3  -I/opt/local/include/pango-1.0
-I/opt/local/include/freetype2 -I/opt/local/include
-I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include   conftest.c
gcc-4.0: -E, -S, -save-temps and -M options are not allowed with multiple
-arch flags
configure:9182: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define PACKAGE "lilypond"
| #define PACKAGE_NAME "LilyPond"
| #define TOPLEVEL_VERSION "2.13.10"
| #define DIRSEP '/'
| #define PATHSEP ':'
| #define DATADIR "NONE/share"
| #define BUILD_PACKAGE_DATADIR
"/Users/Carl/new-lilypond/lilypond-working/out/share/lilypond"
| #define LIBDIR "NONE/lib"
| #define BUILD_PACKAGE_LIBDIR
"/Users/Carl/new-lilypond/lilypond-working/out/lib/lilypond"
| #define NDEBUG 1
| #define HAVE_LIBDL 1
| #define HAVE_DLOPEN 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_FLEXLEXER_H 1
| #define LOCALEDIR "/usr/local/share/locale"
| #define HAVE_LIBINTL 1
| #define HAVE_GETTEXT 1
| #define HAVE_LIBGUILE_H 1
| #define HAVE_LIBGUILE 1
| #define HAVE_SCM_BOOT_GUILE 1
| #define GUILE_MAJOR_VERSION 1
| #define GUILE_MINOR_VERSION 8
| #define GUILE_PATCH_LEVEL 7
| #define HAVE_PYTHON_H 1
| #define HAVE_ASSERT_H 1
| #define HAVE_GRP_H 1
| #define HAVE_PWD_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_WCHAR_H 1
| #define HAVE_SSTREAM 1
| #define HAVE_GETTEXT 1
| #define HAVE_PANGO16 1
| #define HAVE_PANGO_FT2 1
| /* end confdefs.h.  */
| #include <pango/pangoft2.h>
configure:9182: result: no
configure:9182: WARNING: pango/pangoft2.h: accepted by the compiler,
rejected by the preprocessor!
configure:9182: WARNING: pango/pangoft2.h: proceeding with the compiler's
result
configure:9182: checking for pango/pangoft2.h
configure:9182: result: yes


It looks to me like the warning is generated because we have 2 architectures
in the gcc call, so the error here appears to be a red herring.  But I have
so little experience with this that I can't be sure.

Thanks,

Carl