Send Beginners mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://www.haskell.org/mailman/listinfo/beginners
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Beginners digest..."
Today's Topics:
1. cabal -j (harry)
2. Re: cabal -j (Brandon Allbery)
3. Re: cabal -j (gs)
4. Re: cabal -j (Brent Yorgey)
5. Re: cabal -j (Guy)
6. Re: cabal -j (Krzysztof Skrz?tnicki)
----------------------------------------------------------------------
Message: 1
Date: Sun, 5 May 2013 13:44:36 +0000 (UTC)
From: harry <[email protected]>
Subject: [Haskell-beginners] cabal -j
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
I've noticed that cabal install now has a -j option for parallel builds, and
has to be told how many builds to run in parallel. This seems strange - most
parallel capable systems run in parallel by default, with one process/thread
per core. Why is cabal different?
------------------------------
Message: 2
Date: Sun, 5 May 2013 10:35:12 -0400
From: Brandon Allbery <[email protected]>
Subject: Re: [Haskell-beginners] cabal -j
To: The Haskell-Beginners Mailing List - Discussion of primarily
beginner-level topics related to Haskell <[email protected]>
Message-ID:
<CAKFCL4WTB9dTEZYQO_hUt9N-Tde6_roKPcbBq=jyakb+wsq...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Sun, May 5, 2013 at 9:44 AM, harry <[email protected]> wrote:
> I've noticed that cabal install now has a -j option for parallel builds,
> and
> has to be told how many builds to run in parallel. This seems strange -
> most
> parallel capable systems run in parallel by default, with one
> process/thread
> per core. Why is cabal different?
>
Not that different; make doesn't run parallel by default either (see make
-j).
--
brandon s allbery kf8nh sine nomine associates
[email protected] [email protected]
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.haskell.org/pipermail/beginners/attachments/20130505/3aa72a1e/attachment-0001.htm>
------------------------------
Message: 3
Date: Sun, 5 May 2013 18:10:25 +0000 (UTC)
From: gs <[email protected]>
Subject: Re: [Haskell-beginners] cabal -j
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Brandon Allbery <allbery.b <at> gmail.com> writes:
> Not that different; make doesn't run parallel by default either (see make
-j).?
Does cabal -j also suffer from interleaved output? And will it be possible
to set e.g. -j12 as the default?
------------------------------
Message: 4
Date: Sun, 5 May 2013 14:38:44 -0400
From: Brent Yorgey <[email protected]>
Subject: Re: [Haskell-beginners] cabal -j
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=iso-8859-1
On Sun, May 05, 2013 at 06:10:25PM +0000, gs wrote:
> Brandon Allbery <allbery.b <at> gmail.com> writes:
>
> > Not that different; make doesn't run parallel by default either (see make
> -j).?
>
> Does cabal -j also suffer from interleaved output?
No; when the -j flag is turned on it uses an abbreviated output format
that just tells you *what* it is doing (downloading XYZ package,
configuring foo, building baz...) but not the details, with the
details going to a separate log file for each package. There may soon
also be a way to use it with hydra-print which could be nice.
> And will it be possible
> to set e.g. -j12 as the default?
Yes, edit your ~/.cabal/config and add/uncomment the line
jobs: 12
-Brent
------------------------------
Message: 5
Date: Mon, 06 May 2013 09:14:59 +0300
From: Guy <[email protected]>
Subject: Re: [Haskell-beginners] cabal -j
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Brent Yorgey wrote:
> No; when the -j flag is turned on it uses an abbreviated output format
> that just tells you *what* it is doing (downloading XYZ package,
> configuring foo, building baz...) but not the details, with the
> details going to a separate log file for each package. There may soon
> also be a way to use it with hydra-print which could be nice.
So if there aren't any downsides, why not make it the default?
------------------------------
Message: 6
Date: Mon, 6 May 2013 09:10:36 +0200
From: Krzysztof Skrz?tnicki <[email protected]>
Subject: Re: [Haskell-beginners] cabal -j
To: The Haskell-Beginners Mailing List - Discussion of primarily
beginner-level topics related to Haskell <[email protected]>
Message-ID:
<cam7aevhn12wq+z8kaqft6jghkj1+pwokpg7t0jqoz8a6nzj...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
For sure one downside is that the output is less verbose (you wouldn't
see anything otherwise) and buffered; in case of an error only last 10
or so lines are printed which makes it harder to debug. When I
encounter such problem I always rerun the build without -j to see the
actual problem in full.
Unexperienced users would have much problem with this.
Best regards,
Krzysztof Skrz?tnicki
On Mon, May 6, 2013 at 8:14 AM, Guy <[email protected]> wrote:
> Brent Yorgey wrote:
>>
>> No; when the -j flag is turned on it uses an abbreviated output format
>> that just tells you *what* it is doing (downloading XYZ package,
>> configuring foo, building baz...) but not the details, with the
>> details going to a separate log file for each package. There may soon
>> also be a way to use it with hydra-print which could be nice.
>
>
> So if there aren't any downsides, why not make it the default?
>
>
>
>
> _______________________________________________
> Beginners mailing list
> [email protected]
> http://www.haskell.org/mailman/listinfo/beginners
------------------------------
_______________________________________________
Beginners mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/beginners
End of Beginners Digest, Vol 59, Issue 6
****************************************
