Re: gcc4.8.0 build and package

Earnie Boyd <[email protected]> Tue, 23 Apr 2013 18:35:00 -0400
Newsgroups gmane.comp.gnu.mingw.devel
Message-ID <CA+sc5mmnKakKpyGWotk=TC30oOXqAhP31305hH6=1a078Mh39Q@mail.gmail.com>
On Tue, Apr 23, 2013 at 5:27 PM, arthur wrote:
> On 22/04/2013 12:40 PM, arthur wrote:
>> 2. build with '--build=i686-pc-mingw32'
> ....
>
>> Also the bin\mingw32-*.exe will become bin\i686-pc-mingw32-*.exe
>
> I just notice that those bin\mingw32-*.exe are wrapper executables so I
> think even the gcc install will install bin\i686-pc-mingw32-*.exe then
> we still can mv them as bin\mingw32-*.exe (after overwritten as wrapper
> exes).
>
> Do you want we keep as bin\mingw32-*.exe (as today) or keep as
> bin\i686-pc-mingw32-*.exe (as gcc 4.8.0 installed).

I don't see the point.  They're actually used for cross compiling so
let the i686-pc-mingw32-*.exe replace them.  The mingw-get process
should remove the mingw32-*.exe IIRC when the upgrade occurs.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr