On 11/02/13 23:03, Johan Tibell wrote:
Hi,
I think reducing breakages is not necessarily, and maybe not even
primarily, an issue of releases. It's more about realizing that the cost
of breaking things (e.g. changing library APIs) has gone up as the
Haskell community and ecosystem has grown. We
Thank you.
I thought the no such file lines were the problem. In fact my global
container was hidden some how.
On Tue, Feb 12, 2013 at 5:29 AM, Ian Lynagh i...@well-typed.com wrote:
On Sun, Feb 10, 2013 at 06:35:25PM +0800, Magicloud Magiclouds wrote:
Linuxmint Nadia, ghc-7.6.1 was built
On Wed, Feb 13, 2013 at 12:41 AM, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
./configure --with-gcc=/usr/bin/llvm-gcc
Sorry, I was wrong. with 'with-gcc' option, I got a ld error, which I will
post later.
Without this option, I got native code generator result because the
On 02/12/2013 09:37 AM, Simon Marlow wrote:
On 11/02/13 23:03, Johan Tibell wrote:
Hi,
Of course we do also make well-intentioned changes to libraries, via the
library proposal process, and some of these break APIs. But it wouldn't
do any harm to batch these up and defer them until the next
Hi Magicloud,
Setting build.mk to BuildFlavour = perf-llvm means that the GHC
built will be built using the LLVM backend of GHC.
For any build of GHC though, to *use* the LLVM backend of GHC you
simply want to compile with -fllvm.
The output of inplace/bin/ghc-stage2 �Cinfo won't differ for a
On Tue, Feb 12, 2013 at 11:41 AM, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
Then I `mv build.mk.sample build.mk`, set BuildFlavour = perf-llvm,
add GhcWithLlvmCodeGen = YES. Finally `./configure
--with-gcc=/usr/bin/llvm-gcc`. Configure output attached.
After make, I
Thank you for the replies. These are what I got, correct me if I am wrong:
If I want to build ghc executables and standard libraries, all I need is to
set perf-llvm.
And set perf-llvm or not does not effect the ability of ghc to use llvm.
Then how to check if the output files (executables,
On Tue, Feb 12, 2013 at 1:13 PM, Magicloud Magiclouds
magicloud.magiclo...@gmail.com wrote:
Then how to check if the output files (executables, libraries) are
generated by llvm, instead of gcc? In other words, to see if llvm was used
correct.
I doubt that there is a good way unless
Nothing straight forward to do this. You could do any of:
1) Look at the output of make a GHC is compiled. Verify that by and
large most lines have '-fllvm' on them.
2) As above but pipe output of building GHC to a file. Grep it later
for '-fllvm', you should get a very high count.
3) Add a -v2
On 2/12/13 3:37 AM, Simon Marlow wrote:
One reason for the major version bumps is that base is a big
conglomeration of modules, ranging from those that hardly ever change
(Prelude) to those that change frequently (GHC.*). For example, the new
IO manager that is about to get merged in will force
10 matches
Mail list logo
