Build description = HEAD on i386-unknown-linux
(cam-02-unx.europe.corp.microsoft.com)
Build location= /playpen/ghc/nightly/HEAD-cam-02-unx
Build config file = /home/simonmar/nightly/site/msrc/conf-HEAD-cam-02-unx
Nightly build started on cam-02-unx at Tue May 29 19:30:01 BST 2007.
checki
On Tue, May 29, 2007 at 09:01:56PM +0100, Malcolm Wallace wrote:
> Ian Lynagh <[EMAIL PROTECTED]> writes:
>
> > We have several Haskell XML libraries, so we ought to be able to do it
> > properly
>
> There already exists an XML-aware grep-like tool, called Xtract, in
> HaXml. :-)
I wasn't CCing
Fri May 25 09:43:08 PDT 2007 [EMAIL PROTECTED]
* refactor: combine repeated code in file reloading
M ./compiler/ghci/InteractiveUI.hs -7 +2
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Fri May 25 09:31:04 PDT 2007 [EMAIL PROTECTED]
* Changes the behavior of the "edit" command in GHCi.
Currently, when the user invokes the GHCi editor without a parameter
GHCi chooses the last file that loaded _sucessfully_.
This patch changes this behavior to start the editor with the
la
Ian Lynagh <[EMAIL PROTECTED]> writes:
> > How about removing --xml-output and:
> > | grep '^ \* ' | head -n 1 | sed 's| \* ||'
> > (`head` just in case the detailed text has a line starting with "* ")
Note that in the textual output of 'darcs changes', inverted patches
(i.e. made with 'da
On Tue, May 29, 2007 at 01:04:42PM -0400, Isaac Dupree wrote:
>
> Malcolm Wallace wrote:
> >
> > That would be /home/simonmar/bin/commit-messages-split.sh, which does this:
> >
> > patchname=$(${DARCS} changes\
> > --matches="hash ${patch}" \
> > --x
On 5/29/2007 10:04, Isaac Dupree wrote:
...
Or get the second line (is there a better shell way?) :
| head -n 2 | tail -n 1 | sed 's| \* ||'
sed -n 2p ?
--sigbjorn
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/
Malcolm Wallace wrote:
> Ian Lynagh <[EMAIL PROTECTED]> wrote:
>
>>> It would be nice if whatever generates these "patch applied" e-mails
>>> wouldn't replace perfectly fine characters in the e-mail subjects
>>> with the XML entity "equivalents" & gt; & apos; , etc.
>> If someone (you?) wants to
On Tue, May 29, 2007 at 09:33:54AM -0700, Andy Gill wrote:
>
> My suggestion (after taking input from #ghc and #darcs) is
> * Having a web page that contains the contexts (or hash numbers)
> of the various darcs repos that went into making the latest
> good build.
> * This page also contains
Ian Lynagh <[EMAIL PROTECTED]> wrote:
> > It would be nice if whatever generates these "patch applied" e-mails
> > wouldn't replace perfectly fine characters in the e-mail subjects
> > with the XML entity "equivalents" & gt; & apos; , etc.
>
> If someone (you?) wants to track down what's causing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy Gill wrote:
> Hi Simon,
>
> I understand the need to have a HEAD that works most of the time.
>
> But the question "How do I get a recent copy of HEAD, that works(*)"
> seems reasonable.
> I wanted to fellow galois engineer to try something in H
On Mon, May 28, 2007 at 10:13:57PM +1000, Gabriele Keller wrote:
> I had a serious problem building ghc head under Intel MacOS today. The
> first problem was that the FIND makefile var wasn't initialized
> properly.
Can you please send me config.log?
Also, what do these commands say?:
* which
Hi Simon,
I understand the need to have a HEAD that works most of the time.
But the question "How do I get a recent copy of HEAD, that works(*)"
seems reasonable.
I wanted to fellow galois engineer to try something in HEAD, and he
needed to give
up before he got a working build.
(*) where w
Sat May 26 07:31:51 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* Add parser/should_run
A ./tests/ghc-regress/parser/should_run/
A ./tests/ghc-regress/parser/should_run/Makefile
A ./tests/ghc-regress/parser/should_run/all.T
___
Cvs-ghc mail
Sat May 26 07:38:14 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* #1318: pre-emptively add test for Haskell98 treatment of operator "-"
M ./tests/ghc-regress/parser/should_run/all.T +4
A ./tests/ghc-regress/parser/should_run/read001.hs
A ./tests/ghc-regress/parser/should_run/read001.s
Sat May 26 15:44:05 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* add negative-prim-literal tests
the first for behavior common between their new and old parsings (passes
both),
the second to test the new behavior (fails before, passes after)
M ./tests/ghc-regress/parser/should_run/all.T
On Tue, May 29, 2007 at 10:06:04AM -0400, Isaac Dupree wrote:
>
> It would be nice if whatever generates these "patch applied" e-mails
> wouldn't replace perfectly fine characters in the e-mail subjects with
> the XML entity "equivalents" & gt; & apos; , etc. The subject lines
> aren't XML or eve
Tue May 29 08:28:48 PDT 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Update Windows installation docs
M ./docs/users_guide/installing.xml -41 +23
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
| > Nevertheless, I don't think I am alone. For example, not long ago I met
| > Andy Gill in #ghc trying to find a version of the head that's fairly
| > recent and still builds.
| >
| > So, let me make a suggestion. Could the changes to the build system
| > maybe done on a branch of the repos and
Isaac Dupree wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Mitchell wrote:
Hi
Okay, what is the meaning of this error I'm getting repeatedly, trying
to push the testsuite patches:
Waiting for lock /srv/darcs/testsuite/_darcs/lock
Waiting for lock /srv/darcs/testsuite/_darcs/lock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Neil Mitchell wrote:
> Hi
>
>> Okay, what is the meaning of this error I'm getting repeatedly, trying
>> to push the testsuite patches:
>>
>> Waiting for lock /srv/darcs/testsuite/_darcs/lock
>> Waiting for lock /srv/darcs/testsuite/_darcs/lock
>
> U
Tue May 29 10:34:52 EDT 2007 Ian Lynagh <[EMAIL PROTECTED]>
* *Really* fix the copy-and-paste-o
M ./download_ghc_661.html -1 +1
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Tue May 29 10:33:01 EDT 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Fix copy-and-paste-o
M ./download_ghc_661.html -1 +1
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Hi
Okay, what is the meaning of this error I'm getting repeatedly, trying
to push the testsuite patches:
Waiting for lock /srv/darcs/testsuite/_darcs/lock
Waiting for lock /srv/darcs/testsuite/_darcs/lock
Usually means you ran a darcs push and aborted before the end. If you
aren't running dar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Marlow wrote:
> The patches look fine, go ahead and push.
Okay, what is the meaning of this error I'm getting repeatedly, trying
to push the testsuite patches:
Waiting for lock /srv/darcs/testsuite/_darcs/lock
Waiting for lock /srv/darcs/testsu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It would be nice if whatever generates these "patch applied" e-mails
wouldn't replace perfectly fine characters in the e-mail subjects with
the XML entity "equivalents" & gt; & apos; , etc. The subject lines
aren't XML or even HTML (the bodies of the
Sat May 26 16:00:45 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* #1318: lex negative unboxed literals
I reorganized the lexing of numeric literals a bit so the code didn't
get too ugly, after trying a few ways, and also considering possible plans
to be able to conditionally lex negative _bo
Sat May 26 14:50:42 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* #1318: remove negative-prim-literal old hackish implementation
M ./compiler/parser/Parser.y.pp -1 +1
M ./compiler/parser/RdrHsSyn.lhs -15 +2
___
Cvs-ghc mailing list
Cvs-ghc@hask
Sat May 26 14:22:04 PDT 2007 Isaac Dupree <[EMAIL PROTECTED]>
* parseInteger->parseUnsignedInteger to clarify meaning
I decided against adding parseSignedInteger since octal
and hex literals often have junk between the '-' and the
digits, but, compare to Util.readRational which does handle
Manuel M T Chakravarty wrote:
In the last couple of weeks I spent a lot of time just trying to compile
GHC. With the constantly changing build system, incremental builds fail
more often than not after new patches are pulled. And sometimes even
clean builds don't work. For example, today (tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon Marlow wrote:
> The patches look fine, go ahead and push.
Ok, thanks, I will.
Isaac
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGXC38HgcxvIWYTTURAnuzAKC5
Isaac Dupree wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isaac Dupree wrote:
Unfortunately "add negative-prim-literal tests" (according to darcs)
depends on "#1318: pre-emptively add test for..."; either the patches
could be reworked, or we could just get that one reviewed and fixed up
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Isaac Dupree wrote:
> Unfortunately "add negative-prim-literal tests" (according to darcs)
> depends on "#1318: pre-emptively add test for..."; either the patches
> could be reworked, or we could just get that one reviewed and fixed up
> first/simultan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Malcolm Wallace wrote:
> Isaac Dupree <[EMAIL PROTECTED]> wrote:
>
>> know how close GHC's stage1 code
>> is to compilability with other compilers?
>
> AFAIK, ghc's source code primarily uses only two main extensions beyond
> the Haskell language - u
Tue May 29 03:21:43 PDT 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Build Windows installer when making a bindist if ISCC is set
It doesn't work yet, but I'm pretty sure that's because the bindist is
broken rather than the installer is broken.
M ./Makefile -3 +28
A ./distrib/ghc.iss
A
Tue May 29 06:02:54 EDT 2007 Ian Lynagh <[EMAIL PROTECTED]>
* Fix "Porting GHC" link to point at the wiki
It was still pointing to the building guide docs, which aren't included
any more.
M ./download_ghc_661.html -1 +1
___
Cvs-ghc mailing li
Tue May 29 00:42:24 PDT 2007 Simon Marlow <[EMAIL PROTECTED]>
* don't build the threaded RTS when GhcUnregisterised=YES
M ./mk/config.mk.in -3 +9
___
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
Build results:
x86-64 Linux head: lost
x86 Windows head:pass
x86 Windows head fast: pass pass pass pass pass pass
x86-64 Linux head unreg: fail (failed stage1)
Dropping unexpected test passes reports from builders not seen in 7 days:
x86-64 Linux head
Fixed unexpected test pa
38 matches
Mail list logo
