Re: hwloc update with so-bump and mpich rebuild

[Zbigniew Jędrzejewski-Szmek]

Hi,

I started doing the rebuilds now. I'll submit buildroot overrides
as I go. (I was hoping to do this before the bodhi enablement in F31,
but I got confused about the deadline). Unfortunately mpich now failed,
so there'll be some delay. I'll submit one big update for F31 at the
end.

Zbyszek


On Wed, Aug 28, 2019 at 06:19:36AM +0000, Philip Kovacs wrote:
>  
> Are you going to submit f31 bodhi updates for these rebuilds?  Am watching the
notifications....    On Sunday, August 25, 2019, 09:01:05 PM EDT, Orion Poplawski
<orion(a)nwra.com&gt; wrote:  
>  
>  On 8/25/19 1:17 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > Hi,
> > 
> > I made a minor mess in the mpich world and instead of upgrading to
> > 3.3.1 from 3.2.1., I built 3.1.1. I was a bit surprised when I got
> > a bug [1] that mpich in Fedora is from 2014 :(
> > 
> > I'd like to update to 3.3.1, but that needs newer hwloc which has an
> > so-bump.
> > 
> > There's a number of users of hwloc:
> > 
> > mpich
> > pmix
> > openmpi
> > pocl
> > slurm
> > hpx
> > legion
> > aircrack-ng
> > gromacs
> > 
> > They all build fine with hwloc 2.0.4, except from legion.
> > Legion is incompatible.
> > I came up with a patch to partially disable hwloc use [2],
> > and after reporting the issue upstream, I got the feedback
> > that this is the correct approach [3].
> > 
> > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1745252
> > [2] https://src.fedoraproject.org/rpms/legion/pull-request/1
> > [3] https://github.com/StanfordLegion/legion/issues/575
> > 
> > As a stop-gap measure, I rebuilt mpich-3.2.1 again today in
> > rawhide and F31. I'd like to do the update though.
> > 
> > I plan to build hwloc-2.0 and the packages listed above, incl. legion
> > with the patch on Wednesday.
> > 
> > Zbyszek
> 
> Sounds good to me.  Thanks for taking this on.
> 
> 
> -- 
> Orion Poplawski
> Manager of NWRA Technical Systems          720-772-5637
> NWRA, Boulder/CoRA Office            FAX: [phone]
> 3380 Mitchell Lane                      orion(a)nwra.com
> Boulder, CO 80301                https://www.nwra.com/
> _______________________________________________
> devel mailing list -- devel(a)lists.fedoraproject.org
> To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
>

hwloc update with so-bump and mpich rebuild

[Zbigniew Jędrzejewski-Szmek]

Packages are now built. Update is submitted for F31
[https://bodhi.fedoraproject.org/updates/FEDORA-2019-af50f19b83].

On Wed, Aug 28, 2019 at 08:08:23AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
> Hi,
> 
> I started doing the rebuilds now. I'll submit buildroot overrides
> as I go. (I was hoping to do this before the bodhi enablement in F31,
> but I got confused about the deadline). Unfortunately mpich now failed,
> so there'll be some delay. I'll submit one big update for F31 at the
> end.
> 
> Zbyszek
> 
> 
> On Wed, Aug 28, 2019 at 06:19:36AM +0000, Philip Kovacs wrote:
> >  
> > Are you going to submit f31 bodhi updates for these rebuilds?  Am watching the
notifications....    On Sunday, August 25, 2019, 09:01:05 PM EDT, Orion Poplawski
<orion(a)nwra.com&gt; wrote:  
> >  
> >  On 8/25/19 1:17 PM, Zbigniew Jędrzejewski-Szmek wrote:
> > > Hi,
> > > 
> > > I made a minor mess in the mpich world and instead of upgrading to
> > > 3.3.1 from 3.2.1., I built 3.1.1. I was a bit surprised when I got
> > > a bug [1] that mpich in Fedora is from 2014 :(
> > > 
> > > I'd like to update to 3.3.1, but that needs newer hwloc which has an
> > > so-bump.
> > > 
> > > There's a number of users of hwloc:
> > > 
> > > mpich
> > > pmix
> > > openmpi
> > > pocl
> > > slurm
> > > hpx
> > > legion
> > > aircrack-ng
> > > gromacs
> > > 
> > > They all build fine with hwloc 2.0.4, except from legion.
> > > Legion is incompatible.
> > > I came up with a patch to partially disable hwloc use [2],
> > > and after reporting the issue upstream, I got the feedback
> > > that this is the correct approach [3].
> > > 
> > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1745252
> > > [2] https://src.fedoraproject.org/rpms/legion/pull-request/1
> > > [3] https://github.com/StanfordLegion/legion/issues/575
> > > 
> > > As a stop-gap measure, I rebuilt mpich-3.2.1 again today in
> > > rawhide and F31. I'd like to do the update though.
> > > 
> > > I plan to build hwloc-2.0 and the packages listed above, incl. legion
> > > with the patch on Wednesday.
> > > 
> > > Zbyszek
> > 
> > Sounds good to me.  Thanks for taking this on.
> > 
> > 
> > -- 
> > Orion Poplawski
> > Manager of NWRA Technical Systems          720-772-5637
> > NWRA, Boulder/CoRA Office            FAX: [phone]
> > 3380 Mitchell Lane                      orion(a)nwra.com
> > Boulder, CO 80301                https://www.nwra.com/
> > _______________________________________________
> > devel mailing list -- devel(a)lists.fedoraproject.org
> > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]
> >

hwloc update with so-bump and mpich rebuild

[Philip Kovacs]

 Is there something odd going on with arch aarch64 -- openmpi builds are failing on that
arch.
    On Thursday, August 29, 2019, 04:37:55 AM EDT, Zbigniew Jędrzejewski-Szmek
<zbyszek(a)in.waw.pl&gt; wrote:  
 
 Packages are now built. Update is submitted for F31
[https://bodhi.fedoraproject.org/updates/FEDORA-2019-af50f19b83].

On Wed, Aug 28, 2019 at 08:08:23AM +0000, Zbigniew Jędrzejewski-Szmek wrote:
>  Hi,
>  
>  I started doing the rebuilds now. I'll submit buildroot overrides
>  as I go. (I was hoping to do this before the bodhi enablement in F31,
>  but I got confused about the deadline). Unfortunately mpich now failed,
>  so there'll be some delay. I'll submit one big update for F31 at the
>  end.
>  
>  Zbyszek
>  
>  
>  On Wed, Aug 28, 2019 at 06:19:36AM +0000, Philip Kovacs wrote:
>  >  
>  > Are you going to submit f31 bodhi updates for these rebuilds?  Am watching the
> notifications....    On Sunday, August 25, 2019, 09:01:05 PM EDT, Orion Poplawski
> <orion(a)nwra.com&gt; wrote:  
>  >  
>  >  On 8/25/19 1:17 PM, Zbigniew Jędrzejewski-Szmek wrote:
>  > > Hi,
>  > > 
>  > > I made a minor mess in the mpich world and instead of upgrading to
>  > > 3.3.1 from 3.2.1., I built 3.1.1. I was a bit surprised when I got
>  > > a bug [1] that mpich in Fedora is from 2014 :(
>  > > 
>  > > I'd like to update to 3.3.1, but that needs newer hwloc which has an
>  > > so-bump.
>  > > 
>  > > There's a number of users of hwloc:
>  > > 
>  > > mpich
>  > > pmix
>  > > openmpi
>  > > pocl
>  > > slurm
>  > > hpx
>  > > legion
>  > > aircrack-ng
>  > > gromacs
>  > > 
>  > > They all build fine with hwloc 2.0.4, except from legion.
>  > > Legion is incompatible.
>  > > I came up with a patch to partially disable hwloc use [2],
>  > > and after reporting the issue upstream, I got the feedback
>  > > that this is the correct approach [3].
>  > > 
>  > > [1] https://bugzilla.redhat.com/show_bug.cgi?id=1745252
>  > > [2] https://src.fedoraproject.org/rpms/legion/pull-request/1
>  > > [3] https://github.com/StanfordLegion/legion/issues/575
>  > > 
>  > > As a stop-gap measure, I rebuilt mpich-3.2.1 again today in
>  > > rawhide and F31. I'd like to do the update though.
>  > > 
>  > > I plan to build hwloc-2.0 and the packages listed above, incl. legion
>  > > with the patch on Wednesday.
>  > > 
>  > > Zbyszek
>  > 
>  > Sounds good to me.  Thanks for taking this on.
>  > 
>  > 
>  > -- 
>  > Orion Poplawski
>  > Manager of NWRA Technical Systems          720-772-5637
>  > NWRA, Boulder/CoRA Office            FAX: [phone]
>  > 3380 Mitchell Lane                      orion(a)nwra.com
>  > Boulder, CO 80301                https://www.nwra.com/
>  > _______________________________________________
>  > devel mailing list -- devel(a)lists.fedoraproject.org
>  > To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
>  > Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>  > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>  > List Archives:
> https://lists.fedoraproject.org/archives/list/[e-mail]
>  >   
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]

hwloc update with so-bump and mpich rebuild

[Jerry James]

On Thu, Aug 29, 2019 at 2:05 PM Philip Kovacs via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Is there something odd going on with arch aarch64 -- openmpi builds
> are failing on that arch. 
There sure is.  I had the same thing happen with a qd build.  Look for
this in your build log:

checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... no

and then configure decides not to add -fPIC to the compiler flags, and
the library fails to build due to invalid relocations for a shared
object.  It only happens with g++, not gcc, and it only happens in
Rawhide.  I messed around with the qd build for awhile, and
accidentally found that adding -mabi=lp64 to CXXFLAGS makes that
configure test pass.  That shouldn't be necessary, as -mabi=lp64 is
already the default.  So, yes, something strange is going on with
aarch64 in Rawhide.
-- 
Jerry James
http://www.jamezone.org/

hwloc update with so-bump and mpich rebuild

[Philip Kovacs]

 Thanks Jerry -- what you describe is exactly what I am seeing in the build.log  Phil
    On Thursday, August 29, 2019, 04:20:22 PM EDT, Jerry James
<loganjerry(a)gmail.com&gt; wrote:  
 
 On Thu, Aug 29, 2019 at 2:05 PM Philip Kovacs via devel
<devel(a)lists.fedoraproject.org&gt; wrote:
>  Is there something odd going on with arch aarch64 -- openmpi builds
> are failing on that arch. 
There sure is.  I had the same thing happen with a qd build.  Look for
this in your build log:

checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... no

and then configure decides not to add -fPIC to the compiler flags, and
the library fails to build due to invalid relocations for a shared
object.  It only happens with g++, not gcc, and it only happens in
Rawhide.  I messed around with the qd build for awhile, and
accidentally found that adding -mabi=lp64 to CXXFLAGS makes that
configure test pass.  That shouldn't be necessary, as -mabi=lp64 is
already the default.  So, yes, something strange is going on with
aarch64 in Rawhide.
-- 
Jerry James
http://www.jamezone.org/
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/[e-mail]