Re: filename corruption with -osuf in ghc-7.0.3

2012-01-04 Thread Evan Laforge
> In 7.4 we merge the stub object file into the main object file > automatically, so you don't have to worry about stub objects in your > Makefiles or whatever. Nice, this is very convenient. ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@

Re: renamed GMP symbols in GHC

2012-01-04 Thread Matthias Kilian
On Wed, Jan 04, 2012 at 12:31:23PM +, Joachim Breitner wrote: > > One potential problem is that some Linux distributions really don't like > > it if you bundle modified versions of external libraries. However, I > > just don't see a way around this: [...] [...] > I guess this means me... Ind

Re: renamed GMP symbols in GHC

2012-01-04 Thread Joachim Breitner
Hi, Am Mittwoch, den 04.01.2012, 20:50 +0100 schrieb Axel Simon: > On 04.01.2012, at 17:50, Joachim Breitner wrote: > > BTW, Is there a way to get the linker to create two independent copies > > of a library in one program space? Maybe if it is compiled as PIC > > (random name dropping here)? That

Re: renamed GMP symbols in GHC

2012-01-04 Thread Axel Simon
Hi all, On 04.01.2012, at 17:50, Joachim Breitner wrote: > BTW, Is there a way to get the linker to create two independent copies > of a library in one program space? Maybe if it is compiled as PIC > (random name dropping here)? That would seem to be an elegant solution, > as it makes the distro

Re: renamed GMP symbols in GHC

2012-01-04 Thread Brandon Allbery
On Wed, Jan 4, 2012 at 11:50, Joachim Breitner wrote: > Now you might argue that gmp will never be the source of security > problems (although I woudn’t be too convinced about that). But even then > There's actually a patch for a (claimed to be minor potential) security issue referenced on the r

Re: renamed GMP symbols in GHC

2012-01-04 Thread Joachim Breitner
Dear Michal, Am Mittwoch, den 04.01.2012, 16:33 + schrieb Michal Konečný: > On Wednesday 04 January 2012 12:31:23 Joachim Breitner wrote: > > I guess this means me... Indeed Debian has the policy to avoid modified > > bundled libraries, if somehow possible. For example, we patch the build > >

Re: renamed GMP symbols in GHC

2012-01-04 Thread Brandon Allbery
2012/1/4 Michal Konečný > On Wednesday 04 January 2012 12:21:13 Simon Marlow wrote: > > GMP is inherently broken because it > > has global state, so if you want two use it from two clients in the same > > program, you need two copies of it. > > If this could be fixed that would be fantastic. Nev

Re: renamed GMP symbols in GHC

2012-01-04 Thread Michal Konečný
Dear Joachim and Simon, Thank you for your responses. On Wednesday 04 January 2012 12:31:23 Joachim Breitner wrote: > I guess this means me... Indeed Debian has the policy to avoid modified > bundled libraries, if somehow possible. For example, we patch the build > system to use the system-provid

Re: renamed GMP symbols in GHC

2012-01-04 Thread Joachim Breitner
[Fullquote for the benefit of those on the Debian Haskell list.] Dear Simon, Am Mittwoch, den 04.01.2012, 12:21 + schrieb Simon Marlow: > On 22/12/2011 22:58, Michal Konečný wrote: > > Several issues related to the way GMP is included in GHC were publicly > > discussed in the past with the go

Re: renamed GMP symbols in GHC

2012-01-04 Thread Simon Marlow
On 22/12/2011 22:58, Michal Konečný wrote: Several issues related to the way GMP is included in GHC were publicly discussed in the past with the goal of replacing GMP. As summarised in this wiki by Peter Tanski , the main issues were:

Re: Records in Haskell

2012-01-04 Thread Greg Weber
The Frege author does not have a ghc mail list account but gave a more detailed explanation of how he goes about TDNR for records and how often it type checks without annotation in practice. A more general explanation is here: http://www.reddit.com/r/haskell/comments/nph9l/records_stalled_again_le

Re: ANNOUNCE: GHC 7.4.1 Release Candidate 1

2012-01-04 Thread Simon Marlow
On 03/01/2012 16:54, Tristan Ravitch wrote: This might be the expected behavior but I'll ask anyway. I have what seems to be a legitimate stack overflow (due to excessive recursion and not the evaluation of a big thunk). The stack trace from -xc only shows about 13 calls on the stack (with eac