Hi(gh)!

About two weeks ago, I tried compiling 3.7 under Linux (Debian, kernel 
version 2.6)... I soon realized that I would have to install some 
ominous "boost" packages. But as nobody could tell me exactly which of 
these packages I would have to install, I simply tried apt-get install 
boost* - and, promptly, blew my system completely as the system 
partition ran full.

After I managed to get the system working once more, I still have no 
clue what boost packages to install...

See you in Khyberspace!

Yadgar

Post a reply to this message

Jörg 'Yadgar' Bleimann <yaz### [at] gmxde> wrote:
> About two weeks ago, I tried compiling 3.7 under Linux (Debian, kernel 
> version 2.6)... I soon realized that I would have to install some 
> ominous "boost" packages. But as nobody could tell me exactly which of 
> these packages I would have to install, I simply tried apt-get install 
> boost* - and, promptly, blew my system completely as the system 
> partition ran full.

> After I managed to get the system working once more, I still have no 
> clue what boost packages to install...

  I would recommend that if you want to compile your own programs, you
acquire more disk space and install boost using the package manager of
your linux distro (ie. apt-get in your case), rather than trying to
kludge povray to compile with partial boost manual installations. Free
some space of buy a bigger hard disk.

-- 
                                                          - Warp

Post a reply to this message

On Tue, 08 Nov 2011 19:52:14 +0100, Jörg 'Yadgar' Bleimann wrote:

> After I managed to get the system working once more, I still have no
> clue what boost packages to install...

See http://povray.org/beta/source/unix-src-INSTALL.txt

Section 2.2, "Required Support Libraries".

Jim

Post a reply to this message

Hi(gh)!

On 08.11.2011 20:13, Jim Henderson wrote:

> See http://povray.org/beta/source/unix-src-INSTALL.txt
>
> Section 2.2, "Required Support Libraries".

Now I downloaded version 1.47 of the boost libaries from www.boost.org, 
unpacked it into /usr/local/ and then this:

"To compile anything in Boost, you need a directory containing the 
boost/ subdirectory in your #include path."

(http://www.boost.org/doc/libs/1_47_0/more/getting_started/unix-variants.html#get-boost)

What is the #include path? Where do I find it?

Why are these things so brain-shreddingly complicated?

See you in Khyberspace!

Yadgar

Post a reply to this message

> Hi(gh)!
>
> About two weeks ago, I tried compiling 3.7 under Linux (Debian,
> kernel version 2.6)... I soon realized that I would have to install
> some ominous "boost" packages. But as nobody could tell me exactly
> which of these packages I would have to install, I simply tried
> apt-get install boost* - and, promptly, blew my system completely as
> the system partition ran full.
>
> After I managed to get the system working once more, I still have no
>  clue what boost packages to install...

   Here on Ubuntu, I had to install libboost and libboost-dev... I
suppose it should be the same for Debian.

   Regards,

--
Jaime

Post a reply to this message

On Tue, 08 Nov 2011 21:44:45 +0100, Jörg 'Yadgar' Bleimann wrote:

> Now I downloaded version 1.47 of the boost libaries from www.boost.org,
> unpacked it into /usr/local/ and then this:
> 
> "To compile anything in Boost, you need a directory containing the
> boost/
> subdirectory in your #include path."
> 
> (http://www.boost.org/doc/libs/1_47_0/more/getting_started/unix-
variants.html#get-boost)
> 
> What is the #include path? Where do I find it?
> 
> Why are these things so brain-shreddingly complicated?

The path used for #include in *nix is specified with the -I parameter for 
the 'make' command or is specified in the Makefile.

"man make" will tell you what you need to know.

Do you often build software on Linux?  If you don't, you might want to 
start with a tutorial on how to build software in general before diving 
in to build POVray.

Jim

Post a reply to this message

Am 08.11.2011 21:44, schrieb Jörg 'Yadgar' Bleimann:

> What is the #include path? Where do I find it?
>
> Why are these things so brain-shreddingly complicated?

Seems to be typical for libraries. I have yet to see any that comes with 
an easy-to-use build system. Or at least some /standardized/ one, for 
that matter. The tendency there seems to be to try make life for the lib 
developers as easy as possible by using some home-brewn build system 
custom-tailored to their needs, but at the same time making life 
annoyingly difficult for application developers (or end users), forcing 
them to dig through all those different build systems of the libraries 
the app is using.

Okay, maybe I'm exaggerating here. Never mind...

Post a reply to this message

Hi(gh)!

On 08.11.2011 23:04, Jaime Vives Piqueres wrote:

> Here on Ubuntu, I had to install libboost and libboost-dev... I
> suppose it should be the same for Debian.

I only could successfully install libboost-dev - libboost does not exist 
on the repositories for my distro (which is Debian aptosid, kernel 2.6.9).


<yaz### [at] gmxde>", firstly all went fine... until configure complained:

configure: error: cannot find a suitable ZLIB library

What went wrong now? Or should I better first compile and install the 
whole boost v1.47 package from www.boost.org?

See you in Khyberspace!

Yadgar

Post a reply to this message

Hi(gh)!

On 09.11.2011 00:02, Jim Henderson wrote:

> Do you often build software on Linux?

No - it's the very first time in my life (after one or two early aborted 
attempts in the past few years)!

>  If you don't, you might want to
> start with a tutorial on how to build software in general before diving
> in to build POVray.

And where do I find such a tutorial (no, I don't believe in Google being 
my friend!)?

See you in Khyberspace!

Yadgar

Post a reply to this message

Hi(gh)!

On 09.11.2011 00:23, clipka wrote:

> Seems to be typical for libraries. I have yet to see any that comes with
> an easy-to-use build system. Or at least some /standardized/ one, for
> that matter. The tendency there seems to be to try make life for the lib
> developers as easy as possible by using some home-brewn build system
> custom-tailored to their needs, but at the same time making life
> annoyingly difficult for application developers (or end users), forcing
> them to dig through all those different build systems of the libraries
> the app is using.

I'm about to give up... and remorsefully crawling back into 
Micro$lavery! Obviously, it is IMPOSSIBLE for an average DAU (to the 
non-German speakers: Most Stupid User To Assume!) to build any software 
under Linux!

See you in Khyberspace!

Yadgar

Post a reply to this message