From: J. G. <jg-...@jg...> - 2004-01-17 14:53:09
|
Hello, Could this be clarified a little please. Could the build info be added, e.g.: "equal to the build, (which was xxxxxxx)". It is not completly clear which build it is refering to. Kind regards JG http://mingw.org/mingwfaq.shtml#faq-mingw32-gcc.exe ______________ What's the difference between gcc.exe and mingw32-gcc.exe? The mingw32-gcc, mingw32-g++, etc. binaries exist as an aid to cross development. They are created in a typical build of gcc. They are therefore distributed as the maintainers of GCC meant them to be. The gcc.exe indicates that the binary produces binaries for a target equal to the build, while the mingw32-gcc binary produces binaries to be executed on the mingw32 target. _________ |
From: Earnie B. <ea...@us...> - 2004-01-19 12:56:54
|
That would be "a target environment equal to the build environment". Earnie. J. Grant wrote: > Hello, > > Could this be clarified a little please. Could the build info be added, > e.g.: "equal to the build, (which was xxxxxxx)". It is not completly > clear which build it is refering to. > > Kind regards > > JG > > > > http://mingw.org/mingwfaq.shtml#faq-mingw32-gcc.exe > ______________ > What's the difference between gcc.exe and mingw32-gcc.exe? > > The mingw32-gcc, mingw32-g++, etc. binaries exist as an aid to cross > development. They are created in a typical build of gcc. They are > therefore distributed as the maintainers of GCC meant them to be. The > gcc.exe indicates that the binary produces binaries for a target equal > to the build, while the mingw32-gcc binary produces binaries to be > executed on the mingw32 target. > > _________ > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > -- http://www.mingw.org http://sourceforge.net/projects/mingw https://sourceforge.net/donate/index.php?user_id=15438 |
From: J. G. <jg-...@jg...> - 2004-01-19 21:23:52
|
Repeating does not necessarily clarify the entry. I the point this FAQ entry tries to explain is that mingw32-gcc.exe was not compiled natively using a mingw32 compiler and was actually built using a non-mingw32 hosted distribution of gcc etc. I do not think the FAQ entry makes this point successfully. People reading this are likely not going to be gcc developers, thus I think it should be made clearer. I propose a revision to this FAQ entry: __________________________________________________________ What's the difference between gcc.exe and mingw32-gcc.exe? The mingw32-gcc.exe, mingw32-g++.exe, etc. binaries, were compiled using a cross compiler targeting mingw32, from a non-mingw32 build of gcc. These binaries produce binaries to be executed on the mingw32 target. They are therefore distributed as the maintainers of GCC meant them to be. The gcc.exe, g++.exe, etc. binaries were actually compiled from a mingw32 gcc build environment, as well as themselves targeting mingw32. Typically these binaries are identical sizes. __________________________________________________________ I think this is clearer, would you consider using this entry please? Kind regards JG on the 19/01/04 12:56, Earnie Boyd wrote: > That would be "a target environment equal to the build environment". |
From: <dan...@ya...> - 2004-01-19 21:53:16
|
--- "J. Grant" <jg-...@jg...> wrote: > Repeating does not necessarily clarify the entry. > > I propose a revision to this FAQ entry: > > __________________________________________________________ > What's the difference between gcc.exe and mingw32-gcc.exe? > > The mingw32-gcc.exe, mingw32-g++.exe, etc. binaries, were compiled using > a cross compiler targeting mingw32, from a non-mingw32 build of gcc. > These binaries produce binaries to be executed on the mingw32 target. > They are therefore distributed as the maintainers of GCC meant them to > be. The gcc.exe, g++.exe, etc. binaries were actually compiled from a > mingw32 gcc build environment, as well as themselves targeting mingw32. > Typically these binaries are identical sizes. That is wrong. All the binaries were built natively, using make bootstrap. mingw32-gcc.exe is a copy of gcc.exe. Danny > __________________________________________________________ > > > I think this is clearer, would you consider using this entry please? > > Kind regards > > > JG > > > > on the 19/01/04 12:56, Earnie Boyd wrote: > > That would be "a target environment equal to the build environment". > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users http://personals.yahoo.com.au - Yahoo! Personals New people, new possibilities. FREE for a limited time. |
From: <tr...@mx...> - 2004-01-19 23:19:15
|
----- Original Message ----- From: "Danny Smith" <dan...@ya...> To: <min...@li...> Sent: Monday, January 19, 2004 10:53 PM Subject: Re: [Mingw-users] FAQ clarification request > --- "J. Grant" <jg-...@jg...> wrote: > Repeating does not necessarily clarify the entry. > > > > I propose a revision to this FAQ entry: > > > > __________________________________________________________ > > What's the difference between gcc.exe and mingw32-gcc.exe? > > > > The mingw32-gcc.exe, mingw32-g++.exe, etc. binaries, were compiled using > > a cross compiler targeting mingw32, from a non-mingw32 build of gcc. > > These binaries produce binaries to be executed on the mingw32 target. > > They are therefore distributed as the maintainers of GCC meant them to > > be. The gcc.exe, g++.exe, etc. binaries were actually compiled from a > > mingw32 gcc build environment, as well as themselves targeting mingw32. > > Typically these binaries are identical sizes. > > That is wrong. All the binaries were built natively, using make bootstrap. > mingw32-gcc.exe is a copy of gcc.exe. I don't think so. In build I have (think 3.2.3) gcc.exe and mingw32-gcc.exe differs in two bytes! :-) > > Danny > > __________________________________________________________ > > > > > > I think this is clearer, would you consider using this entry please? > > > > Kind regards > > > > > > JG > > > > > > > > on the 19/01/04 12:56, Earnie Boyd wrote: > > > That would be "a target environment equal to the build environment". > > --- Jan Ringos, Tr...@mx... http://tringi.mx-3.cz senior programmer-analyst n.v.t. MX-3, www.mx-3.cz |
From: J. G. <jg-...@jg...> - 2004-01-20 00:08:21
|
> That is wrong. All the binaries were built natively, using make bootstrap. > mingw32-gcc.exe is a copy of gcc.exe. Are you sure? In which case, which "native" compiler of win32 is used, and where can I download it please? If this native compile is gcc, how was it compiled natively for win32 initially? Seems like no one is completely clear what the FAQ entry was aimed at indicating, or what is the actual practice is. Could someone "in the know" clarify clearly please? JG |
From: <dan...@ya...> - 2004-01-20 00:28:22
|
--- "J. Grant" <jg-...@jg...> wrote: > > > That is wrong. All the binaries were built natively, using make bootstrap. > > mingw32-gcc.exe is a copy of gcc.exe. > > Are you sure? Yes I'm sure about the binaries distributed by mingw.org In which case, which "native" compiler of win32 is used, > and where can I download it please? If this native compile is gcc, how > was it compiled natively for win32 initially? I used mingw build of gcc to build gcc. Earlier builds of mingw gcc (2.95.2 and earlier) were cross-compiled on linux I think. > > Seems like no one is completely clear what the FAQ entry was aimed at > indicating, or what is the actual practice is. Could someone "in the > know" clarify clearly please? Here is how gcc.exe and mingw32-gcc.exe come into the world (from the Makefile): # Install the driver program as $(target_noncanonical)-gcc, # $(target_noncanonical)-gcc-$(version) # and also as either gcc (if native) or $(gcc_tooldir)/bin/gcc. install-driver: installdirs xgcc$(exeext) -rm -f $(DESTDIR)$(bindir)/$(GCC_INSTALL_NAME)$(exeext) -$(INSTALL_PROGRAM) xgcc$(exeext) $(DESTDIR)$(bindir)/$(GCC_INSTALL_NAME)$(exeext) -rm -f $(DESTDIR)$(bindir)/$(target_noncanonical)-gcc-$(version) -( cd $(DESTDIR)$(bindir) && \ $(LN) $(GCC_INSTALL_NAME)$(exeext) $(target_noncanonical)-gcc-$(version) ) -if [ -f gcc-cross$(exeext) ] ; then \ if [ -d $(DESTDIR)$(gcc_tooldir)/bin/. ] ; then \ rm -f $(DESTDIR)$(gcc_tooldir)/bin/gcc$(exeext); \ $(INSTALL_PROGRAM) gcc-cross$(exeext) $(DESTDIR)$(gcc_tooldir)/bin/gcc$(exeext); \ else true; fi; \ else \ rm -f $(DESTDIR)$(bindir)/$(target_noncanonical)-gcc-tmp$(exeext); \ ( cd $(DESTDIR)$(bindir) && \ $(LN) $(GCC_INSTALL_NAME)$(exeext) $(target_noncanonical)-gcc-tmp$(exeext) && \ mv -f $(target_noncanonical)-gcc-tmp$(exeext) $(GCC_TARGET_INSTALL_NAME)$(exeext) ); \ fi in this case $(target_noncanonical) = "mingw32" and $(LN) is effectively cp Danny > > JG > > http://personals.yahoo.com.au - Yahoo! Personals New people, new possibilities. FREE for a limited time. |
From: Dave M. <win...@nt...> - 2004-01-20 00:39:56
|
the native compiler is mingw. normally under linux gcc is installed in it's own directory for each target and symbolic links are made to the binaries from the main gcc directory. Unfortunately this behavior results in copies of the files being made under windows, but some of the other tools expect to find (target prefix)-gcc etc so they're still required (afaik) Dave > -----Original Message----- > From: min...@li... > [mailto:min...@li...]On Behalf Of J. Grant > Sent: 20 January 2004 00:13 > To: min...@li... > Subject: Re: [Mingw-users] FAQ clarification request > > > > > That is wrong. All the binaries were built natively, using > make bootstrap. > > mingw32-gcc.exe is a copy of gcc.exe. > > Are you sure? In which case, which "native" compiler of win32 is used, > and where can I download it please? If this native compile is gcc, how > was it compiled natively for win32 initially? > > Seems like no one is completely clear what the FAQ entry was aimed at > indicating, or what is the actual practice is. Could someone "in the > know" clarify clearly please? > > JG > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > MinGW-users mailing list > Min...@li... > > You may change your MinGW Account Options or unsubscribe at: > https://lists.sourceforge.net/lists/listinfo/mingw-users > |
From: J. G. <jg-...@jg...> - 2004-01-28 01:35:24
|
[Reposted as first attempt never arrived, sc8-sf-list1-b.sourceforge.net, 421 Unexpected failure, please try later] The FAQ still seems to not correspond with the way it is. Is this entry is out of date? Did represent the way mingw gcc used to be built? (now they are just identical files from same build). When a new gcc release is made, is gcc is first compiled with previous version? Then built again with the that version to get the "gcc recompiled with self" exe? Can someone simply adjust the FAQ entry to clearly represent the way it is please? Regards JG on the 20/01/04 00:46, Dave Murphy wrote: > the native compiler is mingw. > > normally under linux gcc is installed in it's own directory for each target > and symbolic links are made to the binaries from the main gcc directory. > Unfortunately this behavior results in copies of the files being made under > windows, but some of the other tools expect to find (target prefix)-gcc etc > so they're still required (afaik) > > Dave |
From: J. G. <jg-...@jg...> - 2004-01-26 22:45:47
|
So, FAQ still seems to not correspond with the way it is. Is this entry is out of date, and did represent the way mingw gcc used to be built (now they are just identical files from same build). When a new gcc release is made, is gcc is first compiled with previous version? Then built again with the that version to get the "gcc recompiled with self" exe? Can someone simply adjust the FAQ entry to clearly represent the way it is please? Regards JG on the 20/01/04 00:46, Dave Murphy wrote: > the native compiler is mingw. > > normally under linux gcc is installed in it's own directory for each target > and symbolic links are made to the binaries from the main gcc directory. > Unfortunately this behavior results in copies of the files being made under > windows, but some of the other tools expect to find (target prefix)-gcc etc > so they're still required (afaik) > > Dave |