On 02/09/10 14:06, Adam D. Barratt wrote:
> On Wed, 2010-09-01 at 09:40 -0400, Felipe Sateler wrote:
>> On 01/09/10 04:10, Reinhard Tartler wrote:
>>> this package has been tried four times and every time we see a different
>>> build error:
>>> #1 (on lebrun): segfault in gcc
>>> #2 (on schroeder): segfault in python (i.e. scons, the build system)
>>> #3 (on lebrun): segfault in gcc, but in a different compilation unit as
>>> #4 (on schroeder): sigill in gcc
>> Please, I'd like to know what to do about this. I have a RC bug on
>> csound (#591802) about this build failure and by this point I think this
>> is not a bug in csound. Note that I have built the package successfully
>> on smetana, and Adrian Knoth also did on a machine of his own. Should I
>> upload the package and close the bug?
> In the short term, uploading the package built on smetana in order to
> allow the package to migrate (possibly with a gentle nudge from britney)
> is ok.
OK, I'm uploading now.
> Longer term, we still need to work out why the package builds happily on
> both porter boxes (having managed to build it successfully myself on
> sperger last night) but not on the buildds, so that we can rebuild it in
> the future for security builds and stable updates.
I think I will need help from sparc-savvy people (or should I say, I can
provide help to sparc-savvy people if necessary? I doubt I have much to
say on the issue).
pkg-multimedia-maintainers mailing list