[Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[whatis neveritis]

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 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.

Now when I compile:

//#include 
#include 
int main(int argc, char* argv[])
{
printf("%i bit build\n", sizeof(void*)*8);
return 0;
}

with gcc, (gcc test.c) nothing happens... nore does it work with g++

However if I include  it works with g++

$ g++ test.cpp

$ a.exe
64 bit build

The same problem occurs when I run those commands in windows command
prompt... I ran the exact same test on a win32 machine, and it all worked as
expected.

What is the problem?

Sorry I realise this email doesn't contain a very detailed description of my
setup, but if there is any more information I can send you please let me
know.

My aim is to build a bunch of libraries in 64 bit, such as libsndfile,
libjpeg, libtiff etc.

Thanks in advance.
Regards.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 have to admit, it was a little surprising that g++ worked and gcc
didn't.  Usually, it's the other way around.  On that note, btw, g++
and gfortran don't work too well, and don't give a lot of feedback
that they don't work.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 the next few hours.  Try that, and then we'll go
> from there.
>
> I have to admit, it was a little surprising that g++ worked and gcc
> didn't.  Usually, it's the other way around.  On that note, btw, g++
> and gfortran don't work too well, and don't give a lot of feedback
> that they don't work.

Ok, go get 'em, tiger.  Find them at your friendly download section now.

(Ok, well, I'm posting this as it's uploading, so it'll be in a few minutes..)

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[Aaron Giles]

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.sourceforge.net
> Subject: Re: [Mingw-w64-public] gcc and g++ (c compilation only) not
> workingon MinGW-64 in Microsoft Windows XP Professional x64
> Edition(Version 2003) Service Pack 2
> 
> 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 the next few hours.  Try that, and then we'll go
> > from there.
> >
> > I have to admit, it was a little surprising that g++ worked and gcc
> > didn't.  Usually, it's the other way around.  On that note, btw, g++
> > and gfortran don't work too well, and don't give a lot of feedback
> > that they don't work.
> 
> Ok, go get 'em, tiger.  Find them at your friendly download section
> now.
> 
> (Ok, well, I'm posting this as it's uploading, so it'll be in a few
> minutes..)
> 
>
---
> --
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
> ___
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
> 


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[NightStrike]

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 know (Kai?) if I can do the -D thing for *ANY* target?
ie, is there ever a case where we would require that it *NOT* be
defined?  There was discussion about that somewhere on the mingw list.
 If we can make it so that it builds the same everywhere, then we'll
never need to define that again.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[FX Coudert]

>> 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://www.homepages.ucl.ac.uk/~uccafco/


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[NightStrike]

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 headers along).

Can you elaborate on that?  How does gcc for instance know if you're
targetting a Vista platform?

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[FX Coudert]

> 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://www.homepages.ucl.ac.uk/~uccafco/


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[Aaron Giles]

> 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 you need to do is make sure that define is set for any
Windows-based toolchains. I don't know if having it set will foul up any
of the Linux builds or not.

Aaron


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[whatis neveritis]

>
> Ok, go get 'em, tiger.  Find them at your friendly download section now.
>
> (Ok, well, I'm posting this 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 (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.

$ g++ test.cpp

this command doesn't produce an a.exe, with or without including 

$ gcc testc.cpp

however this one does when the code is c.. (although it doesn't give an
error message when I include  it just silently fails).

So I guess this is a progression on the gcc front, but a regression on the
g++ front..

What do you recommend I do? copy g++ from the old build into this one? my
libraries need both compiles to work before they'll compile. :(

Thanks for your time.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
>
> > Ok, go get 'em, tiger.  Find them at your friendly download section now.
> >
> > (Ok, well, I'm posting this 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 (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.
>
> $ g++ test.cpp
>
> this command doesn't produce an a.exe, with or without including 

I thought we fixed iostream..

Let me think


Kai, did you ever get all those patches into the trunk for this?  If
not, that would explain it.  It's not really a regression for g++;
more like a patch I forgot to apply.

> $ gcc testc.cpp
>
> however this one does when the code is c.. (although it doesn't give an
> error message when I include  it just silently fails).
>
> So I guess this is a progression on the gcc front, but a regression on the
> g++ front..
>
> What do you recommend I do? copy g++ from the old build into this one? my
> libraries need both compiles to work before they'll compile. :(

Hold out a little longer :)

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.

Honestly, can you just use the cross compilers?  They work great.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[Aaron Giles]

> >> 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 compile a hello world app for the first
time. :)

Now for some more serious testing

Aaron


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not workingon MinGW-64 in Microsoft Windows XP Professional x64 Edition(Version 2003) Service Pack 2

[NightStrike]

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 recent mingw headers along).
>
> Apparently so, as I was able to compile a hello world app for the first
> time. :)
>
> Now for some more serious testing

Tread carefully :)

Keep in mind that gcc works much better than g++/gfortran.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[whatis neveritis]

>
> 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 I tried it said:

test.c:1: sorry, unimplemented: 64-bit mode not compiled in

I'm guessing I need to download it from somewhere.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[Kai Tietz]

[EMAIL PROTECTED] wrote on 20.03.2008 
16:17:04:

> On 3/20/08, whatis neveritis <[EMAIL PROTECTED]> wrote:
> >
> > > Ok, go get 'em, tiger.  Find them at your friendly download section 
now.
> > >
> > > (Ok, well, I'm posting this 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 (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.
> >
> > $ g++ test.cpp
> >
> > this command doesn't produce an a.exe, with or without including 

> 
> I thought we fixed iostream..
> 
> Let me think
> 
> 
> Kai, did you ever get all those patches into the trunk for this?  If
> not, that would explain it.  It's not really a regression for g++;
> more like a patch I forgot to apply.
> 
> > $ gcc testc.cpp
> >
> > however this one does when the code is c.. (although it doesn't give 
an
> > error message when I include  it just silently fails).
> >
> > So I guess this is a progression on the gcc front, but a regression on 
the
> > g++ front..
> >
> > What do you recommend I do? copy g++ from the old build into this one? 
my
> > libraries need both compiles to work before they'll compile. :(
> 
> Hold out a little longer :)
> 
> 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 remember.


Cheers
  Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 remember.

Yeah, that was it...  do you have a patch for that?  Did you ever
submit it to gcc?

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 not too sure how to get gcc to compile in 64 bit on it.. so far
> when I tried it said:
>
> test.c:1: sorry, unimplemented: 64-bit mode not compiled in
>
> I'm guessing I need to download it from somewhere.

Yup.  In the download area, I build 5 toolchains, hosted on these systems:

Linux32
Linux64
Win32
Win64
Cygwin32

Pick your poison.  You should be able to run the Win32 one (look for
i686-mingw) on a Win64 host.  It'll run it in the WoW simulator.  I
personally use the Linux64 cross compiler for all of my work, so its
kept most up to date.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[Kai Tietz]

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 forget which one.
> >
> > It was the disabling of stack probing AFAI remember.
> 
> Yeah, that was it...  do you have a patch for that?  Did you ever
> submit it to gcc?
No, this patch is more a hack. The __chkstk has to be fixed not simply 
turned off :)

Cheers,
  Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 don't remember what.  I
> > > > need a patch from Kai, and I forget which one.
> > >
> > > It was the disabling of stack probing AFAI remember.
> >
> > Yeah, that was it...  do you have a patch for that?  Did you ever
> > submit it to gcc?
> No, this patch is more a hack. The __chkstk has to be fixed not simply
> turned off :)

Is there a gcc bug report opened?

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[Kai Tietz]

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 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 remember.
> > >
> > > Yeah, that was it...  do you have a patch for that?  Did you ever
> > > submit it to gcc?
> > No, this patch is more a hack. The __chkstk has to be fixed not simply
> > turned off :)
> 
> Is there a gcc bug report opened?

AFAIK yes. It was about the patch for __alloca. I am still on to find the 
point, which is responsible for the stack clobbering. Joseph's patch has 
solved some problems, as the guys with the fortran compiler told.
I assume the major point for our native build are gmp/mpfr compilation 
failures. Btw, the patches I sent you today requires an rebuild of those 
libraries for native.

Cheers,
  Kai

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[FX Coudert]

> 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?

FX

-- 
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[FX Coudert]

>> 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/


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[Kai Tietz]

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 the major problem is, that gmp and mpfr 
assumes on some places, that long has 64-bit width, which is for this 
target certainly wrong :(

> PS: I have another question: what is the roadmap for merging the 
> headers and crt with 32-bit mingw?
IMHO first the stack clobbering problem has to be solved. But if we reach 
this state, we will continue merging. I think you point specially on the 
mingw_snprintf feature for libgfortran. This will be next.

Cheers,
  Kai

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[whatis neveritis]

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 area, I build 5 toolchains, hosted on these systems:
>
> Linux32
> Linux64
> Win32
> Win64
> Cygwin32
>
> Pick your poison.  You should be able to run the Win32 one (look for
> i686-mingw) on a Win64 host.  It'll run it in the WoW simulator.  I
> personally use the Linux64 cross compiler for all of my work, so its
> kept most up to date.
>

Just to be sure, are we talking about the download section for MinGW-w64
"Complete toolchain snapshot"? It seems you're referring to
"mingw-w64-bin_i686-mingw_20080116", which I've downloaded and tested right
away.

First off I get a message from winrar telling me the symbolic links are
broken.

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++

I tried out that g++ but I got:

"g++.exe: CreateProcess: No such file or directory"

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.
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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.
> > [...]
> > > I'm guessing I need to download it from somewhere.
> >
> > Yup.  In the download area, I build 5 toolchains, hosted on these systems:
> >
> > Linux32
> > Linux64
> > Win32
> > Win64
> > Cygwin32
> >
> > Pick your poison.  You should be able to run the Win32 one (look for
> > i686-mingw) on a Win64 host.  It'll run it in the WoW simulator.  I
> > personally use the Linux64 cross compiler for all of my work, so its
> > kept most up to date.
> >
>
> Just to be sure, are we talking about the download section for MinGW-w64
> "Complete toolchain snapshot"? It seems you're referring to
> "mingw-w64-bin_i686-mingw_20080116", which I've downloaded
> and tested right away.
>
> First off I get a message from winrar telling me the symbolic links are
> broken.

I forgot to tar it with "-h".  Sorry.

> 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
what the given binary targets, which is different from the host.

> I tried out that g++ but I got:
>
> "g++.exe: CreateProcess: No such file or directory"
>
> 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.

The Win32 one is old.  I'm trying to update it now, but it won't be
immediate.  The build process is clunky (I'm working on that, too).
Do you have a linux machine handy?  Or linux in vmware?

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[FX Coudert]

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 well, I  
was told (by Fortran users; I don't know about g++).


For your issue, you should try running the compiler with its full  
path: "C:\foo\bar\bin\g++.exe myfile.cpp". It helps the buggy GCC  
driver.


FX

--
François-Xavier Coudert
http://www.homepages.ucl.ac.uk/~uccafco/

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[NightStrike]

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 properly.  Try that, and we'll work on the other stuff in
due time.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] gcc and g++ (c compilation only) not working on MinGW-64 in Microsoft Windows XP Professional x64 Edition (Version 2003) Service Pack 2

[whatis neveritis]

>
> > 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
> what the given binary targets, which is different from the host.
>
> > I tried out that g++ but I got:
> >
> > "g++.exe: CreateProcess: No such file or directory"
> >
> > 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.
>
> The Win32 one is old.  I'm trying to update it now, but it won't be
> immediate.  The build process is clunky (I'm working on that, too).
> Do you have a linux machine handy?  Or linux in vmware?
>

Yes I have a linux64 installed, and a linux32 running on the linux64 through
vmware.

> No, that's the whole point of WoW: you can run Win32 executables on Win64.
> Running the Win32 cross compiler on Win64 works fairly well, I was told
(by Fortran
> users; I don't know about g++).

I realise, but my experience still hasn't been so good running the mingw 32
bit binaries on xp 64 bit.

> For your issue, you should try running the compiler with its full path:
> "C:\foo\bar\bin\g++.exe myfile.cpp". It helps the buggy GCC driver.

Thanks, I've just tried, but I'm still getting:

g++.exe: CreateProcess: No such file or directory
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

[Mingw-w64-public] quick report on recent snapshots...

[Arthur Norman]

... 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 unpacked and its bin 
dircetory put on the front of my path I have two things that cause me pain 
(and yes I can cope).  (a) it provides binaries with names such as gcc and 
g++ because it thinks it is native - which it is - but those then shadow 
the regular 32-bit cygwin ones I have, and until -m32/-m64 bi-arch is 
there I would feel happier if the binaries remained named as for cross 
compilation. Also if they did it would be easier to just switrch paths and 
compare behaviours of the native and cross versions.  Then (b) when I try 
the native compiler under cygwin my autoconf .deps directory ends up 
messed up with entries like
fwin.o: fwin.c config.h ../cslbase/fwin.h \
c:\mingw64\root0320\bin\../lib/gcc/x86_64-pc-mingw32/4.4.0/include/stdarg.h \
c:\mingw64\root0320\bin\../lib/gcc/x86_64-pc-mingw32/4.4.0/../../../../x86_64-p
where with the cygwin 32-bit compiler I get
fwin.o fwin.o: ../cslbase/fwin.c ./config.h ../cslbase/fwin.h \
   /usr/lib/gcc/i686-pc-cygwin/3.4.4/include/stdarg.h \
/usr/lib/gcc/i686-pc-mingw32/3.4.4/../../../../i686-pc-mingw32/include/st

The "c:\" bits in the path that this gcc has stuck on lead to
$ make fwindemo
.deps/FXDCNativePrinter.Po:1: *** multiple target patterns.  Stop.

i.e. my autoconf-generated makefiles stop working!  When I use the 
mingw-w64-bin_i686-cygwin-1.5.25-11_20080318.tar.bz2 archive (again just 
putting its bin directory on the front of my PATH) the autoconf/make stuff 
behaves as I had hoped.

I accept that the first of these reports is proper behaviour for a native 
compiler, and the second may be proper for a mingw version of gcc when run 
undre a cygwin shell and with cygwin utilities, so REALLY these are MY 
problems not yours - I accept that but still felt you might like to know 
what holds my testing back.

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 
still problems. I have used the cygwin-0318 version to compile the FOX 
windowing toolkit and a bunch of simple tests work. However when I then 
compile SOME of my own programs that use it they seem to work happily, but 
the ones that matter to me more fail. The symptom is windows putting up a 
dialog box saying "name.com has stopped working". My code is in a mixture 
of C and C++ and starts in C. When I put a printf statement at the very 
start of "main" (with an fflush just after it to be sure) I do not even 
get there. When I turn "main" into a function that JUST prints the message 
and stops it still crashes with no output. If I comment out ENOUGH from 
all the other source files at some stage the main program is executed and 
my message appears. So I guess somewhere some C++ initialsation is 
misbehaving?
When I build the same thing using cygwin-compiled FOX libraries by by own 
code cross-compiled on linux64 it still fails by windows pops up its moan 
once not 5 times, so maybe something is slightly different.  I will 
continue to try to narrow this down!

I tried to see if the preview of gdb would help, but I get moans as per a 
previous email report, ie
"warning: A handler for the OS ABI "Cygwin" is not built into this 
configuration of GDB.  Attempting to continue with the default i386:x86-64 
settings." and when I try "...gdb myapp.com" I get that message followed 
by a "gdb has stopped working" message from Windows.

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!

Arthur


-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] quick report on recent snapshots...

[NightStrike]

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 set up.
>
> With mingw-w64-bin-x86_64-mingw_20080320.tar.bz2 unpacked and its bin
> dircetory put on the front of my path I have two things that cause me pain
> (and yes I can cope).  (a) it provides binaries with names such as gcc and
> g++ because it thinks it is native - which it is - but those then shadow
> the regular 32-bit cygwin ones I have, and until -m32/-m64 bi-arch is
> there I would feel happier if the binaries remained named as for cross
> compilation. Also if they did it would be easier to just switrch paths and

For (a), just use the cygwin cross compiler.  It should blend very
nicely with your cygwin environment, and it will have all of the
prefixed filenames.  The gcc executable itself will be a 32-bit
cygwin-linked exe running under WoW, whereas the gcc that you
downloaded is a native 64-bit exe linked only to the MSVCRT.  However,
if what you want is a cross compiler, you can use the cross compiler.

If you are building the toolchain yourself, you can achieve a native
toolchain with cross-compiled-esque prefixes with a configure option
(something like --program-transform-name or some such switch).

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] quick report on recent snapshots...

[NightStrike]

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 static so there is no runtime dependency.  I will
hopefully remember to do this next time.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] quick report on recent snapshots...

[NightStrike]

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 see things being used (and almost working, too!)

The stage you are at now is where we try to find what we call reduced
test cases -- the bare amount of code, 10 or 12 lines or whatever,
that causes an error.  If you could narrow that down, that would be
remarkably helpful.

For gdb, I don't know if that will only work with native compiled
binaries or not.  The cygwin cross compiler definitely would need
-mno-cygwin to avoid requiring the cygwin dll, which isn't ported to
Win64.

I will look more into your issue this evening.  It is very intriguing.
 I would say to fill out a support request ticket on the tracker so
that we can keep track of what's going on.  Also, I think maybe I'll
set up an IRC channel somewhere for this.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

[Mingw-w64-public] Just starting out...

[David Cleaver]

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.  I'd like to build gmp (and maybe 
someday 
mpfr, but that's secondary) and then other projects that depend on gmp.  I'm a 
bit lost and I've got a lot of questions, so I guess I'll get started:

1) Do I need to add "c:\mw64\bin" to my path?
2) Are there any additional folders that I need to add to my path?
3) Do I need to run this inside of msys or cygwin for it to work? Or will 
running it inside the windows 64-bit command prompt suffice? (with the right 
path(s) in place)
4) Why is "c:\mw64\bin\gcc.exe" a 0 byte file?
5) Do I need to make a shortcut (or similar?) to point that gcc.exe to 
"c:\mw64\bin\x86_64-pc-mingw32-gcc-4.4.0.exe"?
6) Why is c:\mw64\bin\x86_64-pc-mingw32-gcc.exe a 0 byte file?
7) Why are all the files in C:\mw64\x86_64-pc-mingw32\bin 0 byte files?
8) With several bin, include, and lib folders, do I need to put any or all in 
my 
path, or maybe: once I've put the correct bin in my path, the tools will find 
the appropriate lib/include that they need?

Well, that should get me started.  ;)  Thanks to anyone who would like to 
tackle 
these amateur-ish questions.

-David C.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Just starting out...

[NightStrike]

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 "c:\mw64".  I'm running Windows XP 64-bit edition and 
> would
> like to build 64-bit windows binaries.  I'd like to build gmp (and maybe 
> someday
> mpfr, but that's secondary) and then other projects that depend on gmp.  I'm a
> bit lost and I've got a lot of questions, so I guess I'll get started:
>
> 1) Do I need to add "c:\mw64\bin" to my path?

Yup.  I'd put it first, too:  PATH=C:\mw64\bin;%PATH%

> 2) Are there any additional folders that I need to add to my path?

Not that I know of.

> 3) Do I need to run this inside of msys or cygwin for it to work? Or will
> running it inside the windows 64-bit command prompt suffice? (with the right
> path(s) in place)

Running it in cygwin should fail, actually, because this binary
expects paths to be in Windows format (C:\...)  Using cmd.exe should
work just fine.

> 4) Why is "c:\mw64\bin\gcc.exe" a 0 byte file?

Erm..  because I made a big mistake?  Or maybe you did when extracting it :)

I really have to remember to use "-h" when making that tar file.  If
you use a real tar program and not winrar, it should work fine.  You
can use cygwin to extract it, or gnulib's tar, or some other tar
program.  With the next snapshot I make, I'll try to tar it better.

> 5) Do I need to make a shortcut (or similar?) to point that gcc.exe to
> "c:\mw64\bin\x86_64-pc-mingw32-gcc-4.4.0.exe"?

Nope.

> 6) Why is c:\mw64\bin\x86_64-pc-mingw32-gcc.exe a 0 byte file?

See above.

> 7) Why are all the files in C:\mw64\x86_64-pc-mingw32\bin 0 byte files?

See above.

> 8) With several bin, include, and lib folders, do I need to put any or all in 
> my
> path, or maybe: once I've put the correct bin in my path, the tools will find
> the appropriate lib/include that they need?

The binary should find the libraries automatically relative to where
it;s installed..

> Well, that should get me started.  ;)  Thanks to anyone who would like to 
> tackle
> these amateur-ish questions.

They're not amateur at all.  They're actually a good indicator for me
for mistakes that I'm making :) :)

Thanks for the feedback!

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Just starting out...

[David Cleaver]

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 files appear to be 
normal.

One thing I noticed, there was no make.exe available.  Perhaps its not supposed 
to be included?  Anyway, Since I have msys/mingw installed, I set my path to:
PATH=C:\mw64\bin;c:\msys\1.0\bin;%PATH%

And I now have access to make, m4, and various other things needed by gmp.  Is 
this the correct thing to do?

> Running it in cygwin should fail, actually, because this binary
> expects paths to be in Windows format (C:\...)  Using cmd.exe should
> work just fine.

I have another question, which may or may not belong on another list, but, is 
it 
possible to run shell scripts (./configure or ./config.guess)?  Now that I type 
this I'm thinking I should maybe run sh.  Ok, just tried that and when I run ls 
or dir it gives errors such as:

sh-2.04$ ls
C:\msys\1.0\bin\sh.exe: *** fork: can't reserve memory for stack 0x48 - 0x68
, Win32 error 0
   0 [main] sh 6992 sync_with_child: child 8544(0x2C0) died before 
initializa
tion with status code 0x1
1922 [main] sh 6992 sync_with_child: *** child state waiting for longjmp
sh: fork: Resource temporarily unavailable

Perhaps my sh is too old?  I'll try to update that here shortly.

>> 4) Why is "c:\mw64\bin\gcc.exe" a 0 byte file?
> 
> Erm..  because I made a big mistake?  Or maybe you did when extracting it :)

Yup, my fault.  The first program I tried was 7-zip.  Apparently I'm not using 
it correctly. :)  Or, maybe it's faulty!  ;)

> Thanks for the feedback!

And thank you for the quick (and very helpful) reply!  Please let me know what 
you (or anyone else) think about my above questions.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Just starting out...

[NightStrike]

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 called
> 7-zip) to re-extract all the files to c:\mw64, all the files appear to be 
> normal.

Sweet :)

> One thing I noticed, there was no make.exe available.  Perhaps its not 
> supposed
> to be included?  Anyway, Since I have msys/mingw installed, I set my path to:
> PATH=C:\mw64\bin;c:\msys\1.0\bin;%PATH%
>
> And I now have access to make, m4, and various other things needed by gmp.  Is
> this the correct thing to do?

That's what I'd do.  It makes life a little easier.  You can also look
at the gnuwin32 project for useful tools on the windows platform.
There's also MS's own Services for Unix (current version is 3.5), SFU
for short.

> > Running it in cygwin should fail, actually, because this binary
> > expects paths to be in Windows format (C:\...)  Using cmd.exe should
> > work just fine.
>
> I have another question, which may or may not belong on another list, but, is 
> it
> possible to run shell scripts (./configure or ./config.guess)?  Now that I 
> type
> this I'm thinking I should maybe run sh.  Ok, just tried that and when I run 
> ls
> or dir it gives errors such as:

configure requires bourne shell or compatible.  You won't get that
natively without possibly Microsoft's PowerShell.

One of these days I'll be able to port bash to native Windows.

> sh-2.04$ ls
> C:\msys\1.0\bin\sh.exe: *** fork: can't reserve memory for stack 0x48 - 
> 0x68
> , Win32 error 0
>   0 [main] sh 6992 sync_with_child: child 8544(0x2C0) died before 
> initializa
> tion with status code 0x1
>1922 [main] sh 6992 sync_with_child: *** child state waiting for longjmp
> sh: fork: Resource temporarily unavailable
>
> Perhaps my sh is too old?  I'll try to update that here shortly.

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
console window instead of rxvt.

> >> 4) Why is "c:\mw64\bin\gcc.exe" a 0 byte file?
> >
> > Erm..  because I made a big mistake?  Or maybe you did when extracting it :)
>
> Yup, my fault.  The first program I tried was 7-zip.  Apparently I'm not using
> it correctly. :)  Or, maybe it's faulty!  ;)

It's both of us.  I need to find a way to make these tar files
compatible with normal windows tools.  I think the issue comes down to
hard links.  What I might do is untar it using cygwin tar, then zip it
up again with WinRAR.  See, they're built originally on a linux
system.  It's a mess, I know

> > Thanks for the feedback!
>
> And thank you for the quick (and very helpful) reply!  Please let me know what
> you (or anyone else) think about my above questions.

They're exactly what this project needs.  Tell your friends! :)

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Re: [Mingw-w64-public] Just starting out...

[David Cleaver]

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
> console window instead of rxvt.

OK, I'm using msys.  I've figured out how to change the path there.  I went to 
gmp and ran "./configure --host=x86_64-pc-mingw32" and then came across an 
error.  While configure is running, it checks to see if it can find a working 
compiler.  It failed and said to check the log file.  When I looked in the log 
file, I came across this:

configure:3851: checking compiler x86_64-pc-mingw32-gcc -O2 -m64
Test compile:
configure:3865: x86_64-pc-mingw32-gcc -O2 -m64  conftest.c >&5
conftest.c: In function 'main':
conftest.c:2: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
configure:3868: $? = 1
failed program was:

int main () { return 0; }
configure:4874: result: no


Now, I tried to compile that same program on my own like:
x86_64-pc-mingw32-gcc -o test.exe test.c
And it worked fine.

But, when I tried it the way the config file tried it:
x86_64-pc-mingw32-gcc -O2 -m64  test.c
It failed, just like it did for the script.

Any ideas on what might be going wrong here?  It fails whether or not I use 
rxvt, so that shouldn't be an issue.

-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/
___
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public