NightStrike wrote:
> No, it's just not setup right. The msys.bat file configures a system
> properly based on if you're 64-bit windows or 32-bit windows. So
> start your shell with that instead of starting sh.exe directly. You
> can use the --norxvt option to msys.bat to use a normal windows
>
On 3/20/08, David Cleaver <[EMAIL PROTECTED]> wrote:
>
> NightStrike wrote:
> > On 3/20/08, David Cleaver wrote:
> >> 1) Do I need to add "c:\mw64\bin" to my path?
> >
> > Yup. I'd put it first, too: PATH=C:\mw64\bin;%PATH%
>
> Awesome! After using tar under cygwin (I originally used a program c
NightStrike wrote:
> On 3/20/08, David Cleaver wrote:
>> 1) Do I need to add "c:\mw64\bin" to my path?
>
> Yup. I'd put it first, too: PATH=C:\mw64\bin;%PATH%
Awesome! After using tar under cygwin (I originally used a program called
7-zip) to re-extract all the files to c:\mw64, all the file
On 3/20/08, David Cleaver <[EMAIL PROTECTED]> wrote:
> Hello everyone,
Hi!
> I would like to start using mingw-w64, but am unsure of what to do.
Emailing here is a good start :)
> I've just downloaded the latest mingw-w64-bin-x86_64-mingw_20080320.tar.bz2
> and extracted
> it to its own folder
Hello everyone,
I would like to start using mingw-w64, but am unsure of what to do. I've just
downloaded the latest mingw-w64-bin-x86_64-mingw_20080320.tar.bz2 and extracted
it to its own folder "c:\mw64". I'm running Windows XP 64-bit edition and
would
like to build 64-bit windows binaries.
On 3/20/08, Arthur Norman <[EMAIL PROTECTED]> wrote:
> But let me stress that a variety of C and C++ programs build and run OK.
> Any suggestions about what could cause a crash before main() is entered
> most welcome!
First, thank you greatly for all of this information. It is wonderful
to se
On 3/20/08, Arthur Norman <[EMAIL PROTECTED]> wrote:
> Now with both the above compilers and the linux64 hosted one (where I
> found a need to install mpfr) I can compile various things but there are
hmm
I guess I used a shared library build of mpfr. I should make all the
gmp/mpfr things be
On 3/20/08, Arthur Norman <[EMAIL PROTECTED]> wrote:
> ... since everybody is very active today!
>
> I run on Vista-x86_64, and run under a cygwin shell so I have all the
> 32-bit development tools I like. When I compile I go "-mno-cygwin" and
> that is how my scripts and autoconf things are all se
... since everybody is very active today!
I run on Vista-x86_64, and run under a cygwin shell so I have all the
32-bit development tools I like. When I compile I go "-mno-cygwin" and
that is how my scripts and autoconf things are all set up.
With mingw-w64-bin-x86_64-mingw_20080320.tar.bz2 unpa
>
> > Secondly I notice the files have long prefixes in the c:\mingw\bin
> > directory, for example "x86_64-pc-mingw32-c++filt.exe", I
> > also notice there are more bins in C:\mingw\x86_64-pc-mingw32\bin, such
> as
> > g++
>
> That's because this is a cross compiler. Those prefixes let you know
>
On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> Yes I have a linux64 installed, and a linux32 running on the linux64 through
> vmware.
I can tell you that the linux64 cross compiler works VERY well, as I
use it to build all of the other compilers. Just make sure to set
your path properl
I don't think mingw and msys work well on WoW all together, at
least in my experience, the 32 stuff has to be run on a 32 but OS,
and vice versa for 64 bit.
No, that's the whole point of WoW: you can run Win32 executables on
Win64. Running the Win32 cross compiler on Win64 works fairly wel
On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
>
>
> On Thu, Mar 20, 2008 at 3:25 PM, NightStrike <[EMAIL PROTECTED]> wrote:
> >
> > On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> > >
> >
> >
> >
> > > > Honestly, can you just use the cross compilers? They work great.
> > [...]
On Thu, Mar 20, 2008 at 3:25 PM, NightStrike <[EMAIL PROTECTED]> wrote:
> On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> >
> > > Honestly, can you just use the cross compilers? They work great.
> [...]
> > I'm guessing I need to download it from somewhere.
>
> Yup. In the download are
FX Coudert <[EMAIL PROTECTED]> wrote on 20.03.2008 16:36:00:
> > I assume the major point for our native build are gmp/mpfr compilation
> > failures.
>
> I'm sorry if I say something stupid, but: have you tried building gmp
> and mpfr with --host=none-none-none?
May, we should give it a try. But
>> PS: I have another question: what is the roadmap for merging the
>> headers and crt with 32-bit mingw?
>
> You're a funny guy :) :) :)
Shall I understand that as a "not planned yet"?
FX
--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/
---
On 3/20/08, FX Coudert <[EMAIL PROTECTED]> wrote:
> PS: I have another question: what is the roadmap for merging the
> headers and crt with 32-bit mingw?
You're a funny guy :) :) :)
-
This SF.net email is sponsored by: Micros
> I assume the major point for our native build are gmp/mpfr compilation
> failures.
I'm sorry if I say something stupid, but: have you tried building gmp
and mpfr with --host=none-none-none?
PS: I have another question: what is the roadmap for merging the
headers and crt with 32-bit mingw?
NightStrike <[EMAIL PROTECTED]> wrote on 20.03.2008 16:27:17:
> On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> > NightStrike <[EMAIL PROTECTED]> wrote on 20.03.2008 16:23:17:
> >
> > > On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> > > > > We did something to fix iostream (although I'll re
On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> NightStrike <[EMAIL PROTECTED]> wrote on 20.03.2008 16:23:17:
>
> > On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> > > > We did something to fix iostream (although I'll remind you that most
> > > > of g++ and all of gfortran is broken), and I d
NightStrike <[EMAIL PROTECTED]> wrote on 20.03.2008 16:23:17:
> On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> > > We did something to fix iostream (although I'll remind you that most
> > > of g++ and all of gfortran is broken), and I don't remember what. I
> > > need a patch from Kai, and I
On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
>
> > Honestly, can you just use the cross compilers? They work great.
> >
>
>
> Hi, yes that is absolutely an option, however I'm not too sure how to get
> that up and running. I've got more than enough win32 machines around me,
> although n
On 3/20/08, Kai Tietz <[EMAIL PROTECTED]> wrote:
> > We did something to fix iostream (although I'll remind you that most
> > of g++ and all of gfortran is broken), and I don't remember what. I
> > need a patch from Kai, and I forget which one.
>
> It was the disabling of stack probing AFAI rememb
as it's uploading, so it'll be in a few
> > minutes..)
> > >
> >
> > OK thanks NightStrike. I've downloaded
> > mingw-w64-bin-x86_64-mingw_20080320, and installed it into
> > an empty c:\mingw directory
> >
> > $ g++ --version
> > g++.exe
>
> Honestly, can you just use the cross compilers? They work great.
>
Hi, yes that is absolutely an option, however I'm not too sure how to get
that up and running. I've got more than enough win32 machines around me,
although not too sure how to get gcc to compile in 64 bit on it.. so far
when
On 3/20/08, Aaron Giles <[EMAIL PROTECTED]> wrote:
> > >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
> >
> > That fix has been included in the build system of GCC itself for
> > quite a few months now. You don't need to do anything special to
> > benefit from it (apart from using rece
> >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> That fix has been included in the build system of GCC itself for
> quite a few months now. You don't need to do anything special to
> benefit from it (apart from using recent mingw headers along).
Apparently so, as I was able to co
OK thanks NightStrike. I've downloaded
> mingw-w64-bin-x86_64-mingw_20080320, and installed it into
> an empty c:\mingw directory
>
> $ g++ --version
> g++.exe (GCC) 4.4.0 20080320 (experimental)
> Copyright (C) 2008 Free Software Foundation, Inc.
> This is free software; see
ed it into an empty c:\mingw directory
$ g++ --version
g++.exe (GCC) 4.4.0 20080320 (experimental)
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$
> On 3/20/08, Aaron Giles <[EMAIL PROTECTED]> wrote:
> > Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> Yeah, I'm gonna go with a 'No' on that one But feel free to try
> it :) :)
>
> I suppose I should add Vista to the list of hosts I build toolchains
> for
No, all yo
> Can you elaborate on that? How does gcc for instance know if you're
> targetting a Vista platform?
See http://gcc.gnu.org/ml/fortran/2008-03/msg00119.html and http://
gcc.gnu.org/ml/fortran/2008-03/msg00120.html
The fix is applied to all mingw hosts.
FX
--
François-Xavier Coudert
http://w
On 3/20/08, FX Coudert <[EMAIL PROTECTED]> wrote:
> >> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> That fix has been included in the build system of GCC itself for
> quite a few months now. You don't need to do anything special to
> benefit from it (apart from using recent mingw he
>> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
That fix has been included in the build system of GCC itself for
quite a few months now. You don't need to do anything special to
benefit from it (apart from using recent mingw headers along).
FX
--
François-Xavier Coudert
http://w
On 3/20/08, Aaron Giles <[EMAIL PROTECTED]> wrote:
> Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
>
> Aaron
Yeah, I'm gonna go with a 'No' on that one But feel free to try it :) :)
I suppose I should add Vista to the list of hosts I build toolchains for
Does anyone kno
Is this built with the Vista fix (-D__USE_MINGW_ACCESS)?
Aaron
--
> -Original Message-
> From: [EMAIL PROTECTED]
[mailto:mingw-w64-
> [EMAIL PROTECTED] On Behalf Of NightStrike
> Sent: Thursday, March 20, 2008 7:15 AM
> To: whatis neveritis; Kai Tietz
> Cc: mingw-w64-public@lists.sourcefo
On 3/20/08, NightStrike <[EMAIL PROTECTED]> wrote:
> On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> > $ gcc --version
> > gcc.exe (GCC) 4.3.0 20080131 (experimental)
>
> > What is the problem?
>
> This is an old version. I'll build a new version and upload it to the
> site, hopefully in
On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> $ gcc --version
> gcc.exe (GCC) 4.3.0 20080131 (experimental)
> What is the problem?
This is an old version. I'll build a new version and upload it to the
site, hopefully in the next few hours. Try that, and then we'll go
from there.
I
Hi,
gcc isn't working on this install of mingw-w64-bin-x86_64-mingw_20080213 on
my OS.
The OS is Microsoft Windows XP Professional x64 Edition (Version 2003)
Service Pack 2
The install is on C:\MinGW
in MSYS:
$ gcc --version
gcc.exe (GCC) 4.3.0 20080131 (experimental)
Copyright (C) 2007 Free S
38 matches
Mail list logo
