This is the mail archive of the cygwin-apps mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC] GCC-4 new packaging.


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Dave Korn wrote:
>   I have .... whatever version of libffi was in the GCC tree at the time 4.3
> was branched.  I don't know how closely tied to the particular API the
> compiler is.  This means that if I create a libffi-devel package, it could
> clash with a cygwin ports installation, and users might get a mismatch (cygwin
> ports libffi5 with gcc-4 libffi-devel for libffi4.
> 
>   I'm not sure what to do about this yet.  Yaakov, any ideas?

AFAICS in Debian sid, the only libffi is provided by the new standalone
libffi-3.0.8, not by gcc-4.3.  That is a change from etch, where
libffi4{,-dev} comes from gcc-4.1.  Can gcc-4.3 be configured to use the
new libffi instead of its own version?

If not, then I would suggest moving gcc's libffi together with the other
GCC libraries, and I'll move my standalone libffi out of /usr/lib as
well to avoid any problems.

(BTW, your libtool patch to force the DLLs of non-module libraries which
are deeper than ${prefix}/lib into ${prefix}/bin should be considered
for inclusion in libtool itself, as gcc is not unique in that regard.)

Also, will a binutils update be required as well for proper usage of
shared libstdc++ and friends?


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAkmRzW4ACgkQpiWmPGlmQSOPfwCg4VQoPuwwKiHU0KjR/6wbOGWO
h78Anjj139bxqRE7Oso/crogtBQReGMQ
=Deic
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]