Devin Matthews
Devin Matthews
BTW, can you also send the output of `powerpc-eabivle-gcc -dM -E - < /dev/null`?
@jongwonjlee shouldn't you have to explicitly link some library or libraries with `-l` for EWL?
> BTW, it faced warnings as stated below. Do you think this may result in a significant problem later on? (I attach the [log](https://github.com/flame/blis/files/7061103/make.log) while executing `make`.) > > ```...
There's not really any pre-defined macro in that list that gives an idea what OS it is/will be running on. @fgvanzee for builds with `--disable-system` maybe `bli_system.h` should instead define...
@jongwonjlee re the flags for EWL, based on the GCC docs I think all you need is `-nostdinc -Ipath/to/EWL/include -Ipath/to/EWL/include/`. These should probably be specified at `configure`-time.
@jongwonjlee my understanding is that you initially got the error "Cannot determine operating system"? @fgvanzee if so then yes this is needed for @jongwonjlee's configuration to work properly without masquerading...
Are you sure `BLIS_ENABLE_SYSTEM` is getting defined? It looks like not.
For the MPI run have you set either `BLIS_NUM_THREADS` or `OMP_NUM_THREADS`? The other thing to check would be the process affinity. Are all cores actually being utilized or are multiple...
BTW, you should not set CFLAGS when configuring BLIS, although I don't think this is the problem.
Huh. My next thought would be to build BLIS without threading and try the MPI again.