from GNU Radio, now the boost conflict has been resolved...
From: David Halls
Sent: 19 August 2015 17:48
To: Marcus Müller; discuss-gnuradio@gnu.org
Subject: RE: [Discuss-gnuradio] Building GNU Radio with previous Boost version
Marcus, Nathan, All,
Thanks Marcus
lk_profile.dir/all] Error 2
make[1]: Leaving directory `/home/gnuradio/gnuradio_build/gnuradio/build'
make: *** [all] Error 2
From: Marcus Müller
Sent: 17 August 2015 15:22
To: David Halls; discuss-gnuradio@gnu.org
Subject: RE: [Discuss-gnuradio] Building
*From:*
discuss-gnuradio-bounces+david.halls=toshiba-trel@gnu.org
on
behalf of Marcus Müller
*Sent:* 14 August 2015 17:59
*To:* discuss-gnuradio@gnu.org
*Subject:* Re: [Discuss-gnuradio] Building GNU Radio with previ
how would this run differently to the current setup, and avoid conflict?
Thanks guys.
David
From: West, Nathan
Sent: 17 August 2015 14:56
To: David Halls
Cc: Marcus Müller; discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Building GNU Radio with
On Mon, Aug 17, 2015 at 6:27 AM, David Halls
wrote:
>
>
> There are no quick/easy workarounds for such issues other than:
>
> 1. Making sure that all components involved make use of the same Boost
> library versions, or
>
> 2. Making sure that the components which require Boost statically link
> a
To: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Building GNU Radio with previous Boost version
Hi David,
boost > 1.35 should work, but 1.49 is, if I remember correctly, an especially
buggy version, especially in Ubuntu.
I guess you wouldn't ask if there wasn't a probl
Hi David,
boost > 1.35 should work, but 1.49 is, if I remember correctly, an
especially buggy version, especially in Ubuntu.
I guess you wouldn't ask if there wasn't a problem, so maybe you want to
elaborate?
Best regards,
Marcus
On 08/14/2015 06:00 PM, David Halls wrote:
>
> Hi guys,
>
>
> For
?Hi guys,
For a number of complicated reasons I would like to build GNU Radio with an
older version of Boost. Specifically 1.49.
Thanks,
David
NOTE: The information in this email and any attachments may be confidential
and/or legally privileged. This messa
