my steps:
yum install -y gcc gcc-c++ autoconf automake make boost boost-devel libpng-devel
libjpeg-devel libtiff-devel
wget https://codeload.github.com/POV-Ray/povray/zip/3.7-stable -O POVRay.zip
unzip POVRay.zip
cd povray-3.7-stable/unix
../prebuild.sh
cd ..
../configure COMPILED_BY="zhaoxing" --with-boost-thread=boost_thread-mt
--disable-strip --enable-debug
make
make install

files:
[root@slave-6-4 unix]# file /usr/lib64/libboost_thread-mt.so.5
/usr/lib64/libboost_thread-mt.so.5: ELF 64-bit LSB shared object, x86-64,
version 1 (SYSV), dynamically linked, stripped
[root@slave-6-4 unix]# file ./povray
../povray: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically
linked (uses shared libs), for GNU/Linux 2.6.18, not stripped
[root@slave-6-4 unix]# cat /etc/issue
CentOS release 6.4 (Final)
Kernel \r on an \m

stack:
Program received signal SIGILL, Illegal instruction.
hashed_index () at /usr/include/boost/multi_index/hashed_index.hpp:611
611     calculate_max_load();
Missing separate debuginfos, use: debuginfo-install
boost-thread-1.41.0-17.el6_4.x86_64 glibc-2.12-1.107.el6.x86_64
libgcc-4.4.7-3.el6.x86_64 libjpeg-turbo-1.2.1-1.el6.x86_64
libpng-1.2.49-1.el6_2.x86_64 libstdc++-4.4.7-3.el6.x86_64
libtiff-3.9.4-9.el6_3.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0  hashed_index () at /usr/include/boost/multi_index/hashed_index.hpp:611
#1  multi_index_container () at /usr/include/boost/multi_index_container.hpp:193
#2  hashed_factory_class () at
/usr/include/boost/flyweight/hashed_factory.hpp:38
#3  holder_arg () at /usr/include/boost/flyweight/detail/flyweight_core.hpp:158
#4  get () at /usr/include/boost/flyweight/static_holder.hpp:33
#5  init () at /usr/include/boost/flyweight/detail/flyweight_core.hpp:111
#6  __static_initialization_and_destruction_0 ()
    at /usr/include/boost/flyweight/detail/flyweight_core.hpp:215
#7  global constructors keyed to _ZN3pov18SubsurfaceInteriorC2Ed() ()
    at backend/lighting/subsurface.cpp:114
#8  0x0000000000606046 in __do_global_ctors_aux ()
#9  0x000000000040b333 in _init ()
#10 0x00007fffffffe5c8 in ?? ()
#11 0x0000000000605fb5 in __libc_csu_init ()
#12 0x00007ffff639ec70 in __libc_start_main () from /lib64/libc.so.6
#13 0x000000000040c839 in _start ()

Am I missing any configure options?

Thanks!

Post a reply to this message

Am 15.01.2014 13:10, schrieb zhao:

> Program received signal SIGILL, Illegal instruction.
> hashed_index () at /usr/include/boost/multi_index/hashed_index.hpp:611
> 611     calculate_max_load();
> Missing separate debuginfos, use: debuginfo-install
> boost-thread-1.41.0-17.el6_4.x86_64 glibc-2.12-1.107.el6.x86_64
> libgcc-4.4.7-3.el6.x86_64 libjpeg-turbo-1.2.1-1.el6.x86_64
> libpng-1.2.49-1.el6_2.x86_64 libstdc++-4.4.7-3.el6.x86_64
> libtiff-3.9.4-9.el6_3.x86_64 zlib-1.2.3-29.el6.x86_64
> (gdb) bt
> #0  hashed_index () at /usr/include/boost/multi_index/hashed_index.hpp:611
> #1  multi_index_container () at /usr/include/boost/multi_index_container.hpp:193
> #2  hashed_factory_class () at
> /usr/include/boost/flyweight/hashed_factory.hpp:38
> #3  holder_arg () at /usr/include/boost/flyweight/detail/flyweight_core.hpp:158
> #4  get () at /usr/include/boost/flyweight/static_holder.hpp:33
> #5  init () at /usr/include/boost/flyweight/detail/flyweight_core.hpp:111
> #6  __static_initialization_and_destruction_0 ()
>      at /usr/include/boost/flyweight/detail/flyweight_core.hpp:215
> #7  global constructors keyed to _ZN3pov18SubsurfaceInteriorC2Ed() ()
>      at backend/lighting/subsurface.cpp:114

The last line indicates to me that you're trying to render a scene with 
SSLT.

Note that the SSLT feature is still highly experimental, with known 
bugs. I suspect that your SSLT texture has a pigment with some zero 
colour component, a situation SSLT can't deal with. That would be 
consistent with what you see.

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:

>
> The last line indicates to me that you're trying to render a scene with
> SSLT.
>
> Note that the SSLT feature is still highly experimental, with known
> bugs. I suspect that your SSLT texture has a pigment with some zero
> colour component, a situation SSLT can't deal with. That would be
> consistent with what you see.

Thanks for checking it so carefully.
I'm not using any parameter or ini
Just run povray, it core dump.

Post a reply to this message

Am 15.01.2014 15:28, schrieb zhao:
> clipka <ano### [at] anonymousorg> wrote:
>
>>
>> The last line indicates to me that you're trying to render a scene with
>> SSLT.
>>
>> Note that the SSLT feature is still highly experimental, with known
>> bugs. I suspect that your SSLT texture has a pigment with some zero
>> colour component, a situation SSLT can't deal with. That would be
>> consistent with what you see.
>
> Thanks for checking it so carefully.
> I'm not using any parameter or ini
> Just run povray, it core dump.

You surely are using some /scene/ to render, right?

Post a reply to this message

Le 15/01/2014 13:10, zhao nous fit lire :
> make
> make install

did you tried : "make check" before "make install" ?

Security note: do not develop as root.

Can we have the tail (summary) of the configure output ?

(there is a know case of a processor not happy with the default of
g++/gcc about -march=native...)

I see also a libgcc 4.4.7... it's a bit old too if the gcc version is
really 4.4.7

Post a reply to this message

clipka <ano### [at] anonymousorg> wrote:
> Am 15.01.2014 15:28, schrieb zhao:
> > clipka <ano### [at] anonymousorg> wrote:
> >
> >>
> >> The last line indicates to me that you're trying to render a scene with
> >> SSLT.
> >>
> >> Note that the SSLT feature is still highly experimental, with known
> >> bugs. I suspect that your SSLT texture has a pigment with some zero
> >> colour component, a situation SSLT can't deal with. That would be
> >> consistent with what you see.
> >
> > Thanks for checking it so carefully.
> > I'm not using any parameter or ini
> > Just run povray, it core dump.
>
> You surely are using some /scene/ to render, right?

No, I dont have a /scene/ thing.

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 15/01/2014 13:10, zhao nous fit lire :
> > make
> > make install
>
> did you tried : "make check" before "make install" ?
>
> Security note: do not develop as root.
>
> Can we have the tail (summary) of the configure output ?
>
> (there is a know case of a processor not happy with the default of
> g++/gcc about -march=native...)
>
> I see also a libgcc 4.4.7... it's a bit old too if the gcc version is
> really 4.4.7

Environment
-----------
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking whether $C_INCLUDE_PATH contains the "." path... no
checking whether $CPLUS_INCLUDE_PATH contains the "." path... no

Programs
--------
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for stdlib.h... (cached) yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether the g++ compiler works... yes
checking how to run the C++ preprocessor... g++ -E
checking for C++ compiler vendor... gnu
checking for g++ version... 4.4.7
checking for ranlib... ranlib

Libraries
---------
checking whether to link with cygwin DLL... no
checking whether to enable static linking... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking whether pthreads work with -pthread... yes
checking for joinable pthread attribute... PTHREAD_CREATE_JOINABLE
checking if more special flags are required for pthreads... no
checking for boostlib >= 1.37... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread-mt... yes
checking whether the boost thread library is usable... yes
checking for sin in -lmkl... no
checking for sin in -lm... yes
checking for clock_gettime in -lrt... yes
checking whether to use the ZLIB library... yes
checking for library containing zlibVersion... -lz
checking zlib.h usability... yes
checking zlib.h presence... yes
checking for zlib.h... yes
checking for libz version >= 1.2.1... 1.2.3, ok
checking whether to use the PNG library... yes
checking for library containing png_get_libpng_ver... -lpng
checking png.h usability... yes
checking png.h presence... yes
checking for png.h... yes
checking for libpng version >= 1.2.5... 1.2.49, ok
checking whether to use the JPEG library... yes
checking for library containing jpeg_std_error... -ljpeg
checking jpeglib.h usability... yes
checking jpeglib.h presence... yes
checking for jpeglib.h... yes
checking for libjpeg version >= 6b (62)... 62, ok
checking whether to use the TIFF library... yes
checking for library containing TIFFGetVersion... -ltiff
checking tiffio.h usability... yes
checking tiffio.h presence... yes
checking for tiffio.h... yes
checking for libtiff version >= 3.6.1... 3.9.4, ok
checking whether to use the OpenEXR library... yes
checking for pkg-config... pkg-config
checking for OpenEXR's pkg-config... not found
configure: WARNING: all program features using the OpenEXR library are disabled
checking for X... libraries /usr/lib, headers /usr/include
checking whether -R must be followed by a space... neither works
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for gethostbyname... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for IceConnectionNumber in -lICE... no
checking X11/Xlib.h usability... no
checking X11/Xlib.h presence... no
checking for X11/Xlib.h... no

Language constructs and functions
---------------------------------
checking whether time.h and sys/time.h may both be included... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking sys/resource.h usability... yes
checking sys/resource.h presence... yes
checking for sys/resource.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking size of int... 4
checking size of long int... 8
checking size of size_t... 8
checking size of float... 4
checking for working memcmp... yes
checking for vsnprintf... yes
checking for getcwd... yes
checking for readlink... yes
checking for nanosleep... yes
checking for clock_gettime... yes
checking for getrusage... yes
checking for gettimeofday... yes
checking for asinh... yes

Compiling
---------
checking whether to enable pipes for communications... yes
checking whether g++ accepts -pipe... yes
checking whether g++ accepts -Wno-multichar... yes
checking whether g++ accepts -Wno-write-strings... yes
checking whether g++ accepts -fno-enforce-eh-specs... yes
checking whether to enable I/O restrictions... yes
checking whether to enable debugging... yes
checking whether g++ accepts -g... yes
checking whether to enable profiling... no
checking whether to enable stripping... no
checking whether to enable optimizations... yes
checking whether g++ accepts -O3... yes
checking whether g++ accepts -ffast-math... yes
checking whether to enable architecture-specific optimizations... yes
checking whether g++ accepts -xHost... no
checking whether g++ accepts -march=native... yes
checking which architecture to optimize for... x86_64-unknown-linux-gnu (using
-march=native)

Makefiles
---------
configure: creating ./config.status
config.status: creating Makefile
config.status: creating source/Makefile
config.status: creating vfe/Makefile
config.status: creating unix/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands

===============================================================================
POV-Ray 3.7.0 has been configured.

Built-in features:
  I/O restrictions:          enabled
  X Window display:          disabled
  Supported image formats:   gif tga iff ppm pgm hdr png jpeg tiff
  Unsupported image formats: openexr

Compilation settings:
  Build architecture:  x86_64-unknown-linux-gnu
  Built/Optimized for: x86_64-unknown-linux-gnu (using -march=native)
  Compiler vendor:     gnu
  Compiler version:    g++ 4.4.7
  Compiler flags:      -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -g -O3 -ffast-math -march=native -pthread

Type 'make check' to build the program and run a test render.
Type 'make install' to install POV-Ray on your system.

The POV-Ray components will be installed in the following directories:
  Program (executable):       /usr/local/bin
  System configuration files: /usr/local/etc/povray/3.7
  User configuration files:   /root/.povray/3.7
  Standard include files:     /usr/local/share/povray-3.7/include
  Standard INI files:         /usr/local/share/povray-3.7/ini
  Standard demo scene files:  /usr/local/share/povray-3.7/scenes
  Documentation (text, HTML): /usr/local/share/doc/povray-3.7
  Unix man page:              /usr/local/share/man

Post a reply to this message

Le_Forgeron <jgr### [at] freefr> wrote:
> Le 15/01/2014 13:10, zhao nous fit lire :
> > make
> > make install
>
> did you tried : "make check" before "make install" ?
>
> Security note: do not develop as root.
>
> Can we have the tail (summary) of the configure output ?
>
> (there is a know case of a processor not happy with the default of
> g++/gcc about -march=native...)
>
> I see also a libgcc 4.4.7... it's a bit old too if the gcc version is
> really 4.4.7

well, the gcc is 4.4.7.  it's common package from CentOS 6.

Post a reply to this message

Am 16.01.2014 03:29, schrieb zhao:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 15.01.2014 15:28, schrieb zhao:
>>> clipka <ano### [at] anonymousorg> wrote:
>>>
>>>>
>>>> The last line indicates to me that you're trying to render a scene with
>>>> SSLT.
>>>>
>>>> Note that the SSLT feature is still highly experimental, with known
>>>> bugs. I suspect that your SSLT texture has a pigment with some zero
>>>> colour component, a situation SSLT can't deal with. That would be
>>>> consistent with what you see.
>>>
>>> Thanks for checking it so carefully.
>>> I'm not using any parameter or ini
>>> Just run povray, it core dump.
>>
>> You surely are using some /scene/ to render, right?
>
> No, I dont have a /scene/ thing.

So you're just running the command "povray" without any parameters?

With that information in mind, I've just re-read the stack trace more 
carefully. If it says what I now think it says, then /something/ appears 
to be wrong with either your boost header files - or your compiler.

Post a reply to this message

Le 16/01/2014 03:58, zhao nous fit lire :
> Le_Forgeron <jgr### [at] freefr> wrote:
>> Le 15/01/2014 13:10, zhao nous fit lire :
>>> make
>>> make install
>>
>> did you tried : "make check" before "make install" ?

so, what about "make check" ?

>>
>> Security note: do not develop as root.
>>
>> Can we have the tail (summary) of the configure output ?
>>

thanks. nothing shoking.

Post a reply to this message