On Mon, Jan 27, 2020 at 09:30:15AM -0700, j...@bitminer.ca wrote:
> Hi Martin,
>
> Thanks for the pointer to a ports page (I needed to reread it,
> clearly!).
>
> Just one nit to your example: perhaps reformat to style(9).
Sure, why not!
And README needs to go into the PLIST of course.
Index:
Hi Martin,
Thanks for the pointer to a ports page (I needed to reread it,
clearly!).
Just one nit to your example: perhaps reformat to style(9).
John
On 2020-01-27 01:12, Martin Reindl wrote:
[CCing Dave Raymond who helped with the openmpi-4.0.1 update]
On Sun, Jan 26, 2020 at 09:21:30AM
[CCing Dave Raymond who helped with the openmpi-4.0.1 update]
On Sun, Jan 26, 2020 at 09:21:30AM -0700, j...@bitminer.ca wrote:
> Hi Martin,
>
> I don't know how to compare the libraries (md5?). I reviewed the
> build logs and diff'd the text files (.h). The build logs showed
> the same
Hi Martin,
I don't know how to compare the libraries (md5?). I reviewed the
build logs and diff'd the text files (.h). The build logs showed
the same compilers (gnu) was used to create mpi binaries and
libraries. The .h files had no differences.
Reviewing the source
is what convinced me that
Hi John,
Did you check the libraries for changes?
I will see if I can find time to commit just the fortran bits tonight.
Then I will look at the CC and README additions.
Thanks for the effort to improve the openmpi port!
-m
Am 25.01.20 um 00:17 schrieb j...@bitminer.ca:
> Hi Martin,
>
> I
Hi Martin,
I have added the CC definition and rebuilt with your other patches
and it works OK on AMD64.
John
Ensure openmpi mpicc and mpifort use GNU compilers
Index: Makefile
===
RCS file: /cvs/ports/devel/openmpi/Makefile,v
Hi Martin,
On 2020-01-22 03:07, Martin Reindl wrote:
On Tue, Jan 21, 2020 at 01:20:29PM -0700, j...@bitminer.ca wrote:
[]
Hi John, Hi Stuart,
I've got around to testing this now a bit more:
- Currently, the port does not use flang. It used to before the update
to
openmpi-4.0.1.
Hi Stuart,
On 2020-01-22 09:31, Stuart Henderson wrote:
On 2020/01/22 09:24, j...@bitminer.ca wrote:
The mixing of gcc-built code with clang "runtime" is not really
such a big deal on AMD64.
I know very little about openmpi but it looks like you're intending
this
as a general statement. For
On 2020/01/22 09:24, j...@bitminer.ca wrote:
> The mixing of gcc-built code with clang "runtime" is not really
> such a big deal on AMD64.
I know very little about openmpi but it looks like you're intending this
as a general statement. For C code it's not a problem. For C++ code it's
a big
Hi Martin,
On 2020-01-22 03:07, Martin Reindl wrote:
On Tue, Jan 21, 2020 at 01:20:29PM -0700, j...@bitminer.ca wrote:
On 2020-01-21 12:45, Martin Reindl wrote:
> Am 20.01.20 um 22:55 schrieb j...@bitminer.ca:
> > This fixes the mpifort command which can't find egfortran.
> >
> > I also
On Wed, Jan 22, 2020 at 10:20:10AM +, Stuart Henderson wrote:
> On 2020/01/22 11:07, Martin Reindl wrote:
> > I've tested the folling diff and checked the libraries for changes with the
> > help of shared_libs.log. libopen-pal only has adress changes and libopen-rte
> > as a tiny symbol name
On Tue, Jan 21, 2020 at 01:20:29PM -0700, j...@bitminer.ca wrote:
>
>
> On 2020-01-21 12:45, Martin Reindl wrote:
> > Am 20.01.20 um 22:55 schrieb j...@bitminer.ca:
> > > This fixes the mpifort command which can't find egfortran.
> > >
> > > I also propose removing COMPILER = base-clang since
On 2020-01-21 12:45, Martin Reindl wrote:
Am 20.01.20 um 22:55 schrieb j...@bitminer.ca:
This fixes the mpifort command which can't find egfortran.
I also propose removing COMPILER = base-clang since this compiles
with gcc anyway. GCC also has some advantages for us fortran
users (coarray
On 2020/01/21 20:45, Martin Reindl wrote:
> Am 20.01.20 um 22:55 schrieb j...@bitminer.ca:
> > This fixes the mpifort command which can't find egfortran.
> >
> > I also propose removing COMPILER = base-clang since this compiles
> > with gcc anyway. GCC also has some advantages for us fortran
> >
Am 20.01.20 um 22:55 schrieb j...@bitminer.ca:
> This fixes the mpifort command which can't find egfortran.
>
> I also propose removing COMPILER = base-clang since this compiles
> with gcc anyway. GCC also has some advantages for us fortran
> users (coarray fortran).
Hello John,
- OK for the
15 matches
Mail list logo
