Thanks Ruben,
> I have completed the x86 build and uploaded it here:
> https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win32/Personal%20Builds/rubenvb/
When I try to compile wxWidgets 2.8.10 as usual .-
mingw32-make -f Makefile.gcc SHARED=1 UNICODE=1 BUILD=release MONO
On 21 September 2010 12:51, Earnie wrote:
> Andy Koppe wrote:
>>> Cygwin isn't strictly obliged to provide an interface to Windows.
>>
>> No, but then it wouldn't really be Cyg*win* anymore. It would
>> effectively be Interix with a particularly slow fork(). That's
>> unless it moved into its own s
2010/9/20 NightStrike
> Wonderful, thanks!
>
> On Mon, Sep 20, 2010 at 11:26 AM, Ruben Van Boxem
> wrote:
> > 2010/9/20 NightStrike
> >>
> >> Did you upload this to the sourceforge file release area under Personal
> >> Builds?
> >>
> >
> > I sure did:
> >
> > x64 binary:
> >
> https://sourcefor
Hi,
I'm sorry to spam the mailing list, but I'm running into a lot of strange
errors
I tried to recompile the exact same source as is uploaded, but instead of
using sezero's builds to do that, I tried using my freshly built toolchain.
The build failed at ppl, with this error:
libtool: compi
Hi,
In an effort to test my build(script), I decided to rebuild everything, now
employing my freshly gained lto capabilities:
CFLAGS="...-flto" # ... = old options, which worked :)
LFLAGS="-flto -fwhopr=$BUILD_CORES"
The options get passed nicely to every configure script, and they are used
wher
On Tue, Sep 21, 2010 at 6:55 PM, Ruben Van Boxem
wrote:
> Hi,
>
> While compiling GNU make
Just be careful doing that: make may require patching especially for
the path separator character (see the make package I maintain at
the downloads page)
> , configure showed a warning saying that my sys
Hi,
While compiling GNU make, configure showed a warning saying that my system
doe snot have waitpid() or wait3() and therefore "-j" would be unreliable. I
understand, but then a simple google on "mingw waitpid" got me this:
http://www.koders.com/c/fid3D4ECA1D12B2F778B030DF13B9C076952EC55658.aspx
Hi,
When I created my new project at SF.net, it offered to create it on the new
beta 2.0 environment, which is, quite frankly, a million times better than
the old one (except for maybe bug reports as I haven't checked that yet).
Would it be fruitful/interesting to the admins to at least explore t
Andy Koppe wrote:
>> Cygwin isn't strictly obliged to provide an interface to Windows.
>
> No, but then it wouldn't really be Cyg*win* anymore. It would
> effectively be Interix with a particularly slow fork(). That's
> unless it moved into its own subsystem, which of course would mean a
> major re
2010/9/20 Ruben Van Boxem
>
> Here's my configure line:
>
> /home/Ruben/mingw64/src/gmp/configure --host=i686-w64-mingw32
>> --build=i686-w64-mingw32 CFLAGS="-mtune=core2 -fomit-frame-pointer
>> -momit-leaf-frame-pointer" --prefix=/home/Ruben/mingw64/build32/gcc-libs
>> --disable-static --enable-
10 matches
Mail list logo
