Hi,

I tried to compile the v2.23 code to see if it will exhibit the same
behavior as the pre-compiled one since the v2.19 was compiled on my
computer.

I got the following error. Any suggestions what might be wrong?

Thanks in advance,
Vaggelis

==========================================================================
                             CONFIGURATION SUMMARY

==========================================================================
Using python version:   3.5.2
Python interpreter:     /usr/bin/python3.5
Installation path:      /usr/lib/python3/dist-packages/graph_tool

C++ compiler (CXX):     g++ -std=gnu++14
C++ compiler version:   5.4.0

Prefix:                 /usr/local
Pkgconfigdir:           ${libdir}/pkgconfig

Python CPP flags:       -I/usr/include/python3.5m
Python LD flags:        -L/usr/lib -lpython3.5m
Boost CPP flags:        -pthread -I/usr/include
Boost LD flags:         -lboost_iostreams -lboost_python-py35 -lboost_regex
-lboost_coroutine
Numpy CPP flags:
-I/home/labuser/.local/lib/python3.5/site-packages/numpy/core/include
Sparsehash CPP flags:
CGAL CPP flags:         -I/usr/include
CGAL LD flags:          -L/usr/lib -lCGAL -lCGAL_Core -lgmp -lboost_thread
-lpthread
Expat CPP flags:        -I/usr/include
Expat LD flags:         -L/usr/lib -lexpat
Cairomm CPP flags:       -I/usr/include/cairomm-1.0
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/cairo
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12
-I/usr/include/sigc++-2.0 -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include
Cairomm LD flags:       -lcairomm-1.0 -lcairo -lsigc-2.0
OpenMP compiler flags:  -fopenmp
OpenMP LD flags:
Extra CPPFLAGS:         -DNDEBUG
Extra CXXFLAGS:         -fopenmp -O3 -fvisibility=default
-fvisibility-inlines-hidden -Wno-deprecated -Wall -Wextra
-ftemplate-backtrace-limit=0
Extra LDFLAGS:

Using OpenMP:           yes
Using sparsehash:       yes
Using cairo:            yes
================================================================================

============================================================
                                    ERROR MESSAGE
============================================================

                     ^
layers/../overlap/../blockmodel/graph_blockmodel.hh: In member function
‘void graph_tool::BlockState<Ts>::add_vertices(Vlist&, Blist&)’:
layers/../overlap/../blockmodel/graph_blockmodel.hh:760:21: warning:
attributes at the beginning of statement are ignored [-Wattributes]
                     [[gnu::fallthrough]];
                     ^
In file included from
layers/graph_blockmodel_layers_overlap_mcmc_bundled.cc:24:0:
layers/../overlap/graph_blockmodel_overlap.hh: In lambda function:
layers/../overlap/graph_blockmodel_overlap.hh:289:32: warning: attributes
at the beginning of statement are ignored [-Wattributes]
                                [[gnu::fallthrough]];
                                ^
  CXX      layers/graph_blockmodel_layers_overlap_multicanonical.lo
In file included from
layers/../overlap/graph_blockmodel_overlap_util.hh:24:0,
                 from
layers/graph_blockmodel_layers_overlap_multicanonical.cc:23:
layers/../overlap/../blockmodel/graph_blockmodel.hh: In lambda function:
layers/../overlap/../blockmodel/graph_blockmodel.hh:300:29: warning:
attributes at the beginning of statement are ignored [-Wattributes]
                             [[gnu::fallthrough]];
                             ^
layers/../overlap/../blockmodel/graph_blockmodel.hh: In member function
‘void graph_tool::BlockState<Ts>::remove_vertices(Vlist&)’:
layers/../overlap/../blockmodel/graph_blockmodel.hh:667:21: warning:
attributes at the beginning of statement are ignored [-Wattributes]
                     [[gnu::fallthrough]];
                     ^
layers/../overlap/../blockmodel/graph_blockmodel.hh: In member function
‘void graph_tool::BlockState<Ts>::add_vertices(Vlist&, Blist&)’:
layers/../overlap/../blockmodel/graph_blockmodel.hh:760:21: warning:
attributes at the beginning of statement are ignored [-Wattributes]
                     [[gnu::fallthrough]];
                     ^
In file included from
layers/graph_blockmodel_layers_overlap_multicanonical.cc:24:0:
layers/../overlap/graph_blockmodel_overlap.hh: In lambda function:
layers/../overlap/graph_blockmodel_overlap.hh:289:32: warning: attributes
at the beginning of statement are ignored [-Wattributes]
                                [[gnu::fallthrough]];
                                ^
make[4]: *** No rule to make target
'layers/graph_blockmodel_layers_overlap_multicanonical_multiflip.cc',
needed by
'layers/graph_blockmodel_layers_overlap_multicanonical_multiflip.lo'.  Stop.
make[4]: Leaving directory
'/media/sf_junk/graph-tool-2.23/src/graph/inference'
Makefile:751: recipe for target 'all-recursive' failed
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory '/media/sf_junk/graph-tool-2.23/src/graph'
Makefile:422: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/media/sf_junk/graph-tool-2.23/src'
Makefile:604: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/media/sf_junk/graph-tool-2.23'
Makefile:491: recipe for target 'all' failed
make: *** [all] Error 2



On Wed, Sep 27, 2017 at 1:35 AM, Tiago de Paula Peixoto <[email protected]>
wrote:

> On 27.09.2017 00:29, Evangelos Petsalis wrote:
> > I am using Ubuntu 16.04 (on a fresh install) and the way I plot the
> graph is
> > using a GraphWidget that is attached to a Glade-generated GUI. The error
> I
> > get is a segmentation fault that kills the whole python environment,
> which
> > leads me to believe that there is something going on with the rendering
> > library - you can see the code dies in the middle of rendering. Note that
> > this happens on v2.22 and v2.23 but NOT on v.2.19.
> >
> > I know I am not being much more specific than before, but posting the
> code
> > that currently crashes would be of zero help since it far from the simple
> > example that you are asking.
>
> Without a specific example, there is virtually zero that anything can be
> done, unfortunately. I don't observe any crashes when doing said
> operations,
> so it must be tied to the specific way you are doing things, and it is
> difficult to guess blindly...
>
> --
> Tiago de Paula Peixoto <[email protected]>
>
>
> _______________________________________________
> graph-tool mailing list
> [email protected]
> https://lists.skewed.de/mailman/listinfo/graph-tool
>
>
_______________________________________________
graph-tool mailing list
[email protected]
https://lists.skewed.de/mailman/listinfo/graph-tool

Reply via email to