Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)

To: Thorsten Glaser <tg@mirbsd.de>
Cc: buildd on ara5 for m68k <buildd@ara5.mirbsd.org>, debian-68k@lists.debian.org, Tiago Bortoletto Vaz <tiago@debian.org>, Toby Smithe <tsmithe@ubuntu.com>
Subject: Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
From: Andreas Schwab <schwab@linux-m68k.org>
Date: Mon, 22 Jun 2015 22:22:04 +0200
Message-id: <[🔎] 871th3sdcj.fsf@igel.home>
In-reply-to: <[🔎] Pine.BSM.4.64L.1506221905060.32246@herc.mirbsd.org> (Thorsten Glaser's message of "Mon, 22 Jun 2015 19:06:56 +0000 (UTC)")
References: <20150621032839.65E0C14E@ara5.mirbsd.org> <[🔎] Pine.BSM.4.64L.1506221905060.32246@herc.mirbsd.org>

Thorsten Glaser <tg@mirbsd.de> writes:

> fail
>
> http://buildd.debian-ports.org/status/fetch.php?pkg=musescore&arch=m68k&ver=2.0.1%2Bdfsg-1&stamp=1434857325
>
> tbh I have no idea what went wrong there…

Easy.

$ grep -c processor /proc/cpuinfo 
0
$ make -j 0
make: the '-j' option requires a positive integer argument

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Reply to:

Follow-Ups:
- Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
  - From: Tiago Bortoletto Vaz <tiago@debian.org>

References:
- Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
  - From: Thorsten Glaser <tg@mirbsd.de>

Prev by Date: Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
Next by Date: Re: Log for attempted build of musescore_2.0.1+dfsg-2 on m68k (dist=unstable)
Previous by thread: Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
Next by thread: Re: Log for attempted build of musescore_2.0.1+dfsg-1 on m68k (dist=unstable)
Index(es):
- Date
- Thread