Re: boost problem while packaging SuperCollider 3.8

2017-09-29 Thread Dan S
2017-09-28 23:54 GMT+01:00 Felipe Sateler :
> On Thu, Sep 28, 2017 at 7:05 PM, Dan S  wrote:
>>
>> 2017-09-26 9:49 GMT+01:00 Dan S :
>> > 2017-09-26 9:26 GMT+01:00 Dan S :
>> >> 2017-09-25 16:36 GMT+01:00 Felipe Sateler :
>> >>> On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  
>> >>> wrote:
>>  On Mon, Sep 25, 2017 at 11:14 AM, Dan S  
>>  wrote:
>> >
>> > 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
>> > >
>> > >
>> > > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  
>> > > wrote:
>> > >>
>> > >> Hi
>> > >>
>> > >> I'm trying to get the new release 3.8 of SuperCollider into the
>> > >> debian-multimedia repository. I've done an import to git here (not
>> > >> pushed yet). The problem is SC's dependency on boost.
>> > >
>> > >
>> > > Please push, so that I can try to reproduce locally.
>> >
>> > OK, done.
>> 
>>  Oh I'm so terribly sorry. I see now that I forgot to push the last
>>  upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
>>  with mine to see if things build. I believe this should fix at least
>>  some problems with newer gcc.
>> >>>
>> >>> Indeed, the patches Adrian Bunk sent fix the failure to build. I have
>> >>> force pushed the changes to git (so please use git reset instead of a
>> >>> simple pull). Some are already upstream but it appears the
>> >>> PyrSched.cpp one is not yet.
>> >>>
>> >>> I'm sorry for causing additional work :(
>> >>
>> >> OK, thanks.
>> >>
>> >> On the latest master then:
>> >> * I refreshed patches (because "gbp -S" failing complaining about fuzzy 
>> >> patches)
>> >> * Build failed on gcc 7 due to an ICE while compiling some part of 
>> >> supernova
>> >> * I'm running a gcc 6 build today, I'll let you know if it completes.
>> >
>> > ...failed due to ICE again :( Something while building supernova
>>
>> OK, now after much updating of packages on my machine, and I have a
>> successful build! Hurrah!
>>
>> My build succeeded as of commit 79d7a5320, plus a local commit in
>> which I ensured it was using GCC 6 (6.4.0).
>> (It failed with an internal compiler error when I allowed it to
>> default to GC 7.2.0.)
>
> Weird. It builds here and on debomatic[1].
>
> [1] 
> http://debomatic-amd64.debian.net/distribution#unstable/supercollider/3.8.0~repack-1/buildlog
>
>>
>> Someone else (Miguel) also reported he can compile and run the 3.8.0
>> version from the debian-multimedia repository now.
>
> Excellent! I have pushed a few changes, including a repack fix (the
> portaudio dir name changed). If you think this looks good I can upload
> (unless there is more stuff pending?).

Looks good to me!

Dan

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-28 Thread Felipe Sateler
On Thu, Sep 28, 2017 at 7:05 PM, Dan S  wrote:
>
> 2017-09-26 9:49 GMT+01:00 Dan S :
> > 2017-09-26 9:26 GMT+01:00 Dan S :
> >> 2017-09-25 16:36 GMT+01:00 Felipe Sateler :
> >>> On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  
> >>> wrote:
>  On Mon, Sep 25, 2017 at 11:14 AM, Dan S  
>  wrote:
> >
> > 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
> > >
> > >
> > > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  
> > > wrote:
> > >>
> > >> Hi
> > >>
> > >> I'm trying to get the new release 3.8 of SuperCollider into the
> > >> debian-multimedia repository. I've done an import to git here (not
> > >> pushed yet). The problem is SC's dependency on boost.
> > >
> > >
> > > Please push, so that I can try to reproduce locally.
> >
> > OK, done.
> 
>  Oh I'm so terribly sorry. I see now that I forgot to push the last
>  upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
>  with mine to see if things build. I believe this should fix at least
>  some problems with newer gcc.
> >>>
> >>> Indeed, the patches Adrian Bunk sent fix the failure to build. I have
> >>> force pushed the changes to git (so please use git reset instead of a
> >>> simple pull). Some are already upstream but it appears the
> >>> PyrSched.cpp one is not yet.
> >>>
> >>> I'm sorry for causing additional work :(
> >>
> >> OK, thanks.
> >>
> >> On the latest master then:
> >> * I refreshed patches (because "gbp -S" failing complaining about fuzzy 
> >> patches)
> >> * Build failed on gcc 7 due to an ICE while compiling some part of 
> >> supernova
> >> * I'm running a gcc 6 build today, I'll let you know if it completes.
> >
> > ...failed due to ICE again :( Something while building supernova
>
> OK, now after much updating of packages on my machine, and I have a
> successful build! Hurrah!
>
> My build succeeded as of commit 79d7a5320, plus a local commit in
> which I ensured it was using GCC 6 (6.4.0).
> (It failed with an internal compiler error when I allowed it to
> default to GC 7.2.0.)

Weird. It builds here and on debomatic[1].

[1] 
http://debomatic-amd64.debian.net/distribution#unstable/supercollider/3.8.0~repack-1/buildlog

>
> Someone else (Miguel) also reported he can compile and run the 3.8.0
> version from the debian-multimedia repository now.

Excellent! I have pushed a few changes, including a repack fix (the
portaudio dir name changed). If you think this looks good I can upload
(unless there is more stuff pending?).

-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-28 Thread Dan S
2017-09-26 9:49 GMT+01:00 Dan S :
> 2017-09-26 9:26 GMT+01:00 Dan S :
>> 2017-09-25 16:36 GMT+01:00 Felipe Sateler :
>>> On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  
>>> wrote:
 On Mon, Sep 25, 2017 at 11:14 AM, Dan S  wrote:
>
> 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
> >
> >
> > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  
> > wrote:
> >>
> >> Hi
> >>
> >> I'm trying to get the new release 3.8 of SuperCollider into the
> >> debian-multimedia repository. I've done an import to git here (not
> >> pushed yet). The problem is SC's dependency on boost.
> >
> >
> > Please push, so that I can try to reproduce locally.
>
> OK, done.

 Oh I'm so terribly sorry. I see now that I forgot to push the last
 upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
 with mine to see if things build. I believe this should fix at least
 some problems with newer gcc.
>>>
>>> Indeed, the patches Adrian Bunk sent fix the failure to build. I have
>>> force pushed the changes to git (so please use git reset instead of a
>>> simple pull). Some are already upstream but it appears the
>>> PyrSched.cpp one is not yet.
>>>
>>> I'm sorry for causing additional work :(
>>
>> OK, thanks.
>>
>> On the latest master then:
>> * I refreshed patches (because "gbp -S" failing complaining about fuzzy 
>> patches)
>> * Build failed on gcc 7 due to an ICE while compiling some part of supernova
>> * I'm running a gcc 6 build today, I'll let you know if it completes.
>
> ...failed due to ICE again :( Something while building supernova

OK, now after much updating of packages on my machine, and I have a
successful build! Hurrah!

My build succeeded as of commit 79d7a5320, plus a local commit in
which I ensured it was using GCC 6 (6.4.0).
(It failed with an internal compiler error when I allowed it to
default to GC 7.2.0.)

Someone else (Miguel) also reported he can compile and run the 3.8.0
version from the debian-multimedia repository now.

Best
Dan

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-26 Thread Dan S
2017-09-26 9:26 GMT+01:00 Dan S :
> 2017-09-25 16:36 GMT+01:00 Felipe Sateler :
>> On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  wrote:
>>> On Mon, Sep 25, 2017 at 11:14 AM, Dan S  wrote:

 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
 >
 >
 > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  
 > wrote:
 >>
 >> Hi
 >>
 >> I'm trying to get the new release 3.8 of SuperCollider into the
 >> debian-multimedia repository. I've done an import to git here (not
 >> pushed yet). The problem is SC's dependency on boost.
 >
 >
 > Please push, so that I can try to reproduce locally.

 OK, done.
>>>
>>> Oh I'm so terribly sorry. I see now that I forgot to push the last
>>> upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
>>> with mine to see if things build. I believe this should fix at least
>>> some problems with newer gcc.
>>
>> Indeed, the patches Adrian Bunk sent fix the failure to build. I have
>> force pushed the changes to git (so please use git reset instead of a
>> simple pull). Some are already upstream but it appears the
>> PyrSched.cpp one is not yet.
>>
>> I'm sorry for causing additional work :(
>
> OK, thanks.
>
> On the latest master then:
> * I refreshed patches (because "gbp -S" failing complaining about fuzzy 
> patches)
> * Build failed on gcc 7 due to an ICE while compiling some part of supernova
> * I'm running a gcc 6 build today, I'll let you know if it completes.

...failed due to ICE again :( Something while building supernova

 >> The upstream includes boost in the download, and so to be Debian-like,
 >> we strip that out and use system boost instead. This works in prev
 >> releases, but in 3.8 (which has updated to use boost 1.63) it errors
 >> out with confusing compiler/linker problems:
 >> https://github.com/supercollider/supercollider/issues/3203
 >>
 >
 > I notice you are using wheezy. I'd first try building in sid. BTW, where 
 > did
 > you get boost 1.63? Unstable has 1.62...

 "libboost1.63-dev" etc packages
>>>
>>> OK, why did you bump these deps? I don't see any specific requirement
>>> for 1.63 (at least with a quick grep through the sources).
>>>
>>
>> I did not keep this commit in the forced push (but have kept locally
>> in case it is still needed), because SC built fine without it.
>
> The reason for the dependency is that in the older boost I was using
> last week (1.58?) there was a straightforward build failure because a
> boost function's arguments have changed across versions. So there
> should be SOME version bump in the dependency but I don't know what
> the minimum is. I went for 1.63 because it matches the bundled SC
> version and was available.
>
> This has now taken a lot of my time and I'm afraid I cannot do much
> more (work commitments). If I had time I could trace that dependency
> issue, report the ICE, test that SC runs...! But I must stop, sorry.
>
> Dan

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-26 Thread Dan S
2017-09-25 16:36 GMT+01:00 Felipe Sateler :
> On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  wrote:
>> On Mon, Sep 25, 2017 at 11:14 AM, Dan S  wrote:
>>>
>>> 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
>>> >
>>> >
>>> > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  wrote:
>>> >>
>>> >> Hi
>>> >>
>>> >> I'm trying to get the new release 3.8 of SuperCollider into the
>>> >> debian-multimedia repository. I've done an import to git here (not
>>> >> pushed yet). The problem is SC's dependency on boost.
>>> >
>>> >
>>> > Please push, so that I can try to reproduce locally.
>>>
>>> OK, done.
>>
>> Oh I'm so terribly sorry. I see now that I forgot to push the last
>> upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
>> with mine to see if things build. I believe this should fix at least
>> some problems with newer gcc.
>
> Indeed, the patches Adrian Bunk sent fix the failure to build. I have
> force pushed the changes to git (so please use git reset instead of a
> simple pull). Some are already upstream but it appears the
> PyrSched.cpp one is not yet.
>
> I'm sorry for causing additional work :(

OK, thanks.

On the latest master then:
* I refreshed patches (because "gbp -S" failing complaining about fuzzy patches)
* Build failed on gcc 7 due to an ICE while compiling some part of supernova
* I'm running a gcc 6 build today, I'll let you know if it completes.


>>> >> The upstream includes boost in the download, and so to be Debian-like,
>>> >> we strip that out and use system boost instead. This works in prev
>>> >> releases, but in 3.8 (which has updated to use boost 1.63) it errors
>>> >> out with confusing compiler/linker problems:
>>> >> https://github.com/supercollider/supercollider/issues/3203
>>> >>
>>> >
>>> > I notice you are using wheezy. I'd first try building in sid. BTW, where 
>>> > did
>>> > you get boost 1.63? Unstable has 1.62...
>>>
>>> "libboost1.63-dev" etc packages
>>
>> OK, why did you bump these deps? I don't see any specific requirement
>> for 1.63 (at least with a quick grep through the sources).
>>
>
> I did not keep this commit in the forced push (but have kept locally
> in case it is still needed), because SC built fine without it.

The reason for the dependency is that in the older boost I was using
last week (1.58?) there was a straightforward build failure because a
boost function's arguments have changed across versions. So there
should be SOME version bump in the dependency but I don't know what
the minimum is. I went for 1.63 because it matches the bundled SC
version and was available.

This has now taken a lot of my time and I'm afraid I cannot do much
more (work commitments). If I had time I could trace that dependency
issue, report the ICE, test that SC runs...! But I must stop, sorry.

Dan

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Felipe Sateler
On Mon, Sep 25, 2017 at 12:22 PM, Felipe Sateler  wrote:
> On Mon, Sep 25, 2017 at 11:14 AM, Dan S  wrote:
>>
>> 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
>> >
>> >
>> > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  wrote:
>> >>
>> >> Hi
>> >>
>> >> I'm trying to get the new release 3.8 of SuperCollider into the
>> >> debian-multimedia repository. I've done an import to git here (not
>> >> pushed yet). The problem is SC's dependency on boost.
>> >
>> >
>> > Please push, so that I can try to reproduce locally.
>>
>> OK, done.
>
> Oh I'm so terribly sorry. I see now that I forgot to push the last
> upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
> with mine to see if things build. I believe this should fix at least
> some problems with newer gcc.

Indeed, the patches Adrian Bunk sent fix the failure to build. I have
force pushed the changes to git (so please use git reset instead of a
simple pull). Some are already upstream but it appears the
PyrSched.cpp one is not yet.

I'm sorry for causing additional work :(

>>
>> >> The upstream includes boost in the download, and so to be Debian-like,
>> >> we strip that out and use system boost instead. This works in prev
>> >> releases, but in 3.8 (which has updated to use boost 1.63) it errors
>> >> out with confusing compiler/linker problems:
>> >> https://github.com/supercollider/supercollider/issues/3203
>> >>
>> >
>> > I notice you are using wheezy. I'd first try building in sid. BTW, where 
>> > did
>> > you get boost 1.63? Unstable has 1.62...
>>
>> "libboost1.63-dev" etc packages
>
> OK, why did you bump these deps? I don't see any specific requirement
> for 1.63 (at least with a quick grep through the sources).
>

I did not keep this commit in the forced push (but have kept locally
in case it is still needed), because SC built fine without it.


-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Felipe Sateler
On Mon, Sep 25, 2017 at 11:14 AM, Dan S  wrote:
>
> 2017-09-25 13:48 GMT+01:00 Felipe Sateler :
> >
> >
> > On Mon, Sep 25, 2017 at 7:37 AM, Dan S  wrote:
> >>
> >> Hi
> >>
> >> I'm trying to get the new release 3.8 of SuperCollider into the
> >> debian-multimedia repository. I've done an import to git here (not
> >> pushed yet). The problem is SC's dependency on boost.
> >
> >
> > Please push, so that I can try to reproduce locally.
>
> OK, done.

Oh I'm so terribly sorry. I see now that I forgot to push the last
upload, which fixes the FTBFS with gcc 7. I'm now merging your changes
with mine to see if things build. I believe this should fix at least
some problems with newer gcc.

>
> >> The upstream includes boost in the download, and so to be Debian-like,
> >> we strip that out and use system boost instead. This works in prev
> >> releases, but in 3.8 (which has updated to use boost 1.63) it errors
> >> out with confusing compiler/linker problems:
> >> https://github.com/supercollider/supercollider/issues/3203
> >>
> >
> > I notice you are using wheezy. I'd first try building in sid. BTW, where did
> > you get boost 1.63? Unstable has 1.62...
>
> "libboost1.63-dev" etc packages

OK, why did you bump these deps? I don't see any specific requirement
for 1.63 (at least with a quick grep through the sources).




-- 

Saludos,
Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Dan S
2017-09-25 13:48 GMT+01:00 Felipe Sateler :
>
>
> On Mon, Sep 25, 2017 at 7:37 AM, Dan S  wrote:
>>
>> Hi
>>
>> I'm trying to get the new release 3.8 of SuperCollider into the
>> debian-multimedia repository. I've done an import to git here (not
>> pushed yet). The problem is SC's dependency on boost.
>
>
> Please push, so that I can try to reproduce locally.

OK, done.

>> The upstream includes boost in the download, and so to be Debian-like,
>> we strip that out and use system boost instead. This works in prev
>> releases, but in 3.8 (which has updated to use boost 1.63) it errors
>> out with confusing compiler/linker problems:
>> https://github.com/supercollider/supercollider/issues/3203
>>
>
> I notice you are using wheezy. I'd first try building in sid. BTW, where did
> you get boost 1.63? Unstable has 1.62...

"libboost1.63-dev" etc packages

>> The SC team actually have patches applied to their own boost:
>>
>> https://github.com/supercollider/supercollider/blob/develop/external_libraries/boost_sc_changes.patch
>>
>
> This looks unrelated (at least the first part).
>
>>
>> It's possible that using bundled+patched boost would fix these
>> difficulties, though I'm not sure if this would be acceptable.
>> Grateful for any insights.
>
>
> It is possible, but lets first rule out other causes.
>
> --
>
> Saludos,
> Felipe Sateler

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


Re: boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Felipe Sateler
On Mon, Sep 25, 2017 at 7:37 AM, Dan S  wrote:

> Hi
>
> I'm trying to get the new release 3.8 of SuperCollider into the
> debian-multimedia repository. I've done an import to git here (not
> pushed yet). The problem is SC's dependency on boost.
>

Please push, so that I can try to reproduce locally.


>
> The upstream includes boost in the download, and so to be Debian-like,
> we strip that out and use system boost instead. This works in prev
> releases, but in 3.8 (which has updated to use boost 1.63) it errors
> out with confusing compiler/linker problems:
> https://github.com/supercollider/supercollider/issues/3203
>
>
I notice you are using wheezy. I'd first try building in sid. BTW, where
did you get boost 1.63? Unstable has 1.62...


> The SC team actually have patches applied to their own boost:
> https://github.com/supercollider/supercollider/blob/develop/external_
> libraries/boost_sc_changes.patch
>
>
This looks unrelated (at least the first part).


> It's possible that using bundled+patched boost would fix these
> difficulties, though I'm not sure if this would be acceptable.
> Grateful for any insights.
>

It is possible, but lets first rule out other causes.

-- 

Saludos,
Felipe Sateler
___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Re: boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Jonas Smedegaard
Quoting Dan S (2017-09-25 12:37:36)
> The SC team actually have patches applied to their own boost:
> https://github.com/supercollider/supercollider/blob/develop/external_libraries/boost_sc_changes.patch

That patch seems useful to push upstream to Boost developers.

> It's possible that using bundled+patched boost would fix these 
> difficulties, though I'm not sure if this would be acceptable. 

Best is to identify _all_ deviations from pristine Boost, identify for 
each case if it can be upstreamed, and for changes that cannot if those 
can be ignored in Debian, and if not then package a forked Boost 
library.  I.e. *not* sneak in a forked Boost as embedded code copy.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


boost problem while packaging SuperCollider 3.8

2017-09-25 Thread Dan S
Hi

I'm trying to get the new release 3.8 of SuperCollider into the
debian-multimedia repository. I've done an import to git here (not
pushed yet). The problem is SC's dependency on boost.

The upstream includes boost in the download, and so to be Debian-like,
we strip that out and use system boost instead. This works in prev
releases, but in 3.8 (which has updated to use boost 1.63) it errors
out with confusing compiler/linker problems:
https://github.com/supercollider/supercollider/issues/3203

The SC team actually have patches applied to their own boost:
https://github.com/supercollider/supercollider/blob/develop/external_libraries/boost_sc_changes.patch

It's possible that using bundled+patched boost would fix these
difficulties, though I'm not sure if this would be acceptable.
Grateful for any insights.

Best
Dan


https://anonscm.debian.org/cgit/pkg-multimedia/supercollider.git/tree/

___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers