X-Spam-Check-By: sourceware.org Date: Sat, 3 Mar 2007 11:16:13 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: missing definition of __STRING macro in standard cygwin headers Message-ID: <20070303161613.GA18671@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000001c75d7b$f1a52100$05ffa8c0 AT Hydrogen> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000001c75d7b$f1a52100$05ffa8c0@Hydrogen> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Sat, Mar 03, 2007 at 12:08:50PM +0200, Jaakko P??kk?nen wrote: >...cygwin doesn't have >#define __STRING #x >defined in any of the standard header files which means some source code >won't compile out of the box (FAAC library in this case). Hacking up all the >software by inserting that bit into source headers fixes the problem but I >seriously think this should be fixed in the system. http://cygwin.com/lists.html#cygwin-patches cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/