POV-Ray : Newsgroups : povray.beta-test : problem with +D option at specific output file dimensions : Re: problem with +D option at specific output file dimensions Server Time
1 May 2024 01:37:20 EDT (-0400)
  Re: problem with +D option at specific output file dimensions  
From: James Dietrich
Date: 13 Dec 2013 11:40:01
Message: <web.52ab37e5151ce5afe8302f4e0@news.povray.org>
I thought I would try compiling a version with debug symbols in the hopes of
getting a meaningful backtrace, but was unable to do so.

I ran ./configure this way:
../configure --enable-debug --disable-optimiz COMPILED_BY="James Dietrich
<my_email@address>"
and the compilation process eventually failed with this:

Making all in unix
make[2]: Entering directory `/usr/local/povray/povray/unix'
g++ -DHAVE_CONFIG_H -I. -I..  -I.. -I../source -I../source -I../source/backend
-I../source/base -I../source/frontend -I../vfe -I../vfe/unix -I/usr/include/SDL
-D_GNU_SOURCE=1 -D_REENTRANT  -pthread -I/usr/include  -I/usr/include  -pipe
-Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -g -pthread -MT
disp_sdl.o -MD -MP -MF .deps/disp_sdl.Tpo -c -o disp_sdl.o disp_sdl.cpp
mv -f .deps/disp_sdl.Tpo .deps/disp_sdl.Po
g++ -DHAVE_CONFIG_H -I. -I..  -I.. -I../source -I../source -I../source/backend
-I../source/base -I../source/frontend -I../vfe -I../vfe/unix -I/usr/include/SDL
-D_GNU_SOURCE=1 -D_REENTRANT  -pthread -I/usr/include  -I/usr/include  -pipe
-Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -g -pthread -MT
disp_text.o -MD -MP -MF .deps/disp_text.Tpo -c -o disp_text.o disp_text.cpp
mv -f .deps/disp_text.Tpo .deps/disp_text.Po
g++  -pipe -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -g -pthread
-L/usr/lib  -L/usr/lib -o povray disp_sdl.o disp_text.o ../vfe/libvfe.a
.../source/libpovray.a -lSDL -L/usr/lib/x86_64-linux-gnu -lSDL -lXpm  -lSM -lICE
-lX11  -ltiff -ljpeg -lpng -lz -lrt -lm -lboost_thread-mt  -pthread
-lboost_system
.../source/libpovray.a(png.o): In function
`boost::date_time::month_formatter<boost::gregorian::greg_month,
boost::date_time::iso_extended_format<char>,
char>::format_month(boost::gregorian::greg_month const&, std::ostream&)':
/usr/include/boost/date_time/date_formatting.hpp:44: undefined reference to
`boost::gregorian::greg_month::as_short_string() const'
/usr/include/boost/date_time/date_formatting.hpp:49: undefined reference to
`boost::gregorian::greg_month::as_long_string() const'
collect2: error: ld returned 1 exit status
make[2]: *** [povray] Error 1
make[2]: Leaving directory `/usr/local/povray/povray/unix'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/povray/povray'
make: *** [all] Error 2

If someone can help me with this, I'll be glad to try again to create a better
backtrace, if that would be helpful.

Thanks you,
James

P.S. Bill, since you're curious about the odd render resolution, here's how it
happened. Our organization sells a variety of spiralbound products. The spirals
are many different colors, and a couple different sizes, too. Photographing
these items (for our catalog & website) did not lead to the best results, so I
finally decided to render the product images in povray. I created a povray file
that will produce a spiralbound cover image or a spiralbound open spread. The
size and color of the spiral, the height and width of the product, the position
of the spiral (top or left), whether to make a closed book or an open spread,
the thickness of the product, as well as the image(s) to use can all be
specified. I am quite pleased with the results.

This problem arose when I came to producing an open spread of our 5.5x4.25 inch
booklets. I wanted the resulting image to be approximately 900 pixels high so it
could be printed up to three inches high and still have at least 300 dpi. Some
empty/transparent area would of course be trimmed off all the sides, so I
decided to make povray render it about 1000 pixels high. So I found the lowest
integer that, when multiplied by 4.25, would give an integer result equal to or
greater than 1000. That integer was 236. 4.25*236=1003; 5.5*236=1298, and that
gets multiplied by two for the open spread to give 2596.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.