Open MPI logo

Hardware Locality announce Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-announce] Hardware locality (hwloc) v1.4.2rc1 released
From: Brice Goglin (Brice.Goglin_at_[hidden])
Date: 2012-05-03 18:31:42


1.4.2rc1 windows builds are now online as well at
    http://www.open-mpi.org/software/hwloc/v1.4/
It's my very first time building those things, so I hope they'll work as
expected.

Brice

Le 03/05/2012 14:51, Brice Goglin a écrit :
> The Hardware Locality (hwloc) team is pleased to announce the first
> release candidate for v1.4.2:
>
> http://www.open-mpi.org/projects/hwloc/
>
> v1.4.2rc1 is the first milestone of a bug fix release. It brings
> several important fixes.
>
> The following is a summary of the changes since v1.4.1:
>
> * Fix build on Solaris 9 and earlier when fabsf() is not a compiler
> built-in. Thanks to Igor Galić for reporting the problem.
> * Fix support for more than 32 processors on Windows. Thanks to Hartmut
> Kaiser for reporting the problem.
> * Fix process-wide binding and cpulocation routines on Linux when some
> threads disappear in the meantime. Thanks to Vlad Roubtsov for reporting
> the issue.
> * Make installed scripts executable. Thanks to Jirka Hladky for reporting
> the problem.
> * Fix libtool revision management when building for Windows. This fix was
> also released as hwloc v1.4.1.1 Windows builds. Thanks to Hartmut Kaiser
> for reporting the problem.
> * Add Port info attribute to network OS devices inside OpenFabrics PCI
> devices so as to identify which interface corresponds to which port.
> * Document requirements for interoperability helpers: I/O devices discovery
> is required for some of them; the topology must match the current host
> for most of them.
>
> Note that I haven't been able to post Windows builds yet but it will
> happen in the near future.
>
> --
> Brice
>
>