Date: Mon, 16 Oct 2017 02:32:07 -0700 From: Yuri <yuri@rawbw.com> To: Gleb Popov <6yearold@gmail.com>, FreeBSD ports list <freebsd-ports@freebsd.org> Subject: Re: Using blaslapack Message-ID: <ea81868d-4a63-4133-899c-0fdae6f25a51@rawbw.com> In-Reply-To: <ff52a059-b54e-d904-ca1c-185c62faea9b@rawbw.com> References: <CALH631nHU9ZSkJKx4ptgcRTDASmi7UnMnjPGHWtaWEEK_Y-8hw@mail.gmail.com> <CALH631nWkhedW5s=8R-GWZnZ3fsYM4hVN=yXXMe2QFo8vc4KDw@mail.gmail.com> <CALH631k2kAs0qtz36XvY=c2xcsrgetriA_iNqQMhavxTtES1=g@mail.gmail.com> <CALH631=YD2qoTNDh6r%2B0%2Bb-OzADEC-8F9HAQ4uoOWZuPw44zjA@mail.gmail.com> <CALH631mDpr2VFoVnxB5oegkL5UdNmRvmv7i_ZNMfQLLHB=KbUQ@mail.gmail.com> <CALH631=VdJd78ixjGJg1=N=LphTyiBbpk2GAnR34m42EUzdy1Q@mail.gmail.com> <CALH631=NSpx76EVVHWMBtGAKTWzD_nfU5EPUH5EwOkPXaBVRAA@mail.gmail.com> <CALH631kvLSZpRmcVg_zrXTq105zs97LdUvqgXh6QPv64x=U-Tg@mail.gmail.com> <CALH631kYp-7HcGwoeTtzrF%2BZhW4b8c6O-GpCQMLj2JuyWBLUfA@mail.gmail.com> <CALH631=0aW8Ag_khWBUyDE=3kJoHt9zC75YXkqiFXxiHrzo8cA@mail.gmail.com> <CALH631nw1pqoDewgHpm_SQYWa490WiGdYdhqo3tNfiHK_uiPCw@mail.gmail.com> <CALH631=c%2BoSuS6=J7G3r8njAmVBQG_oeBb=7EtEZvoO2t=c=zA@mail.gmail.com> <CALH631=mEn2p2cmE7t7cWsoDpJceEjFgd_sE2eMe3QRUqx=iDA@mail.gmail.com> <ff52a059-b54e-d904-ca1c-185c62faea9b@rawbw.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/16/17 02:18, Yuri wrote: > > You can try to apply the patch from > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220313 and then have > USES=fortran:flang instead of just USES=fortran in your port. Please > let me know if this works. flang is a new, experimental fortran > implementation that aims to replace gcc fortran. Sorry, you also need to set USES=fortran:flang in blas/lapack and rebuild them too. All involved fortran-using ports need to use flang. Yuri
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea81868d-4a63-4133-899c-0fdae6f25a51>