Re: GCC 5 now the default in wily (release pocket)

2015-08-16 Thread Michi Henning
Sorry, I don't follow. This is on Jenkins. I have no choice as to what packages are used to build with there. Am I missing something? If boost can't be built for the new ABI, how is my gcc 5 compiled code going to link with boost? Cheers, Michi. On 14 Aug 2015, at 18:20 , Matthias Klose w

Re: GCC 5 now the default in wily (release pocket)

2015-08-16 Thread Michi Henning
As of today, none of our CI jobs are building any longer. It looks like gcc 5 is now the default in Jenkins, but the libraries that are installed are still compiled with 4.9. So, for example, we fail to link against leveldb because leveldb still has the old ABI string symbols in it. The boost -d

Re: GCC 5 now the default in wily (release pocket)

2015-08-16 Thread Matthias Klose
On 08/14/2015 10:07 AM, Michi Henning wrote: > As of today, none of our CI jobs are building any longer. > > It looks like gcc 5 is now the default in Jenkins, but the libraries that are > installed are still compiled with 4.9. > So, for example, we fail to link against leveldb because leveldb st

Re: GCC 5 now the default in wily (release pocket)

2015-08-14 Thread Steve Langasek
Hi Michi, On Fri, Aug 14, 2015 at 06:36:41PM +1000, Michi Henning wrote: > Sorry, I don't follow. > This is on Jenkins. I have no choice as to what packages are used to build > with there. > Am I missing something? Why are these jobs building in jenkins, rather than in a ppa? Who administers t