Re: Alexandre Julliard : configure: Don't accept mingw32 as target name, we need an explicit CPU specification.
On Fri, Jun 19, 2009 at 9:27 AM, Alexandre Julliard<julliard(a)winehq.org> wrote:
Module: wine Branch: master Commit: ccbf959969e32c9d71d2b4c46dbfe4db1ad2ab3f URL: http://source.winehq.org/git/wine.git/?a=commit;h=ccbf959969e32c9d71d2b4c46d...
Author: Alexandre Julliard <julliard(a)winehq.org> Date: Thu Jun 18 21:35:51 2009 +0200
configure: Don't accept mingw32 as target name, we need an explicit CPU specification.
I don't think this change is right. It is a very common convention to use mingw32 as a generic convention for 32bit x86. It seems the best practice would be if mingw32 is passed then to assume a sensible lowest common default. Thanks -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
Steven Edwards <winehacker(a)gmail.com> writes:
I don't think this change is right. It is a very common convention to use mingw32 as a generic convention for 32bit x86. It seems the best practice would be if mingw32 is passed then to assume a sensible lowest common default.
This is not a configure option, it's the name of the installed mingw32 binaries. They are supposed to follow the GNU naming convention for cross-compilers, and they do on all sane distros AFAIK. -- Alexandre Julliard julliard(a)winehq.org
On Fri, Jun 19, 2009 at 1:21 PM, Alexandre Julliard<julliard(a)winehq.org> wrote:
This is not a configure option, it's the name of the installed mingw32 binaries. They are supposed to follow the GNU naming convention for cross-compilers, and they do on all sane distros AFAIK.
Right I get that. I just mean that its pretty common to see homebrewed cross-compilers with just mingw32 as the prefix. The reason I guess is that on Windows (c:\mingw\bin\*) it does not follow the gnu naming convention because it does not have to follow it and people carry that over when they are rolling their own cross-compiler. Now that most distro's are shipping mingw packages this is less common. I guess your argument is right and anyone rolling their own should get with the program and follow the standard. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
On Fri, Jun 19, 2009 at 12:43 PM, Steven Edwards <winehacker(a)gmail.com>wrote:
On Fri, Jun 19, 2009 at 1:21 PM, Alexandre Julliard<julliard(a)winehq.org> wrote:
This is not a configure option, it's the name of the installed mingw32 binaries. They are supposed to follow the GNU naming convention for cross-compilers, and they do on all sane distros AFAIK.
Right I get that. I just mean that its pretty common to see homebrewed cross-compilers with just mingw32 as the prefix. The reason I guess is that on Windows (c:\mingw\bin\*) it does not follow the gnu naming convention because it does not have to follow it and people carry that over when they are rolling their own cross-compiler. Now that most distro's are shipping mingw packages this is less common. I guess your argument is right and anyone rolling their own should get with the program and follow the standard.
-- Steven Edwards
"There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
Fedora, Debian/Ubuntu, SUSE, and Mandriva come with complete toolkits that follow the GNU naming convention for the Win32 cross compiler.
On Friday 19 June 2009 10:21:33 am Alexandre Julliard wrote:
Steven Edwards <winehacker(a)gmail.com> writes:
I don't think this change is right. It is a very common convention to use mingw32 as a generic convention for 32bit x86. It seems the best practice would be if mingw32 is passed then to assume a sensible lowest common default.
This is not a configure option, it's the name of the installed mingw32 binaries. They are supposed to follow the GNU naming convention for cross-compilers, and they do on all sane distros AFAIK.
Gentoo names them with the mingw32- prefix only, on my 32-bit x86 install.
On Fri, Jun 19, 2009 at 4:21 PM, Chris Robinson<chris.kcat(a)gmail.com> wrote:
This is not a configure option, it's the name of the installed mingw32 binaries. They are supposed to follow the GNU naming convention for cross-compilers, and they do on all sane distros AFAIK.
Gentoo names them with the mingw32- prefix only, on my 32-bit x86 install.
Yes Gentoo is the only major odd-man out. We should send a patch upstream for its emerge overlay or whatever they call the think. -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
participants (4)
-
Alexandre Julliard -
Chris Robinson -
King InuYasha -
Steven Edwards