Re: Our GCC-4.8 is broken

On Sat, Jan 4, 2014 at 12:21 PM, Keith Marshall wrote:
>
> so even this exhibits one hard coded reference to /mingw/share/local,
> (with some drive specific prefix), which rather begs the question: why
> did this not propagate to your previous GCC release?  Or, did it, but it
> went unnoticed, because it refers to drive C:, which is less likely to
> become inaccessible?
>

This is my guess.  If it is cross-compiled from Linux the drive
specifier will disappear.  I suppose the rule-of-thumb for an MSYS
driven build is to always use C: as the work device to help avoid the
probability but there would still be some faction of the user base
that may experience the issue.

BTW: I am overly taxed on time at the moment and thus have been absent
from conversation and code input/output.  I don't expect that to
change before the 2nd or 3rd quarter of 2014.

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

------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT 
organizations don't have a clear picture of how application performance 
affects their revenue. With AppDynamics, you get 100% visibility into your 
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk