From: brettg@posteo.net
To: Sergiu Marton <brown121407@gmail.com>
Cc: 38782@debbugs.gnu.org,
bug-Guix <bug-guix-bounces+brettg=posteo.net@gnu.org>,
Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: bug#38782: portaudio fails to build
Date: Sun, 29 Dec 2019 10:36:25 +0100 [thread overview]
Message-ID: <c7932d5d12c42f0e9984f4ca2230569e@posteo.net> (raw)
In-Reply-To: <CAJ=hFwQF-MJb92=X5UQvRktCoPkS7sir7zJYGMTTL-davLCFkQ@mail.gmail.com>
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@nicolasgoaziou.fr> wrote:
>>
>> Hello,
>>
>> Sergiu Marton <brown121407@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
next prev parent reply other threads:[~2019-12-29 9:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-28 21:48 bug#38782: portaudio fails to build Sergiu Marton
2019-12-28 23:08 ` Ricardo Wurmus
2019-12-29 7:48 ` Sergiu Marton
2019-12-29 8:43 ` Nicolas Goaziou
2019-12-29 8:59 ` Sergiu Marton
2019-12-29 9:36 ` brettg [this message]
2019-12-29 9:43 ` Nicolas Goaziou
2019-12-29 9:45 ` brettg
2019-12-29 10:07 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c7932d5d12c42f0e9984f4ca2230569e@posteo.net \
--to=brettg@posteo.net \
--cc=38782@debbugs.gnu.org \
--cc=brown121407@gmail.com \
--cc=bug-guix-bounces+brettg=posteo.net@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).