GNU bug report logs -
#38782
portaudio fails to build
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 38782 in the body.
You can then email your comments to 38782 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sat, 28 Dec 2019 21:48:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Sergiu Marton <brown121407 <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Sat, 28 Dec 2019 21:48:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I have mpv installed, which depends on rsound, which, in turn, depends
on portaudio. Since my last guix pull, portaudio fails to build - it
fails during the build phase. I attached the build log. I tried
reading it, but I don't know what to make of it.
[portaudio-log.bz2 (application/octet-stream, attachment)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sat, 28 Dec 2019 23:09:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 38782 <at> debbugs.gnu.org (full text, mbox):
Sergiu Marton <brown121407 <at> gmail.com> writes:
> I have mpv installed, which depends on rsound, which, in turn, depends
> on portaudio. Since my last guix pull, portaudio fails to build - it
> fails during the build phase. I attached the build log. I tried
> reading it, but I don't know what to make of it.
I have been able to build it locally. I suppose the problem might be
with parallel building. Disabling parallel builds for the portaudio
package might fix this.
--
Ricardo
Reply sent
to
Sergiu Marton <brown121407 <at> gmail.com>
:
You have taken responsibility.
(Sun, 29 Dec 2019 07:49:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Sergiu Marton <brown121407 <at> gmail.com>
:
bug acknowledged by developer.
(Sun, 29 Dec 2019 07:49:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 38782-done <at> debbugs.gnu.org (full text, mbox):
> I have been able to build it locally. I suppose the problem might be
> with parallel building. Disabling parallel builds for the portaudio
> package might fix this.
It built just fine with --cores=1 --max-jobs=1. Thanks!
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 08:45:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 38782 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello,
Sergiu Marton <brown121407 <at> gmail.com> writes:
>> I have been able to build it locally. I suppose the problem might be
>> with parallel building. Disabling parallel builds for the portaudio
>> package might fix this.
>
> It built just fine with --cores=1 --max-jobs=1. Thanks!
Would the following patch fix the issue then?
Regards,
--
Nicolas Goaziou
[0001-gnu-portaudio-Fix-build.patch (text/x-diff, inline)]
From 8acdc1540661bc80e8c724f29b6b162ccfb3307e Mon Sep 17 00:00:00 2001
From: Nicolas Goaziou <mail <at> nicolasgoaziou.fr>
Date: Sun, 29 Dec 2019 09:36:44 +0100
Subject: [PATCH] gnu: portaudio: Fix build.
* gnu/packages/audio.scm (portaudio)[arguments]: Build sequentially.
Fixes <https://bugs.gnu.org/38782>. This is a follow-up to commit
1ce6bfc21ce328d787df76c6ee132f9f828d098b.
---
gnu/packages/audio.scm | 1 +
1 file changed, 1 insertion(+)
diff --git a/gnu/packages/audio.scm b/gnu/packages/audio.scm
index 204ea6acf0..a76a48d4c6 100644
--- a/gnu/packages/audio.scm
+++ b/gnu/packages/audio.scm
@@ -2874,6 +2874,7 @@ portions of LAME.")
("pkg-config" ,pkg-config)))
(arguments
'(#:tests? #f ;no 'check' target
+ #:parallel-build? #f
#:configure-flags '("--with-pic"
"--enable-cxx"
;; XXX: The following prevents a build error
--
2.24.1
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 09:00:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 38782 <at> debbugs.gnu.org (full text, mbox):
> Would the following patch fix the issue then?
That fixes it without requiring extra CLI arguments. Nice, thanks.
On Sun, Dec 29, 2019 at 8:44 AM Nicolas Goaziou <mail <at> nicolasgoaziou.fr> wrote:
>
> Hello,
>
> Sergiu Marton <brown121407 <at> gmail.com> writes:
>
> >> I have been able to build it locally. I suppose the problem might be
> >> with parallel building. Disabling parallel builds for the portaudio
> >> package might fix this.
> >
> > It built just fine with --cores=1 --max-jobs=1. Thanks!
>
> Would the following patch fix the issue then?
>
> Regards,
>
> --
> Nicolas Goaziou
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 09:37:01 GMT)
Full text and
rfc822 format available.
Message #22 received at 38782 <at> debbugs.gnu.org (full text, mbox):
On 29.12.2019 09:59, Sergiu Marton wrote:
>> Would the following patch fix the issue then?
>
> That fixes it without requiring extra CLI arguments. Nice, thanks.
>
> On Sun, Dec 29, 2019 at 8:44 AM Nicolas Goaziou
> <mail <at> nicolasgoaziou.fr> wrote:
>>
>> Hello,
>>
>> Sergiu Marton <brown121407 <at> gmail.com> writes:
>>
>> >> I have been able to build it locally. I suppose the problem might be
>> >> with parallel building. Disabling parallel builds for the portaudio
>> >> package might fix this.
>> >
>> > It built just fine with --cores=1 --max-jobs=1. Thanks!
>>
>> Would the following patch fix the issue then?
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
I would personally comment the reason for disabling parallel builds and
affix this bug number to the commit sub-header message. I am at work
right now, so I lack the ability to do this myself at the moment. But if
I get home and this issue is still open, I will do it. It's up for grabs
if somebody beats me to it.
Best,
Brett Gilio
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 09:44:02 GMT)
Full text and
rfc822 format available.
Message #25 received at 38782 <at> debbugs.gnu.org (full text, mbox):
Hello,
brettg <at> posteo.net writes:
> I would personally comment the reason for disabling parallel builds
You mean as a comment in the package definition? I checked other
definitions, comments in this situation, if any, are terse. E.g.,
";fails on some systems".
> and affix this bug number to the commit sub-header message.
I added the bug reference to the commit message. Do you mean it should
be moved right after the commit title (separated by a blank line)?
Regards,
--
Nicolas Goaziou
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 09:46:01 GMT)
Full text and
rfc822 format available.
Message #28 received at 38782 <at> debbugs.gnu.org (full text, mbox):
On 29.12.2019 10:43, Nicolas Goaziou wrote:
> Hello,
>
> brettg <at> posteo.net writes:
>
>> I would personally comment the reason for disabling parallel builds
>
> You mean as a comment in the package definition? I checked other
> definitions, comments in this situation, if any, are terse. E.g.,
> ";fails on some systems".
>
>> and affix this bug number to the commit sub-header message.
>
> I added the bug reference to the commit message. Do you mean it should
> be moved right after the commit title (separated by a blank line)?
>
> Regards,
On a second look, your commit message is fine. And the `; fails on some
systems` seems fine to me. Sorry, I am quite sleep deprived right now.
:)
Best,
Brett Gilio
Information forwarded
to
bug-guix <at> gnu.org
:
bug#38782
; Package
guix
.
(Sun, 29 Dec 2019 10:09:02 GMT)
Full text and
rfc822 format available.
Message #31 received at 38782 <at> debbugs.gnu.org (full text, mbox):
brettg <at> posteo.net writes:
> On 29.12.2019 10:43, Nicolas Goaziou wrote:
>> Hello,
>>
>> brettg <at> posteo.net writes:
>>
>>> I would personally comment the reason for disabling parallel builds
>>
>> You mean as a comment in the package definition? I checked other
>> definitions, comments in this situation, if any, are terse. E.g.,
>> ";fails on some systems".
>>
>>> and affix this bug number to the commit sub-header message.
>>
>> I added the bug reference to the commit message. Do you mean it should
>> be moved right after the commit title (separated by a blank line)?
>>
>> Regards,
>
> On a second look, your commit message is fine. And the `; fails on
> some systems` seems fine to me. Sorry, I am quite sleep deprived right
> now. :)
Great. I applied the patch. All the credit goes to Ricardo Wurmus for
the fix.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 26 Jan 2020 12:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 4 years and 63 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.