All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: remove boost-jam-native 3.1.11
Date: Thu, 04 Dec 2008 15:58:19 -0500	[thread overview]
Message-ID: <4938446B.8020100@balister.org> (raw)
In-Reply-To: <49382D2D.1030504@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]

Robert Schuster wrote:
> Hi,
> I would like to remove the boost-jam-native recipe for version 3.1.11
> and instead rely on version 3.1.16 which we also have.
> 
> The reason is that you cannot build the newer boost version 1.34 and
> 1.36 with the older boost-jam while 1.33 can work with the newer as well.

You don't need to remove the old one, just set things to use the new 
one. I have no problem with this.

> On a related note: I invested some time to get boost 1.34.1 being build
> nicely including the bzip2 and gzip support. Now I see that in the 1.36
> recipe those are disabled again. That is unfortunate because wesnoth
> needs them.

I think I added the recipe. I use it on the beagle, which uses gcc 4.3, 
which may have had some trouble with parts of boost. I'm OK with moving 
to a newer boost, but there are some non-backward compatible changes in 
boost that we will need to watch out for. I needed only a couple pieces 
from boost 1.36, so I built the ones I needed and set the recipe to 
DEFAULT_PREFERENCE="-1".

Philip


> 
> Regards
> Robert
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  parent reply	other threads:[~2008-12-04 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-04 19:19 RFC: remove boost-jam-native 3.1.11 Robert Schuster
2008-12-04 19:31 ` Koen Kooi
2008-12-04 20:58 ` Philip Balister [this message]
2008-12-05 11:19   ` Robert Schuster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4938446B.8020100@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.