Re: Our GCC-4.8 is broken

Cesar,

On 24/12/13 21:13, Cesar Strauss wrote:
> I avoided linking gcc to libintl by configuring gcc with --disable-nls. 
> This produced a build without any drive letters, which confirmed the 
> suspicion of libintl (gettext) being the vector.
> 
> The previous packaged version of gettext did not had this problem, so a 
> short term solution is to downgrade gettext and rebuild gcc and other 
> affected packages.

I've posted a new snapshot build of gettext-0.18.3.1 in my personal
project space at
https://sourceforge.net/projects/keithmarshall.u/files/mingw-gettext/

I've built this with with a mingw32-gcc-4.8.2 cross-compiler, which I
hope I've configured to be compatible with yours.  Perhaps you could
check this for suitability for formal release, please?

FWIW, I've packaged this using my own mingw-pkg tool, (still under
development, but I guess I should think about sharing it), and I've
tried to preserve the package layout Chuck had adopted for 0.18.1.1-2,
rather than Earnie's problematic layout of 0.18.3.1-1.  If you're
interested, I've added my package specification to the arch/mingw32
directory, within the source tarball.

-- 
Regards,
Keith.

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