Re: Collision between libgfortran and gcc-libs
Qingshan Chen writes: > 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 gcc-libs is almost a requirement these days. I hope that we can just remove the .la from the gfortran package. This should go in a bulk build to ensure that nothing breaks. (Diff not tested) Index: Makefile === RCS file: /cvs/ports/lang/gfortran/Makefile,v retrieving revision 1.35 diff -u -p -r1.35 Makefile --- Makefile12 May 2016 01:17:13 - 1.35 +++ Makefile7 Jul 2016 11:10:00 - @@ -15,7 +15,7 @@ PKGNAME-lib = libgfortran-$V SHARED_LIBS = gfortran2.0 REVISION = 16 -REVISION-lib = 18 +REVISION-lib = 19 CATEGORIES = lang math @@ -108,5 +108,6 @@ post-install: ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/libgcc.a ${PREFIX}/lib/gcc/${CONFIG}/$V/libgcc.a ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/cc1 ${PREFIX}/libexec/gcc/${CONFIG}/$V/cc1 ${INSTALL_MAN} ${WRKBUILD}/gcc/doc/gfortran.1 ${PREFIX}/man/man1/gfortran.1 + rm ${PREFIX}/lib/libgfortran.la .include Index: pkg/PLIST-lib === RCS file: /cvs/ports/lang/gfortran/pkg/PLIST-lib,v retrieving revision 1.3 diff -u -p -r1.3 PLIST-lib --- pkg/PLIST-lib 19 Mar 2015 20:25:26 - 1.3 +++ pkg/PLIST-lib 7 Jul 2016 11:09:10 - @@ -6,6 +6,5 @@ lib/gcc/${CONFIG}/${V}/ lib/gcc/${CONFIG}/${V}/libgfortranbegin.a lib/gcc/${CONFIG}/${V}/libgfortranbegin.la lib/libgfortran.a -lib/libgfortran.la @lib lib/libgfortran.so.${LIBgfortran_VERSION} %%PIC%% -- jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Collision between libgfortran and gcc-libs
Could we just get rid of gfortran? It seems that nothing in ports is using it.. On 2016/07/07 13:16, Jeremie Courreges-Anglas wrote: > Qingshan Chen writes: > > > 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 > > gcc-libs is almost a requirement these days. I hope that we can just > remove the .la from the gfortran package. This should go in a bulk > build to ensure that nothing breaks. > > (Diff not tested) > > Index: Makefile > === > RCS file: /cvs/ports/lang/gfortran/Makefile,v > retrieving revision 1.35 > diff -u -p -r1.35 Makefile > --- Makefile 12 May 2016 01:17:13 - 1.35 > +++ Makefile 7 Jul 2016 11:10:00 - > @@ -15,7 +15,7 @@ PKGNAME-lib = libgfortran-$V > SHARED_LIBS =gfortran2.0 > > REVISION = 16 > -REVISION-lib = 18 > +REVISION-lib = 19 > > CATEGORIES = lang math > > @@ -108,5 +108,6 @@ post-install: > ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/libgcc.a > ${PREFIX}/lib/gcc/${CONFIG}/$V/libgcc.a > ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/cc1 > ${PREFIX}/libexec/gcc/${CONFIG}/$V/cc1 > ${INSTALL_MAN} ${WRKBUILD}/gcc/doc/gfortran.1 > ${PREFIX}/man/man1/gfortran.1 > + rm ${PREFIX}/lib/libgfortran.la > > .include > Index: pkg/PLIST-lib > === > RCS file: /cvs/ports/lang/gfortran/pkg/PLIST-lib,v > retrieving revision 1.3 > diff -u -p -r1.3 PLIST-lib > --- pkg/PLIST-lib 19 Mar 2015 20:25:26 - 1.3 > +++ pkg/PLIST-lib 7 Jul 2016 11:09:10 - > @@ -6,6 +6,5 @@ lib/gcc/${CONFIG}/${V}/ > lib/gcc/${CONFIG}/${V}/libgfortranbegin.a > lib/gcc/${CONFIG}/${V}/libgfortranbegin.la > lib/libgfortran.a > -lib/libgfortran.la > @lib lib/libgfortran.so.${LIBgfortran_VERSION} > %%PIC%% > > > > -- > jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE >
Re: Collision between libgfortran and gcc-libs
Stuart Henderson writes: > Could we just get rid of gfortran? It seems that nothing in ports is using > it.. I understand your point, but except for PLIST changes for releases, gfortran doesn't seem to add much maintenance overhead. And, as mentioned by the OP, there are still people using it. Given the number of files in patches/, it doesn't look like something that could be easily installed locally. :( I still propose that we try to resolve that conflict, diff (tested since first submission) below for convenience. Since you mention that nothing in ports uses it (I should have checked earlier), ok? Index: Makefile === RCS file: /cvs/ports/lang/gfortran/Makefile,v retrieving revision 1.35 diff -u -p -r1.35 Makefile --- Makefile12 May 2016 01:17:13 - 1.35 +++ Makefile7 Jul 2016 11:10:00 - @@ -15,7 +15,7 @@ PKGNAME-lib = libgfortran-$V SHARED_LIBS = gfortran2.0 REVISION = 16 -REVISION-lib = 18 +REVISION-lib = 19 CATEGORIES = lang math @@ -108,5 +108,6 @@ post-install: ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/libgcc.a ${PREFIX}/lib/gcc/${CONFIG}/$V/libgcc.a ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/cc1 ${PREFIX}/libexec/gcc/${CONFIG}/$V/cc1 ${INSTALL_MAN} ${WRKBUILD}/gcc/doc/gfortran.1 ${PREFIX}/man/man1/gfortran.1 + rm ${PREFIX}/lib/libgfortran.la .include Index: pkg/PLIST-lib === RCS file: /cvs/ports/lang/gfortran/pkg/PLIST-lib,v retrieving revision 1.3 diff -u -p -r1.3 PLIST-lib --- pkg/PLIST-lib 19 Mar 2015 20:25:26 - 1.3 +++ pkg/PLIST-lib 7 Jul 2016 11:09:10 - @@ -6,6 +6,5 @@ lib/gcc/${CONFIG}/${V}/ lib/gcc/${CONFIG}/${V}/libgfortranbegin.a lib/gcc/${CONFIG}/${V}/libgfortranbegin.la lib/libgfortran.a -lib/libgfortran.la @lib lib/libgfortran.so.${LIBgfortran_VERSION} %%PIC%% > On 2016/07/07 13:16, Jeremie Courreges-Anglas wrote: >> Qingshan Chen writes: >> >> > 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 >> >> gcc-libs is almost a requirement these days. I hope that we can just >> remove the .la from the gfortran package. This should go in a bulk >> build to ensure that nothing breaks. >> >> (Diff not tested) >> >> Index: Makefile >> === >> RCS file: /cvs/ports/lang/gfortran/Makefile,v >> retrieving revision 1.35 >> diff -u -p -r1.35 Makefile >> --- Makefile 12 May 2016 01:17:13 - 1.35 >> +++ Makefile 7 Jul 2016 11:10:00 - >> @@ -15,7 +15,7 @@ PKGNAME-lib = libgfortran-$V >> SHARED_LIBS = gfortran2.0 >> >> REVISION = 16 >> -REVISION-lib = 18 >> +REVISION-lib = 19 >> >> CATEGORIES =lang math >> >> @@ -108,5 +108,6 @@ post-install: >> ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/libgcc.a >> ${PREFIX}/lib/gcc/${CONFIG}/$V/libgcc.a >> ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/cc1 >> ${PREFIX}/libexec/gcc/${CONFIG}/$V/cc1 >> ${INSTALL_MAN} ${WRKBUILD}/gcc/doc/gfortran.1 >> ${PREFIX}/man/man1/gfortran.1 >> +rm ${PREFIX}/lib/libgfortran.la >> >> .include >> Index: pkg/PLIST-lib >> === >> RCS file: /cvs/ports/lang/gfortran/pkg/PLIST-lib,v >> retrieving revision 1.3 >> diff -u -p -r1.3 PLIST-lib >> --- pkg/PLIST-lib19 Mar 2015 20:25:26 - 1.3 >> +++ pkg/PLIST-lib7 Jul 2016 11:09:10 - >> @@ -6,6 +6,5 @@ lib/gcc/${CONFIG}/${V}/ >> lib/gcc/${CONFIG}/${V}/libgfortranbegin.a >> lib/gcc/${CONFIG}/${V}/libgfortranbegin.la >> lib/libgfortran.a >> -lib/libgfortran.la >> @lib lib/libgfortran.so.${LIBgfortran_VERSION} >> %%PIC%% >> >> >> >> -- >> jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE >> > -- jca | PGP:
Re: Collision between libgfortran and gcc-libs
On Thu, Jul 07, 2016 at 01:16:48PM +0200, Jeremie Courreges-Anglas wrote: > Qingshan Chen writes: > > > 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 > > gcc-libs is almost a requirement these days. I hope that we can just > remove the .la from the gfortran package. This should go in a bulk > build to ensure that nothing breaks. > That solves the collision, but now you have libgfortran 2.0 and 6.0 installed. gfortran will presumably pick up the newer library belonging to g95. That cant be a good thing. Qingshan: Anything stopping you from using the g95 package instead of gfortran?
Re: Collision between libgfortran and gcc-libs
> 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. > > > On 2016/07/07 13:16, Jeremie Courreges-Anglas wrote: >> Qingshan Chen writes: >> >> > 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 >> >> gcc-libs is almost a requirement these days. I hope that we can just >> remove the .la from the gfortran package. This should go in a bulk >> build to ensure that nothing breaks. >> >> (Diff not tested) >> >> Index: Makefile >> === >> RCS file: /cvs/ports/lang/gfortran/Makefile,v >> retrieving revision 1.35 >> diff -u -p -r1.35 Makefile >> --- Makefile12 May 2016 01:17:13 -1.35 >> +++ Makefile7 Jul 2016 11:10:00 - >> @@ -15,7 +15,7 @@ PKGNAME-lib =libgfortran-$V >> SHARED_LIBS =gfortran2.0 >> >> REVISION = 16 >> -REVISION-lib = 18 >> +REVISION-lib = 19 >> >> CATEGORIES =lang math >> >> @@ -108,5 +108,6 @@ post-install: >> ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/libgcc.a > ${PREFIX}/lib/gcc/${CONFIG}/$V/libgcc.a >> ln -sf /usr/lib/gcc-lib/${CONFIG}/${SYSV}/cc1 > ${PREFIX}/libexec/gcc/${CONFIG}/$V/cc1 >> ${INSTALL_MAN} ${WRKBUILD}/gcc/doc/gfortran.1 > ${PREFIX}/man/man1/gfortran.1 >> +rm ${PREFIX}/lib/libgfortran.la >> >> .include >> Index: pkg/PLIST-lib >> === >> RCS file: /cvs/ports/lang/gfortran/pkg/PLIST-lib,v >> retrieving revision 1.3 >> diff -u -p -r1.3 PLIST-lib >> --- pkg/PLIST-lib19 Mar 2015 20:25:26 -1.3 >> +++ pkg/PLIST-lib7 Jul 2016 11:09:10 - >> @@ -6,6 +6,5 @@ lib/gcc/${CONFIG}/${V}/ >> lib/gcc/${CONFIG}/${V}/libgfortranbegin.a >> lib/gcc/${CONFIG}/${V}/libgfortranbegin.la >> lib/libgfortran.a >> -lib/libgfortran.la >> @lib lib/libgfortran.so.${LIBgfortran_VERSION} >> %%PIC%% >> >> >> >> -- >> jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE >> >
Re: Collision between libgfortran and gcc-libs
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.
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.
Re: Collision between libgfortran and gcc-libs
Tobias Ulmer writes: > On Thu, Jul 07, 2016 at 01:16:48PM +0200, Jeremie Courreges-Anglas wrote: >> Qingshan Chen writes: >> >> > 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 >> >> gcc-libs is almost a requirement these days. I hope that we can just >> remove the .la from the gfortran package. This should go in a bulk >> build to ensure that nothing breaks. >> > > That solves the collision, but now you have libgfortran 2.0 and 6.0 > installed. gfortran will presumably pick up the newer library belonging > to g95. That cant be a good thing. > > Qingshan: Anything stopping you from using the g95 package instead of > gfortran? Just like Qingshan I thought that lang/gfortran was the real deal. I should have looked closer. Let's forget about the conflict. sthen and you proposed to delete lang/gfortran: I think that's a good idea. -- jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
Re: Collision between libgfortran and gcc-libs
Il 12 luglio 2016 19:21:33 CEST, j...@wxcvbn.org ha scritto: >Just like Qingshan I thought that lang/gfortran was the real deal. >I should have looked closer. Let's forget about the conflict. sthen >and you proposed to delete lang/gfortran: I think that's a good idea. +1 for nuking it from me too. Ciao! David
Re: Collision between libgfortran and gcc-libs
On Tue, Jul 12, 2016 at 07:37:52PM +0200, David Coppa wrote: > > +1 for nuking it from me too. > > Ciao! > David > > I believe that spatstat module in R requires lang/gfortran to compile. Some other useful modules depend on spatstat, e.g. radiomics. Please do not delete lang/gfortran, I am interested to fix it, if possible. Thanks, Alex
Re: Collision between libgfortran and gcc-libs
On Wed, Jul 13, 2016 at 11:26:46AM +1200, m...@extensibl.com wrote: > On Tue, Jul 12, 2016 at 07:37:52PM +0200, David Coppa wrote: > > > > +1 for nuking it from me too. > > > > Ciao! > > David > > > > > I believe that spatstat module in R requires lang/gfortran to compile. Some > other useful modules depend on spatstat, e.g. radiomics. > > Please do not delete lang/gfortran, I am interested to fix it, if possible. Not true, I just installed it without having lang/gfortran installed. > Thanks, > Alex > --
Re: Collision between libgfortran and gcc-libs
On Wed, 13 Jul 2016 08:59:49 +0100 Zé Loff wrote: > Not true, I just installed it without having lang/gfortran installed. While spatstat does not depend directly on gfortran, its dependency, deldir, does. Did you compile deldir with g77? I think gfortran could be removed then.
Re: Collision between libgfortran and gcc-libs
On Wed, Jul 13, 2016 at 08:55:24PM +1200, m...@extensibl.com wrote: > On Wed, 13 Jul 2016 08:59:49 +0100 > Zé Loff wrote: > > > Not true, I just installed it without having lang/gfortran installed. > > While spatstat does not depend directly on gfortran, its dependency, > deldir, does. Did you compile deldir with g77? I think gfortran could > be removed then. Incidentally it was with g95 (I needed GCC 4.9 to compile some other R packages) but yes, deldir was also installed as a dependency without lang/gfortran. Cheers Zé --