From owner-freebsd-fortran@FreeBSD.ORG Wed Sep 10 03:40:47 2014 Return-Path: Delivered-To: fortran@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B631EB6C; Wed, 10 Sep 2014 03:40:47 +0000 (UTC) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "troutmask.apl.washington.edu", Issuer "troutmask.apl.washington.edu" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 78C43C20; Wed, 10 Sep 2014 03:40:47 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.9/8.14.9) with ESMTP id s8A3ek8a070583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 9 Sep 2014 20:40:46 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.9/8.14.9/Submit) id s8A3ekSC070582; Tue, 9 Sep 2014 20:40:46 -0700 (PDT) (envelope-from sgk) Date: Tue, 9 Sep 2014 20:40:46 -0700 From: Steve Kargl To: Pedro Giffuni Subject: Re: Help with gfortran Message-ID: <20140910034045.GB70488@troutmask.apl.washington.edu> References: <540E18DB.3020006@freebsd.org> <540FA812.1050606@freebsd.org> <20140910022632.GA70317@troutmask.apl.washington.edu> <540FC32E.6000305@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <540FC32E.6000305@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: fortran@FreeBSD.org X-BeenThere: freebsd-fortran@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Fortran on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Sep 2014 03:40:47 -0000 On Tue, Sep 09, 2014 at 10:19:10PM -0500, Pedro Giffuni wrote: > > On 09/09/14 21:26, Steve Kargl wrote: > > On Tue, Sep 09, 2014 at 08:23:30PM -0500, Pedro Giffuni wrote: > >> While here, I think it should be possible to drop libstdc++ into an > >> independent port and have all the g++ ports use libc++ by default. > >> > > I'm no expert on this, but I suspect that g++ will be unhappy with > > libc++. libstdc++ and libc++ simply are incompatible. > > > > It should be somewhat like using stlport with g++ and libc++ > supports the standards well enough that it should just work. The problem is that libc++ doesn't support GNU C++. > At least the contrary; having libstdc++ work compatibly with > clang, is already possible: > > http://clang.llvm.org/cxx_status.html > I suspect that that is not even close to what is needed. Last time I tried to use news/pan, it died a miserable death. It uses a g++-ism, which clang does not support, and from what I've inferred from a certain developer clang will never support this g++-ism. When the gcc to clang switch was pulled, news/pan would not build with clang. So someone had the brilliant idea to simpy use g++ with news/pan. Unfortunately, one also needs to re-compile some (all?) libraries, which are written in C++, that news/pan uses because libstdc++ and libc++ are incompatible. I've been down that road. I now use thunderbird to read USENET. :( -- Steve