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] |
On 6/17/2013 06:24, JonY wrote: Oops, sorry dropped the list. > On 6/17/2013 00:48, Yaakov (Cygwin/X) wrote: >> On 2013-06-16 06:48, JonY wrote: >>> I noticed some deps are still marked as experimental, eg >>> cloog/ppl/mpc/mpfr/gmp. Parts of the experimental ppl even requires >>> experimental 4.7.x libstdc++. >> >> For gcc-4.7, we need the test versions of all those deps. >> >>> setup constantly tries to revert it to stable versions. >> >> That's just how setup (mis)handles test releases. >> >>> Should I still put gcc 4.7.3-1 as experimental? >> >> No, I think we just need to stabilize it and its deps, obsoleting >> 'gcc4', 'gcc' 3.x and 'gcc-mingw-' in the process. >> > > gcc4? > > Anyway, like Achim says, I was thinking to push to experimental. Once > upload is complete, someone will change the setup.hint files, gcc and > its deps over to stable, so there won't be any gaps when gcc install > will potentially be broken. > > For the record, here are the deps stated by cygport: > > On 6/17/2013 00:48, Yaakov (Cygwin/X) wrote: >>>>> gcc requires: gcc-core gcc-g++ >>>>> gcc-core requires: bash libcloog0 libgcc1 libgmp3 libgomp1 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 libquadmath0 libssp0 zlib0 binutils w32api-headers w32api-runtime >>>>> gcc-g++ requires: libcloog0 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 libstdc++6 python python3 zlib0 gcc-core >>>>> gcc-java requires: bash libcloog0 libgcc1 libgcj13 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 python python3 zlib0 gcc-core java-ecj >>>>> gcc-fortran requires: libcloog0 libgfortran3 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 zlib0 gcc-core >>>>> gcc-objc requires: libcloog0 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libobjc4 libppl_c4 zlib0 gcc-core >>>>> gcc-objc++ requires: libcloog0 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 zlib0 gcc-core gcc-g++ gcc-objc >>>>> gcc-ada requires: libcloog0 libgmp3 libiconv2 libintl8 libmpc3 libmpfr4 libppl_c4 zlib0 gcc-core >>>>> libgcc1 requires: >>>>> libgomp1 requires: libgcc1 >>>>> libssp0 requires: >>>>> libgfortran3 requires: libgcc1 libquadmath0 >>>>> libgcj-common requires: >>>>> libobjc4 requires: libgcc1 >>>>> libstdc++6 requires: libgcc1 >>>>> libstdc++6-devel requires: >>>>> libgnat4.7 requires: libgcc1 >>>>> libgcj13 requires: libgcc1 libiconv2 zlib0 libgcj-common >>>>> libquadmath0 requires: libgcc1 > > Sounds doable? Alternatively, the current experimental gcc 4.7.2 and its > dep be made stable before 4.7.3 is pushed, after all, I did use 4.7.2 to > build the new gcc, it is stable enough. > Doable?
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |