Fedora rawhide FTBFS status 2010-05-27 x86_64

Braden McDaniel braden at endoframe.com
Mon May 31 19:54:53 UTC 2010


On Mon, 2010-05-31 at 12:43 -0500, Matt Domsch wrote:
Fedora Fails To Build From Source Results for x86_64
> using rawhide from 2010-05-27
> 
> This is a full rebuild, the first for Fedora 14's rawhide.  The
> builders all have Fedora 13 installed.
> 
> Full logs at http://linux.dell.com/files/fedora/FixBuildRequires/

This seems to be diagnosing a good deal more than broken
BuildRequires...

> openvrml-0.18.5-2.fc14 (build/make) braden

        libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -I../src/libopenvrml -I../src/libopenvrml -I../src/local/libopenvrml-dl -DOPENVRML_LIBDIR_=\"/usr/lib64\" -DOPENVRML_PKGDATADIR_=\"/usr/share/openvrml\" -DOPENVRML_PKGLIBDIR_=\"/usr/lib64/openvrml\" -DBOOST_MPL_CFG_NO_PREPROCESSED_HEADERS -DBOOST_MPL_LIMIT_VECTOR_SIZE=30 -I/usr/lib/jvm/java/include -I/usr/lib/jvm/java/include/linux -DNDEBUG -I/usr/include/freetype2 -pthread -I/usr/include/libxml2 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fvisibility=hidden -fvisibility-inlines-hidden -Wno-missing-braces -Wno-strict-aliasing -Wno-unused-variable -c libopenvrml/openvrml/script.cpp  -fPIC -DPIC -o libopenvrml/openvrml/.libs/libopenvrml_libopenvrml_la-script.o
    {standard input}: Assembler messages:
    {standard input}:71597: Warning: end of file not at end of a line; newline inserted
    {standard input}:72206: Error: expected comma after name `_ZNK5boost6spirit7classic16assertive_parserIN8openvrml16vrml_parse_errorENS1_14functor_parserINS3_12int32_parserEEEE5parseINS1_7scannerINS1_10multi_passISt19istreambuf_iteratorIcSt11char_traitsIcEENS1_19multi_pass_policies14input' in .size directive
    g++: Internal error: Killed (program cc1plus)
    Please submit a full bug report.
    See <http://bugzilla.redhat.com/bugzilla> for instructions.

Ouch.  I'm not sure if this is Random Badness or not; but i386 failed,
too; so maybe it's the same thing.  Nope.  While it *might* have the
same problem, i386 didn't get past configure:

        checking for GIO... ./configure: line 21460: 19388 Segmentation fault      (core dumped) ( $PKG_CONFIG --exists --print-errors "gio-2.0" ) 2>&5
    ./configure: line 21476: 19392 Segmentation fault      (core dumped) ( $PKG_CONFIG --exists --print-errors "gio-2.0" ) 2>&5
    no
        
Well, that's... interesting.

If there were disc space issues (as Dan Horák suggests), that could
result in some rather exotic errors.

-- 
Braden McDaniel <braden at endoframe.com>



More information about the devel mailing list