Collision between libgfortran and gcc-libs
Sorry for the double posting here. The message was originally posted on m...@openbsd.org, and is being re-posted here, in the hope of reaching the right people. Hi All, It seems that gcc-libs-4.9.3p3 collides with libgfortran-4.3.1p16, which is required by gfortran-4.2.1p15. I have run into this issue a couple of times, when I tried to install various packages. The following message appeared when I tried to install gnucash, which requires webkit-2.4.9p4v1, which in turn requires gcc-libs-4.9.3p3: Collision in gcc-libs-4.9.3p3: the following files already exist /usr/local/lib/libgfortran.la (libgfortran-4.2.1p16 and gcc-libs-4.9.3p3) Can't install webkit-2.4.9p4v1: can't resolve gcc-libs-4.9.3p3 I installed OpenBSD recently, on this Toshiba Satellite L505 laptop, and I have applied all the published security patches. Beyond that, I have no idea how to resolve this collision issue. I do need to keep this gfortran package on my system for my scientific research. Any suggestions will be greatly appreciated. Thanks! Best, Qingshan
Re: Collision between libgfortran and gcc-libs
On 07/10/16 01:00, Stuart Henderson wrote: On 2016/07/09 15:47, Thomas Frohwein wrote: On Friday, July 8, 2016 1:10 PM, Stuart Henderson wrote: Could we just get rid of gfortran? It seems that nothing in ports is using it.. Some R packages require gfortran to be built. I managed to install gfortran a few weeks ago by manually removing the gcc file that was colliding. However, the R package (I think it was knitr) required a newer version of gfortran, so I had to make do without that package. The newer version of gfortran is in the g95 package, the executable is called egfortran. This is interesting. I was confused at first. There is a G95 project, which is not part of GNU GCC project, but aims to produce a modern high quality Fortran compiler. G95 has quite some followers. See www.g95.org As you mentioned, the executable of the g95 package is egfortran. The output of 'egfortran -v' does suggest that it is a newer version of the GCC Fortran compiler. In this case, I am not against removing the older gfortran package, though I am a little worried that the mismatch between the versions of gcc and gfortran might cause problems in some situations.
Re: Collision between libgfortran and gcc-libs
On 07/10/16 14:10, Qingshan Chen wrote: On 07/10/16 01:00, Stuart Henderson wrote: On 2016/07/09 15:47, Thomas Frohwein wrote: On Friday, July 8, 2016 1:10 PM, Stuart Henderson wrote: Could we just get rid of gfortran? It seems that nothing in ports is using it.. Some R packages require gfortran to be built. I managed to install gfortran a few weeks ago by manually removing the gcc file that was colliding. However, the R package (I think it was knitr) required a newer version of gfortran, so I had to make do without that package. The newer version of gfortran is in the g95 package, the executable is called egfortran. This is interesting. I was confused at first. There is a G95 project, which is not part of GNU GCC project, but aims to produce a modern high quality Fortran compiler. G95 has quite some followers. See www.g95.org As you mentioned, the executable of the g95 package is egfortran. The output of 'egfortran -v' does suggest that it is a newer version of the GCC Fortran compiler. In this case, I am not against removing the older gfortran package, though I am a little worried that the mismatch between the versions of gcc and gfortran might cause problems in some situations. I take back my last sentence. A newer version of gcc, matching egfortran, is also available, and it is called egcc.
