X-Spam-Check-By: sourceware.org Date: Thu, 27 Apr 2006 21:45:29 +0200 (MET DST) From: Angelo Graziosi To: cygwin AT cygwin DOT com Subject: Re: Fixing the state of C++ in Cygwin Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Charles Wilson wrote: > The whole point of the cygwin packaging system is that SUPPOSEDLY, if > you use the packaged script, you can rebuild the package exactly as the > official distributed one was built As I have written (http://cygwin.com/ml/cygwin/2006-04/msg00822.html), I used the packaged script (gcc-3.4.4-1.sh) but the packaging is a little different. For example, as it results from the script (and after executing gcc-3.4.4-1.sh pkg), libfrtbegin.a is moved in the directory i686-pc-cygwin instead that in i686-pc-cygwin/3.4.4, and g77 -print-file-name=libfrtbegin.a gives /usr/lib/gcc/i686-pc-cygwin/3.4.4/libfrtbegin.a (in which g77 is that just built) It looks that official distributed GCC-3.4.4-1 has been built with a little different script. Cheers, Angelo. -- 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/