This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Fixing the state of C++ in Cygwin
- From: Angelo Graziosi <Angelo dot Graziosi at roma1 dot infn dot it>
- To: cygwin at cygwin dot com
- Date: Thu, 27 Apr 2006 21:45:29 +0200 (MET DST)
- Subject: Re: Fixing the state of C++ in Cygwin
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/