hi jonathan,

> I'd say "Yes, they are a problem".  I'm not sure what you need to fix.
> Ultimately, if you don't have the programs you need out of the build, there
> is a problem.  It's a weird error, too - because normally configure would
> detect the problem.  I'd try to track down where -arch ppc (as opposed to
> -arch=ppc) came from; that would deal with a lot of the trouble.

poking around a bit, i found

        cat /usr/include/stdarg.h
                /* This file is public domain.  */
->              /* GCC uses its own copy of this header */
                #if defined(__GNUC__)
                #include_next <stdarg.h>
                #elif defined(__MWERKS__)
                #include "mw_stdarg.h"
                #else
                #error "This header only supports __MWERKS__."
                #endif

whereas,

        cat /usr/lib/gcc/powerpc-apple-darwin9/4.2.1/include/stdarg.h
                /* Copyright (C) 1989, 1997, 1998, 1999, 2000 Free Software 
Foundation, Inc.
                
                This file is part of GCC.
                
                GCC is free software; you can redistribute it and/or modify
                ...
                /*
                 * ISO C Standard:  7.15  Variable arguments  <stdarg.h>
                 */
                
                #ifndef _STDARG_H
                #ifndef _ANSI_STDARG_H_
                #ifndef __need___va_list
                #define _STDARG_H
                #define _ANSI_STDARG_H_
                ...


i tried mod'ing CPPFLAGS with the .../4.2.1/include/stdarg.h path --
no dice.  likely hard-coded somewhere (will look).

so, as workaround, prior to configure

        mv /usr/include/stdarg.h /usr/include/stdarg.h.ORIG
        cp /usr/lib/gcc/powerpc-apple-darwin9/4.2.1/include/stdarg.h
/usr/include/stdarg.h

successfully removes the

        makedepend: warning:  cryptlib.c (reading /usr/include/stdarg.h, line
4): cannot find include file "stdarg.h"

warnings, but not the,

        makedepend: warning:  cannot open "ppc"

which are still there.

that said, mmake/install complete fine. and downstream usage of the
resultant openssl bins/libs seems ok.

so, the "ppc" warning may be just a syntactical warning ... but would
be good to know for sure.  now to try to find the reason/src of the
warning.

cheers.

Reply via email to