Re: Why so many ports have run-dependencies on non-system gcc versions?
On Friday 22 May 2009 02:00:29 Yuri wrote: When I tried to delete gcc-4.3.4_20090517 I got this message: pkg_delete: package 'gcc-4.3.4_20090517' is required by these other packages and may not be deinstalled: blas-1.0_3 cgnslib-2.5.3_1 fftw3-3.2 fftw3-float-3.2_1 fr-med-2.3.5 getdp-1.2.1_7 gmsh-2.3.1 lapack-3.2.1 libofa-0.9.3_3 libsamplerate-0.1.7_1 octave-3.0.5_1 suitesparse-3.3.0 Probably only fftw3 requires gcc43 and the rest comes from needing fftw3. As others said, it's not just building, it will need runtime libraries and in the case of fftw3, fortran support. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why so many ports have run-dependencies on non-system gcc versions?
On Fri, May 22, 2009 at 10:32:58AM +0200, Mel Flynn wrote: On Friday 22 May 2009 02:00:29 Yuri wrote: When I tried to delete gcc-4.3.4_20090517 I got this message: pkg_delete: package 'gcc-4.3.4_20090517' is required by these other packages and may not be deinstalled: blas-1.0_3 cgnslib-2.5.3_1 fftw3-3.2 fftw3-float-3.2_1 fr-med-2.3.5 getdp-1.2.1_7 gmsh-2.3.1 lapack-3.2.1 libofa-0.9.3_3 libsamplerate-0.1.7_1 octave-3.0.5_1 suitesparse-3.3.0 Probably only fftw3 requires gcc43 and the rest comes from needing fftw3. As others said, it's not just building, it will need runtime libraries and in the case of fftw3, fortran support. At least blas and lapack need gcc, by default gcc43, see /usr/ports/Mk/bsd.gcc.mk. I cannot build gcc43 on alpha-6.4, so I'm trying to switch to gcc44 by modifying bsd.gcc.mk. Not sure if this will not cause many other problems with other ports. -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 928 8233 Fax: +44 (0)117 929 4423 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Why so many ports have run-dependencies on non-system gcc versions?
When I tried to delete gcc-4.3.4_20090517 I got this message: pkg_delete: package 'gcc-4.3.4_20090517' is required by these other packages and may not be deinstalled: blas-1.0_3 cgnslib-2.5.3_1 fftw3-3.2 fftw3-float-3.2_1 fr-med-2.3.5 getdp-1.2.1_7 gmsh-2.3.1 lapack-3.2.1 libofa-0.9.3_3 libsamplerate-0.1.7_1 octave-3.0.5_1 suitesparse-3.3.0 When I tried to delete gcc-4.2.5_20090325 I got this: pkg_delete: package 'gcc-4.2.5_20090325' is required by these other packages and may not be deinstalled: pdftk-1.41 Why all these ports depend on gcc? They may want to compile with different gcc therefore incurring the build-dependency. But why I can't now uninstall those gccs? Looks like they are all run-dependency. Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Why so many ports have run-dependencies on non-system gcc versions?
Yuri wrote: When I tried to delete gcc-4.3.4_20090517 I got this message: pkg_delete: package 'gcc-4.3.4_20090517' is required by these other packages and may not be deinstalled: blas-1.0_3 cgnslib-2.5.3_1 fftw3-3.2 fftw3-float-3.2_1 fr-med-2.3.5 getdp-1.2.1_7 gmsh-2.3.1 lapack-3.2.1 libofa-0.9.3_3 libsamplerate-0.1.7_1 octave-3.0.5_1 suitesparse-3.3.0 When I tried to delete gcc-4.2.5_20090325 I got this: pkg_delete: package 'gcc-4.2.5_20090325' is required by these other packages and may not be deinstalled: pdftk-1.41 Why all these ports depend on gcc? They may want to compile with different gcc therefore incurring the build-dependency. But why I can't now uninstall those gccs? Looks like they are all run-dependency. gcc provides a shared library that some applications link to. Take for example: ccowart dev-aux bin $ ldd sabcmd sabcmd: libsablot.so.70 = /usr/local/lib/libsablot.so.70 (0x2807f000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28148000) libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x2823d000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x2825d000) libm.so.5 = /lib/libm.so.5 (0x28352000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x28367000) libc.so.7 = /lib/libc.so.7 (0x28372000) I can see this as being a real reason why a particular gcc needs to be around at runtime. Look at the dynamic linking information with ldd. If it doesn't depend on a file provided by those versions of gcc, it's probably an inaccuracy in the port's dependency list. -- Chris Cowart Network Technical Lead Network Infrastructure Services, RSSP-IT UC Berkeley pgpkstk5I4cJX.pgp Description: PGP signature
Re: Why so many ports have run-dependencies on non-system gcc versions?
On Thu 21 May 2009 at 17:26:06 PDT Chris Cowart wrote: gcc provides a shared library that some applications link to. Take for example: ccowart dev-aux bin $ ldd sabcmd sabcmd: libsablot.so.70 = /usr/local/lib/libsablot.so.70 (0x2807f000) libiconv.so.3 = /usr/local/lib/libiconv.so.3 (0x28148000) libexpat.so.6 = /usr/local/lib/libexpat.so.6 (0x2823d000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x2825d000) libm.so.5 = /lib/libm.so.5 (0x28352000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x28367000) libc.so.7 = /lib/libc.so.7 (0x28372000) I can see this as being a real reason why a particular gcc needs to be around at runtime. Look at the dynamic linking information with ldd. If it doesn't depend on a file provided by those versions of gcc, it's probably an inaccuracy in the port's dependency list. Here's the online documentation for libgcc, which describes what this library provides: http://gcc.gnu.org/onlinedocs/gccint/Libgcc.html Perhaps this lib should be made available as a seperate port that others could list as a dependency, rather than the full-blown compiler suite? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
