delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2006/04/27/15:45:53

X-Spam-Check-By: sourceware.org
Date: Thu, 27 Apr 2006 21:45:29 +0200 (MET DST)
From: Angelo Graziosi <Angelo DOT Graziosi AT roma1 DOT infn DOT it>
To: cygwin AT cygwin DOT com
Subject: Re: Fixing the state of C++ in Cygwin
Message-ID: <Pine.OSF.4.21.0604272131130.16347-100000@ax0rm1.roma1.infn.it>
MIME-Version: 1.0
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019