https://ghc.haskell.org/trac/ghc/wiki/WindowsGhc that link should be
>> used instead of the WindowsTaskForce link directly.
>>
>> @Darren & Martin, would you also like to be added to the page?
>>
>> Regards,
>> Tamar
>>
>> *From:* Roman Kuznetsov
>&
gt; To: Darren Grant ; Mikolaj Konarski
>
> Cc: Phyx ; Roman Kuznetsov ;
> ghc-devs@haskell.org; David Macek ; kyrab
> ; Gintautas Miliauskas ; Martin
> Foster
> Subject: RE: Resolving Windows 64-bit linker issues
>
> One really helpful thing would be to
>
> ·
nk. It's
on the heavy side (92MB) and would probably need to be trimmed beforehand
though.
Are there any utilities other than ghc-split which rely on perl at ghc
runtime? If not, are there any plans to convert ghc-split to a sane
language? I would sign up if I knew I would have the time.
; but does not cause any harm (for some reason) so it is basically
> > invisible.
> >
> > However, first it would be nice if somebody else could confirm that it
> > is indeed the case.
>
> Yeah, for what it is worth, this also happens on my FreeBSD
Hey,
I'm on vacation right now without access to my workstation, I will be back
in a couple weeks.
I believe hvr@ was having some stability issues too, maybe he can help
reproduce the problem?
Thanks for looking into this.
--
Gintautas Miliauskas
On Nov 10, 2014 6:24 PM, "David Mac
but it did not
help, 4/8 validation runs segfaulted (-j5).
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
T5435_dyn_asm [bad stdout] (normal)
> >rtsT7037 [bad stdout] (normal)
> >rts T8124 [exit code non-0] (threaded1)
> >rtsrdynamic [bad exit code] (normal)
> >sim
Oh, and David, thanks for your help. It's really appreciated. This issue
has been driving me nuts recently, and I don't have a good strategy to root
it out...
On Tue, Nov 4, 2014 at 11:23 PM, David Macek
wrote:
> On 4. 11. 2014 23:20, Gintautas Miliauskas wrote:
> > ghc shoul
ope it helps somehow. Maybe your issues come from mixing msys2 and
> mingw toolchain after all.
>
>
>
> --
> David Macek
>
>
> --
> ___
> Msys2-users mailing li
I'm using /usr/bin/perl, and don't have the mingw perl installed.
On Tue, Nov 4, 2014 at 4:10 PM, David Macek wrote:
> On 4. 11. 2014 14:14, Gintautas Miliauskas wrote:
> > I'm working on ghc trunk.
>
> I'm trying to reproduce your errors, but I
irst
position to make sure that the right DLLs are, I still got a few segfaults,
so this is probably not it.
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
can't find what source version you're
> using, Gintautas. Release/trunk?
>
> --
> David Macek
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs
>
--
Gintautas Miliaus
thing,
regardless of the value of the MSYS variable:
$ /usr/bin/gcc -o crash crash.c
$ ./crash.exe
hi
$ echo $?
0
On Tue, Nov 4, 2014 at 1:56 AM, Ray Donnelly
wrote:
> On Tue, Nov 4, 2014 at 12:45 AM, Gintautas Miliauskas
> wrote:
> > I have a suspicion that the segmentation faults a
rget 'maintainer-clean' failed
Closing and reopening the msys2 console seems to help - for some time.
On Tue, Nov 4, 2014 at 1:30 AM, Ray Donnelly
wrote:
> On Mon, Nov 3, 2014 at 11:07 PM, Gintautas Miliauskas
> wrote:
> > +ghc-devs
> >
> > Hi Ray,
> >
ue is thus
unlikely to be somewhere deep in ghc, it's either on the surface or in
msys2. There could be a problem with our gcc build, but other compiler
versions crash too, so I don't think that's it.
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
Nice!
This needs a host ghc (with alex and happy) preinstalled, correct?
On Tue, Nov 4, 2014 at 12:55 AM, David Macek
wrote:
> On 4. 11. 2014 0:07, Gintautas Miliauskas wrote:
> > A PKGBUILD for ghc should be feasible, although the bootstrapping is a
> bit tricky (some Haskell tool
sure how
useful it would be since for Windows there is already a nicely packaged
native Haskell Platform installer.
On Mon, Nov 3, 2014 at 3:30 AM, Ray Donnelly
wrote:
> On Sun, Nov 2, 2014 at 11:45 PM, Gintautas Miliauskas
> wrote:
> > Hello,
> >
> > I have been worki
Potentially related issues:
https://github.com/haskell/cabal/issues/1698
https://ghc.haskell.org/trac/ghc/ticket/2924
https://ghc.haskell.org/trac/ghc/ticket/3231
https://ghc.haskell.org/trac/ghc/ticket/2650
On Mon, Nov 3, 2014 at 1:24 AM, Gintautas Miliauskas <
gintautas.miliaus...@gmail.
l.org/ghc/reportabug
libraries/base/ghc.mk:4: recipe for target
'libraries/base/dist-install/build/GHC/TypeLits.o' failed
I may have been building in a non-clean repository after a git pull though,
could that have caused this?
--
Gintautas Miliauskas
__
(Aaand I messed up the initial calendar invitation. It should be set to the
correct time now, 8pm UTC.)
On Mon, Nov 3, 2014 at 3:12 PM, Gintautas Miliauskas <
gintautas.miliaus...@gmail.com> wrote:
>
> Alright, based on the votes let's do Wednesday (Nov 5) 8:00pm.
>>
>
> Alright, based on the votes let's do Wednesday (Nov 5) 8:00pm.
>
Sorry, forgot to specify the timezone: 8:00pm UTC.
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
ess
or something else.
If any of the involved paths is a directory, this could be #8482
<https://ghc.haskell.org/trac/ghc/ticket/8482>, although that does not seem
to be the case.
On Thu, Oct 30, 2014 at 7:13 PM, Páli Gábor János
wrote:
> 2014-10-30 16:24 GMT+01:00 Gintautas Miliauskas
e flags
--extra-include-dirs= and --extra-lib-dirs= to specify where it is.
If the header file does exist, it may contain errors that are caught by the
C
compiler at the preprocessing stage. In this case you can re-run configure
with the verbosity flag -v3 to see the error messages.
--
Ginta
ead?) Is it really significant? If it is, can we split off
related tests? If it isn't, let's just enable them by default.
On Thu, Oct 30, 2014 at 10:19 PM, Austin Seipp
wrote:
> On Thu, Oct 30, 2014 at 6:48 AM, Gintautas Miliauskas
> wrote:
> > Going through some vali
g
> patches every day sound? This is normally very trivial amounts of time
> these days, considering Phabricator tends to catch the most obvious
> failures.
>
> BTW: I merged your pull request on the Win32 repository, so we can
> update MinGW - I didn't realize that it
r and more portable.
Looking forward to seeing everyone!
I will try to take notes of the meeting and send them to the mailing list
afterwards.
On Thu, Oct 30, 2014 at 9:03 PM, Gintautas Miliauskas <
gintautas.miliaus...@gmail.com> wrote:
> Updated.
>
> Note that I'm on vacation st
t;
> I also think this is a good idea.
>
https://phabricator.haskell.org/D406
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
; Kind Regards,
> Tamar
>
> *From:* Gintautas Miliauskas
> *Sent:* Thursday, October 30, 2014 16:34
> *To:* Simon Peyton Jones
> *Cc:* kyra , ghc-devs@haskell.org
>
>
>
> On Tue, Oct 28, 2014 at 11:02 PM, Simon Peyton Jones <
> simo...@microsoft.com> w
7;s try that. Shall we try to find a good timeslot? Sign up at
http://doodle.com/34e598zc7m8sbaqm
--
Gintautas Miliauskas <http://doodle.com/34e598zc7m8sbaqm>
<http://doodle.com/34e598zc7m8sbaqm>
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
:49 GMT+01:00 Gintautas Miliauskas :
> > Can you try running the offending command with -v to see which step
> > breaks?
>
> I have tried it, even together with building the GHC sources with a
> recent toolchain, but I did not get much forward.
>
> > I tried running it lo
t not good enough")? The latter
are important, but they seem to be much more prone to fail without good
reason. Perhaps do some color coding of the test runner output? That would
also help.
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
https://phabricator.haskell.org/D400
On Mon, Oct 27, 2014 at 1:34 PM, Gintautas Miliauskas <
gintau...@miliauskas.lt> wrote:
> FYI, after the fix ghc builds again on Windows 32-bit, but validate.sh
> fails:
>
> rts\Linker.c: In function 'allocateImageAndTrampolines
uld willingly cede maintainership of Win32. I’m copying
> him. Bryan?
>
>
>
> *From:* Herbert Valerio Riedel [mailto:hvrie...@gmail.com]
> *Sent:* 29 October 2014 12:47
> *To:* Gintautas Miliauskas
> *Cc:* Phyx; Simon Peyton Jones; kyra; ghc-devs@haskell.org
> *Subject:
ou have seen, but
>
> http://hackage.haskell.org/package/Win32
>
> points quite clearly to
>
> https://github.com/haskell/win32
>
> and that's the official upstream repository GHC tracks (via a locally
> mirrored repo at git.haskell.org)
>
>
Can you try running the offending command with -v to see which step breaks?
I tried running it locally under strace but did not see any file renames
either.
On Tue, Oct 28, 2014 at 6:37 PM, Páli Gábor János
wrote:
> 2014-10-26 18:17 GMT+01:00 Gintautas Miliauskas :
> > Maybe it&#x
e.
>
> [1]
> http://git.haskell.org/ghc.git/commit/4b648be19c75e6c6a8e6f9f93fa12c7a4176f0ae
> [2] http://haskell.inf.elte.hu/builders/windows-x86-head/56/10.html
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
> ht
sure everyone can help - there's always so much to do
> and so little time, we need to encourage it all we can.
>
> As Simon says: Upward and Onward!
>
> [1] http://haskell.inf.elte.hu/builders/
> [2]
> https://ghc.haskell.org/trac/ghc/query?status=!closed&os=Window
The patch looks good both on i686 and x86_64. Cool stuff!
On Mon, Oct 27, 2014 at 12:01 PM, kyra wrote:
> On 10/27/2014 1:37 PM, Gintautas Miliauskas wrote:
>
>>
>> During a couple of days I'll extract my patch to Linker.c and put
>> it to Phabricator t
h, this slipped my mind. On it.
>
> On Fri, Oct 24, 2014 at 10:33 AM, Simon Marlow wrote:
> > I sent a patch to Austin to validate+commit earlier this week.
> >
> > On 24/10/2014 15:08, Gintautas Miliauskas wrote:
> >>
> >> This is still not fixed, right?
what the problem does "#define _MSVCRT_ 1" solve? I didn't
> need it at all (I never run validate.sh though).
>
Without it I think I got a bunch of conflicting export definitions from the
C library, and removing the ones in Linker.c resulted in runtim
setup), some of which could probably be fixed
easily. Some additional eyes and fingers on keyboards would be very welcome
there.
If you want to experiment with the patch, make sure to also patch in the
related changes listed in the last comment on the Phab page.
--
Gint
the
> meantime.
>
> [1]
> http://git.haskell.org/ghc.git/commit/4b648be19c75e6c6a8e6f9f93fa12c7a4176f0ae
> [2] http://haskell.inf.elte.hu/builders/windows-x86-head/56/10.html
> ___
> ghc-devs mailing list
> ghc-devs@haskell.org
>
build/Linker.o' failed
>> >
>> > make[1]: *** [rts/dist/build/Linker.o] Error 1
>> >
>> > make[1]: *** Waiting for unfinished jobs
>> >
>> >
>> > _______
>> > ghc-devs mailing list
&g
o take into account license issues,
> such as hosting the source-code as well, if we host binary distributions
> depending on the licenses involved (I'm not sure if this was ever
> considered for ghc-tarballs.git to begin with)
>
> Cheers,
> hvr
>
--
Gintautas Miliauska
i?id=17466 to see what the
developers say, but have not gotten a response yet. Perhaps someone here
knows what's going on?
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
ut that though...
2. Download failing due to internet connectivity issues or missing proxy
configuration. This could easily be addressed by printing a message with a
URL and a filesystem location to put the file in the case that the download
fails.
If there are no objections, I'll
eresting not just to
people building ghc). Would you mind moving that text off to a separate
wikipage and adding a link to it instead?
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
> willing?I’d say that being a member indicates a positive willingness to
> help others, along with some level of expertise, NOT a promise to drop
> everything to attend to someone else’s problem.
>
>
>
> Simon
>
>
>
> *From:* loneti...@gmail.com [mailto:loneti..
I'll set up a wikipage this evening.
Should we get a mailing list of our own too, or do you think it's best to
continue on ghc-devs@?
--
Gintautas Miliauskas
On Oct 9, 2014 9:52 AM, "Simon Peyton Jones" wrote:
> I think I’m fairly behind on the current build process of
CParser.o'
The errors are not deterministic at all. Any idea what's happening? Any
suggestions for debugging this?
On Wed, Oct 8, 2014 at 1:21 AM, Gintautas Miliauskas <
gintautas.miliaus...@gmail.com> wrote:
> I've cleaned up the main Windows build
> <https://ghc.ha
s of this email being honourable exceptions.
>
>
>
> but nothing really happened. Maybe this time it can! Possible member of
> such a task force are:
>
> ·Gintautas Miliauskas gintautas.miliaus...@gmail.com
>
> ·kyra ky...@mail.ru
>
> ·Marek
Is there any particular reason why taking in GitHub pull requests would be
more problematic than, say, applying patches attached to Trac bugs? Both
have to be dealt with manually by someone with commit rights for the
canonical repository anyway. If the issue is important enough that, say,
tracking
* full history of ghc-tarballs is tracked, easier bisecting
> * no extra scripts needed
>
> I don't know how much space overhead git adds. wget-ting just the files
> themselves might still be faster.
>
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
gwin or gcc
> or whatever the that user happens to have installed.
>
A "rubenvb" build is one of the available types of prebuilt binary packages
of mingw for Windows. Let's figure out if there is something more
mainstream and if we can migrate to that.
--
Gintautas Miliauskas
ich use cygwin1.dll /
msys-2.0.dll? Not sure there's much benefit to that...
> > 14. The test runner assumes native Windows Python, but it's only a few
> > small changes away from working fine on the python2 provided by msys2,
> > which would cut another exter
exactly to warn the user if such a type of gcc is detected, because that's
almost never what you want.
On Sun, Sep 28, 2014 at 9:08 AM, kyra wrote:
> On 9/28/2014 1:04 AM, Gintautas Miliauskas wrote:
>
>> 11. A build with the host gcc failed. I think the cause is that it is too
&
of date or misleading
> information, and yes I think we should focus on msys2.
>
>
>
> Great stuff
>
>
>
> Simon
>
>
>
> *From:* ghc-devs [mailto:ghc-devs-boun...@haskell.org] *On Behalf Of
> *Gintautas
> Miliauskas
> *Sent:* 15 September 2014 21:58
> *To:* ghc
and verified.
Best regards,
--
Gintautas Miliauskas
___
ghc-devs mailing list
ghc-devs@haskell.org
http://www.haskell.org/mailman/listinfo/ghc-devs
58 matches
Mail list logo
