Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Message-ID: <3E4EC408.8070500@ece.gatech.edu> Date: Sat, 15 Feb 2003 17:49:44 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130 X-Accept-Language: en-us, en MIME-Version: 1.0 Newsgroups: gmane.os.cygwin To: cygwin AT cygwin DOT com Subject: Re: [Problem] mempcpy is missing? (FAQ alert) References: <20030215210505 DOT GA29578 AT redhat DOT com> <010601c2d537$decb05c0$78d96f83 AT pomello> <20030215215840 DOT GA3446 AT redhat DOT com> In-Reply-To: <20030215215840.GA3446@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > Of course we're going to fix cygwin. I just checked in a fix. While I > assume this will probably be the end of it since no one will go to the > effort of trying to fix libintl's configury and, if they did, there > would probably be no official response anyway, the complete and correct > fix is to modify libintl. Then people using cygwin 1.3.10 - 1.3.20 > could benefit too. No, I'm going to fix gettext, thankyouverymuch. the thing that scares me, is I like to keep gettext, in particular, synced up with the official version. the reason is because gettextize is used to install the actual source code into a target package. By changing the code on cygwin, anyone maintaining a package on cygwin will generate different dist tarballs than if they were maintaining it on linux. Badness. So, I dunno if I should fold the change into our distribution and then push it to Bruno, or push it to Bruno and simply update cygwin's version when Bruno releases 0.11.6 --Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/