Trace should probably just be eliminated. I "championed" it a long time
ago, but the reason for doing it has long passed - and as a result, it is
virtually unused in the code base.
On Wed, Jul 10, 2013 at 12:40 PM, Vasiliy wrote:
> Nothing special, for a trace it's just --enable-trace. I'm not
Nothing special, for a trace it's just --enable-trace. I'm not
building libompitrace though, following marco's suggestion, only
arbitrary defined MCA_BASE_VAR_VERBOSE_MPIDEV_ALL = 2 (it wasn't
defined anyway), and did not change the library ordering.
It wonderfully passes almost all the tests even
What command are you using to configure OMPI?
On Jul 10, 2013, at 2:58 PM, Vasiliy
wrote:
> not exactly the subject, however, since I've mentioned 'trace' here,
> it's for this thread:
> - undeclared 'value', or should I have configured it with
> -Dvalue=, it wouldn't compile anyway
>
> make[
not exactly the subject, however, since I've mentioned 'trace' here,
it's for this thread:
- undeclared 'value', or should I have configured it with
-Dvalue=, it wouldn't compile anyway
make[3]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/opal/util'
CC trace.l
No issue with doing so. If this was someone trying to use it, I'd put it at a
high priority. If just someone trying all the configure options, then a lower
priority.
The problem stems from a little bit-rot. Those components are updated and
working on a side branch being used by my old company,
(giggling) No, it's unsafe. I've disabled 'trace' for now. On a more
serious note, why not adding those, if they should be here?
Making check in mca/sensor/resusage
make[2]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/mca/sensor/resusage'
CC sensor_resusa
Is it safe to say that you are going thru an exercise testing every option that
exists? Just want to know so I can set expectations
On Jul 8, 2013, at 11:47 AM, Vasiliy wrote:
> there're more to come:
>
> Making all in mca/sensor/resusage
> make[2]: Entering directory
> '/usr/src/64bit/releas
there're more to come:
Making all in mca/sensor/resusage
make[2]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/orte/mca/sensor/resusage'
CC sensor_resusage.lo
/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/orte/mca/sensor/resusage/sensor_resu
Oh, well, it does not:
Making all in mca/db/sqlite
make[2]: Entering directory
'/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/build/opal/mca/db/sqlite'
CC libmca_db_sqlite_la-db_sqlite_component.lo
/usr/src/64bit/release/openmpi/openmpi-1.9.0-a1/src/openmpi-1.9.0/opal/mca/db/sqlite/db_sq
Actually, those headers needed to be deleted - done. I take it you were
deliberately trying to build that support? Otherwise, it shouldn't have built.
On Jul 8, 2013, at 11:11 AM, Vasiliy wrote:
> Could somebody add these required headers to the repository? Thank you
> in advance:
>
> Making a
10 matches
Mail list logo
