Re: How many versions of clang/llvm are currently required to maintain a system
Hi, A big chunk of this is down to lang/pure. The upstream links for pure at bitbucket.org have mysteriously disappeared; those who care may get an uneasy feeling. > On 6 Mar 2017, at 07:16, Mark Linimon wrote: > > Please see https://wiki.freebsd.org/ObsoleteLLVMVersions . > > mcl > ___ > freebsd-curr...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" > -- Bob Bishop r...@gid.co.uk ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Future direction of virtualbox-ose port on FreeBSD
Hi, On 13 Apr 2011, at 12:38, Bernhard Froehlich wrote: > Hi VirtualBox users. > > I'm sending this because there are a few problems in how we currently > maintain the emulators/virtualbox-ose ports on FreeBSD. [etc] A question: woud there be any advantage in separating out the kernel module from the rest of it? Just asking, because I have no idea about the stability of the components and interfaces. -- Bob Bishop +44 (0)118 940 1243 r...@gid.co.ukfax +44 (0)118 940 1295 mobile +44 (0)783 626 4518 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
Hi, On 4 Jun 2007, at 16:14, Steve Kargl wrote: On Mon, Jun 04, 2007 at 09:43:03AM +0100, Bob Bishop wrote: [...]A better fix would be to make ports dependent on an appropriate compiler port, but that's a lot of work and some users will prefer ifc anyway. The work has already been done for most ports. Lapack is one of the few that doesn't use gfortran42 by default. See http://www.freebsd.org/cgi/getmsg.cgi?fetch=313584+318166+/usr/ local/www/db/text/2007/freebsd-ports/20070318.freebsd-ports OK, I wasn't aware of that good work because I don't read -ports. Thanks -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: /usr/share/mk/sys.mk and FORTRAN on -CURRENT
Hi, On 4 Jun 2007, at 02:09, Steve Kargl wrote: On Sun, Jun 03, 2007 at 04:47:33PM -0700, Don Lewis wrote: I was taking a look at why math/lapack fails to build on -CURRENT and discovered that the port uses ${FC} to find the FORTRAN compiler. I then discovered that /usr/share/mk/sys.mk defines ${FC} as f77 (or fort77). I don't this is appropriate since f77 has been removed from -CURRENT. I don't know what the proper fix is, but I though I should point out the problem ... There are two bugs here. 1) FC should be removed. Why? One might well want the option to use any of the several FORTRAN compilers from ports. 2) The various ports that use Fortran should use gfortran42 installed with lang/gcc42. The various ports that use Fortran should be checked to see what version of FORTRAN they want. I suspect the easiest fix is to have $FC empty by default and for dependent ports to output a helpful diagnostic. A better fix would be to make ports dependent on an appropriate compiler port, but that's a lot of work and some users will prefer ifc anyway. -- Steve -- Bob Bishop +44 (0)118 940 1243 [EMAIL PROTECTED] fax +44 (0)118 940 1295 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"