Looks like that one got patched by redhat.

My advice at this point: wait until monday. Sorry.

You actually don't need capidl to build bitc. If you hand-build

        libsherpa
        astmaker
        bitcc-boostratp

in that order, the bitc build should succeed. You may also need imath. I
don't remember at the moment.

shap

On Thu, 2007-01-11 at 06:26 +0100, Pierre THIERRY wrote:
> Scribit Jonathan S. Shapiro dies 10/01/2007 hora 23:50:
> > You will want a copy of flex 2.5.4.
> 
> I found it in the previous stable release of Debian, Woody. Then it
> fails a bit later:
> 
> make[2]: Entering directory 
> `/home/pierre/Logiciel/Libre/Coyotos/coyotos/src/ccs/astmaker'
> In file included from 
> /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/backward/iostream.h:31,
>                  from /usr/include/FlexLexer.h:47,
>                  from BUILD/AMlexer.cxx:254:
> /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../include/c++/4.1.2/backward/backward_warning.h:32:2:
>  error: #warning This file includes at least one deprecated or antiquated 
> header. Please consider using one of the 32 headers found in section 17.4.1.2 
> of the C++ standard. Examples include substituting the <X> header for the 
> <X.h> header for C++ includes, or <iostream> instead of the deprecated header 
> <iostream.h>. To disable this warning use -Wno-deprecated.
> make[2]: *** [BUILD/AMlexer.o] Error 1
> make[2]: Leaving directory 
> `/home/pierre/Logiciel/Libre/Coyotos/coyotos/src/ccs/astmaker'
> *** RECURSIVE BUILD STOPS ***
> make[1]: *** [recurse] Error 1
> make[1]: Leaving directory 
> `/home/pierre/Logiciel/Libre/Coyotos/coyotos/src/ccs'
> make: *** [package] Error 2
> 
> I tried to correct it in the file from the flex package, but then other
> errors show up.
> 
> So I'll wait for the non-flex version of capidl to build bitcc.
> 
> Patiently,
> Pierre
> _______________________________________________
> bitc-dev mailing list
> [email protected]
> http://www.coyotos.org/mailman/listinfo/bitc-dev

_______________________________________________
bitc-dev mailing list
[email protected]
http://www.coyotos.org/mailman/listinfo/bitc-dev

Reply via email to