compressed binary.
>
> Starting from offset 0x100 (256):
> f7 ce 21 7c 5b b1 1a d7 a6 67 a2 55 e2 22 4e 88
>
> Byte 262 is 0x1a (26)
>
> 2015-06-22 17:21 GMT+02:00 LRN
> <mailto:lrn1...@gmail.com>>:
HTH,
--
Mook
--
Hi! You had to go and have an interesting problem, so I wrote a crappy
sample :p https://gist.github.com/mook/33abbeb13b6bb511fc21 - Note that
I didn't close the handles that I should (see the various
WaitForDebugEvent-related documentation).
On 11/14/2014 07:49 AM, Vincent Torri wrote:
ve, though I have no idea if it's
better or worse than SF's search:
http://dir.gmane.org/gmane.comp.gnu.mingw.w64.general
--
Mook
--
Everyone hates slow websites. So do we.
Make your web apps faster with App
On 3/27/2012 8:40 PM, Anil Sahukar wrote:
> My goal is to build the cross-compiler for MinGW-w64 starting from the
> native MinGW and source packages GMP (5.0.2) , PPL (0.11), CLooG
> (0.15.11) and binutils-2.21.53.
>
> From config.log:
>
> It was created by configure, which was generated by GNU A
this, though I suspect it's broken.
In general: I strongly agree that the current situation isn't very good,
and wish you luck on whatever you can to fix it - I will try to answer
questions, though I suspect my response time might not be awesome. Keep
?revision=4386&view=markup#l231
So the comment is a lie - well, adding new fields would be bad, because
buildbot unconditionally clobbers that file :)
--
Mook
--
All the data continuously generated in your IT
chines. Makes it easier to run the makefile
locally and (usually) produce the same results. The various
intermediate targets in the makefile serves as entry points for
buildbot, assuming all the previous steps were already done.
HTH,
--
Mook
ve thoughts are welcome, and help in getting the
> machinery set up. In my eyes, this would mean making my scripts
> runnable on some build infrastructure, and expanding them to work for
> Cygwin/Mac, hopefully without much trouble.
If msys
t
extract it... but that's half-baked and needs more thought. And is
independent of just plain shipping less stuff, and should come after
that's done first.
--
Mook
--
BlackBerry® DevCon Americas, Oct. 18-20,
ccounts on all machines, I believe, much less ability to install things
at will. Though they probably wouldn't mind doing things if it's not
too frequent.)
Needs buildbot side changes to find the right file to upload too, of course.
--
Mook
currently too much of a slacker :\
--
need to include a system
header (pretty much any one of them).
> Also, is there a way to find out what all typedef's there are in the mingw64
> environment? Is there a way to get gcc to output this info? Is there
> already a
> list somew
to launch, and
therefore not an issue with the build system).
So: it would probably work. Most of the time. Just try to avoid
building really-large-projects-with-ridiculous-build-systems... Or be
prepared to re-run your build. :(
(This is all actually hearsay - I tend to avoid building with
gt;> vision) but with some help I think I can create the buildbot (with some
>> patience by the maintainer). I am not a Python expert but I am brave enough
>> and have some spare time to burn.
>
>
> Get with Mook on our IRC channel. The additional steps necessary to
> enha
's some funny
backwards-compatibility thing?
Either way, without more of the config log it's difficult to tell why
it's trying to use a half-msvc toolchain.
--
Mook
--
ThinkGeek and WIRED's Gee
imprinted on the binary somehow... make sense?
Yeah, and was supposed to be harmless. I guess not?
>
> Its being quite annoying to deal with this since libtool keeps trying to
> check libstdc++.la on that path, which as I don't have, just fails...
And it should be finding it elsewher
reaks non-sysroot
prefix builds, so that's not useful.
Mostly sending this just so the mailing list archive can help remember
this for me ;)
[1] http://gcc.gnu.org/viewcvs/trunk/gcc/cppdefault.c?view=markup#l44
--
Mook
-
ATION rand_s and
HeapEnableTerminationOnCorruption in enum HEAP_INFORMATION_CLASS)
--
Mook
Being completely useless, mostly hanging out on IRC
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon
(As far as I can tell, current m-c will fail due to the mingw-w64
headers #defining BOOL somewhere conflicting with the new 64 bit jit
that I haven't had time to poke yet)
--
Mook
(one of the crazier people)
--
Come
18 matches
Mail list logo
